Dutch
Master Poster
- Joined
- Feb 22, 2007
- Messages
- 2,466
It has been the same valid point over and over that you ignore. Namely, you cherry pick your data.
For example, earlier you linked your timeline to an earthquake and proclaimed it a significant hit. I pointed out that similar sized earthquakes occur nearly every single day. So, how can one earthquake be significant while dozens of others are ignored?
You are referrring to the 8.4 Sumatra quake on September 12. I have already outlined why this quake is significant with my November 15 HD Cube analysis that gives predictions for these future Phi points too.
If you want to be taken seriously you need to do some things that people have been asking for from the beginning of this thread.
1) Define what is a significant event.
an event that can be identified as a valid expression of expected themes on specific moments in our perspective of time. That could be high impact or subtle
2) List all significant events within a given time frame.
these events are monitored with the timelines I use
3) Show any significance of the intervals between related events.
that depends on the timecoded pattern on which the underlying themes find its expression in our reality, so what do you mean here exactly?
What you are doing is prejudging what dates should be significant, then finding anything on that date to create your match. The problem being that equaly significant events like the ones you highlight are occuring all over the intervals between your 3840 days (or whatever time frame you are looking at).
I identify a future timeframe that could give expression of specific underlying themes. It does not happen everyday that the Pope dies, the birdflu breaks out or Tolimir is arrested. In fact every single event could be put into perspective if you have the time to do so and if you have a complete understanding of the underlying Design. I only use a few limited elements of described Design and the 'coincidences' already jump off the screen. If you want to judge what I am doing than you have to follow my postings on the tim eline realtime
It would be like me saying that since a red car was in an accident on Monday this week and Monday last week it is proof of an underlying design. Well not realy, since if I bothered to check I would likely find that red cars are involved in accidents every day, just like other color cars.
and why is a period of a week significant? I use elements of Design that give recurring 'coincidental' expressions of expected related events.
But that is what you are doing. You pick an event, then you pick some time interval and go looking for a related event on that interval. But your mistake is that you are not also looking at how many times related events are occuring off your desired interval alignments.
so that means that a complete understanding of the underlying Design could indicate even more related events, if they are indeed related.
That is your cherry picking of the data. And that is what makes it all meaningless. And that is what you keep ignoring.
that remains to be seen. Obviously you have missed the 'in the face' moments when these odd 'coincidences' occur on the expected keydates.
You should keep an eye on the timelines very closely if you think that you can dismiss this as meaningless, or you give it a rest