"System clock
Changing the system clock will affect the counter accordingly; it seems to reset to 1d 2h 34m 56s upon reaching 0:00:00:00. Could this mean it's just a hoax, or does that just mess with it, the only valid time being when it hasn't been changed? 64.231.120.38 01:30, 30 June 2006 (UTC)
<Quickman> Look at that comment in context.
<Quickman> if(diff<=0 && !document.getElementById('deployed')) {
<Quickman> location.href='/';
<Quickman> /* REDIR UNTIL USER/SERVER SYNC */
<Quickman> }
<Quickman> The reason it's just refreshing if you skip to the end of the countdown is simple.
<Quickman> if(diff<=0 && !document.getElementById('deployed')) {
<Quickman> It's looking for that GET string as well as the countdown being over.
Friend of mine (Wikipedian ThomasWinwood) found this out by analyzing the JavaScript, so even if you just end the countdown, it won't do anything - yet.--Guess Who 08:06, 30 June 2006 (UTC)
Not that any of that actually means anything. The clock is just a simple contrivance for the sake of having something active on the page rather than just a static "wait until [date/time]" message, and tampering with it won't make any difference to the time the site operators actually reveal what it is they're trying to sell us (which is all I think it will turn out to be). ~ Matticus78 14:15, 30 June 2006 (UTC)
This is what happens when the timer reaches zero:
http://eon8zero.ytmnd.com/"
z en.wiki
![:]](./images/smilies/icon_har1.gif){kind=icon}
((
((