AnneFan
Smiling Assassin
- Joined
- Aug 1, 2011
- Messages
- 22,135
- Reaction score
- 140
- Points
- 73
Fans can't do that.I think its a good idea to just ignore it.
When the trailer is there,
We will know, we will hear about it .

Fans can't do that.I think its a good idea to just ignore it.
When the trailer is there,
We will know, we will hear about it .
You guys must've missed it. After looking into the source code, we discovered a countdown within it.
That countdown doesn't end until Monday.
Interestingly, inside the javascript function that uses that variable...90000 (seconds?) is immediately subtracted from the value of deltaT (the parameter is dTL inside the function). This would translate to -25 hours. I'm still studying the code, but it's possible that 0 could get here a little sooner.
Also, I noticed if you're using a mobile device, you get a looping gif of the static, rather than a video:
http://www.manofsteel.com/transmissi...9/incoming.gif
Here's a link to the javascript if anyone else wants to check it out:
http://www.manofsteel.com/js/src/transmission.js
A couple of other things:
The transId variable determines the URL the video and audio come from.
The deltaT (- the 25 hours) variable eventually gets stored in a value called tRem. I'd wager that's short for 'time remaining'.
I also think that as things get closer, we'll end up with a visible countdown. There's no need to have javascript counting down on the client side...unless you want to show the client how much time is left, either explicitly, with an on screen countdown...or 'covertly', with exposed javascript that you didn't bother to obfuscate. So, either it's a visible countdown...or they WANT us to poke around in their code and come up with the answer ourselves. Or I'm wrong.
Not quite. It's the original guess - 25 hours.A few pages back, a guy told us that it's more likely a 25 hours countdown
Ah... Remember a week ago when we were soulless husks getting into fights about arguing about arguing about arguing there was nothing to talk about?
Not quite. It's the original guess - 25 hours.
And with the way it's rounding internally, I think that translates to:
aM = 2777.383333333333 = 2777 (minutes)*
aH = 46.28972222222222 = 46 (hours)
aD = 1.928738425925926 = 2 (days)
..from now
*The minutes are probably about a half hour off by now.
So, Sunday night?
Is it true the trailer is 3 minutes and 5 seconds?
when is the MTV awards thing?? is it this weekend?
Yes, it's this Sunday night.when is the MTV awards thing?? is it this weekend?
Only if I have any idea what I'm talking about.So, Sunday night?
My best guess for that javascript, is that it loads the video/audio initially, then every half second, checks to see how long it's been since the page was loaded. If it's been long enough [ (the hour you loaded the page + 3)/5 != (current hour +3 /5)] (that's every 5 hours, if my math is right), it refreshes the page, which would load new audio/video (if it's time for it) or the old one (if it's not).
The question for me still is, how does the code know when it's time for the next audio/video, and is it predictable?
Also, it's not clear what happens when the countdown hits 0..other than it forces a hard refresh of the page and clears all the countdown variables.
That hard refresh is called displayDriver_finish, which is probably a good sign.
Edit:
Only if I have any idea what I'm talking about.
Sunday night.
Yes, it's this Sunday night.
hmmmm.........the page looks like TV static.
the MTV awards are this Sunday......
hmmmm............
hmmmm.........the page looks like TV static.
the MTV awards are this Sunday......
hmmmm............
hmmmm.........the page looks like TV static.
the MTV awards are this Sunday......
hmmmm............