All Things Superman: An Open Discussion - - - Part 40

Status
Not open for further replies.
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.

Oh thanks man :up:, I don't know JavaScript :woot:. Hope the trailer is here in less than 25 hours
 
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.

Let me be the first to welcome our newest :ninja: to the Hype! :applaud

:woot:
 
It definitely changed. And I think jasvll is right, there is a possibility of it coming sooner. I feel like we can do something to possibly speed it up but we don't know what that is yet.
 
It definitely changed. And I think jasvll is right, there is a possibility of it coming sooner. I feel like we can do something to possibly speed it up but we don't know what that is yet.

Not sure. Maybe leaving the site and going back to check helps on the count.
 
This is like a combo of two of the virals from TDKR. The one with the audio signals for the advanced screenings and the one with each frame of the third trailer before its release.
 
maybe it will be Faora's face telling the people of Earth to prepare ourselves......to KNEEL BEFORE ZOD!! :D
 
There is something there, behind it, but cant tell if its more static.
 
My guess is it will start like a tv with a bad signal. In and out. Then it will suddenly be clear.
 
This is like a combo of two of the virals from TDKR. The one with the audio signals for the advanced screenings and the one with each frame of the third trailer before its release.
I was thinking of TDKR's virals, so I opened the audio files up in a program to analyze them the same way the hidden text was found in TDKR's files, but didn't have any luck.
 
So, the transID variable, and in turn, the audio/video URL, has changed 3 times:

x39ck -> clkse89 -> c934k200

Someone spot the pattern (assuming there is one), so we can skip to the end of this thing.

I have a guess that those numbers could be seconds left in the countdown or a time value encoded into something other than base10. That way, the URLs can change automatically, without anyone having to update them on WB's side.

Let me be the first to welcome our newest :ninja: to the Hype! :applaud

:woot:

Why, thank you.
 
So, the transID variable, and in turn, the audio/video URL, has changed 3 times:

x39ck -> clkse89 -> c934k200

Someone spot the pattern (assuming there is one), so we can skip to the end of this thing.

I have a guess that those numbers could be seconds left in the countdown or a time value encoded into something other than base10. That way, the URLs can change automatically, without anyone having to update them on WB's side.



Why, thank you.
Of course. My thoughts exactly ( yeah right )
 
So, the transID variable, and in turn, the audio/video URL, has changed 3 times:

x39ck -> clkse89 -> c934k200

Someone spot the pattern (assuming there is one), so we can skip to the end of this thing.

I have a guess that those numbers could be seconds left in the countdown or a time value encoded into something other than base10. That way, the URLs can change automatically, without anyone having to update them on WB's side.



Why, thank you.

Are you a WB ninja sent to stop us from losing our minds and give us hints? :oldrazz:
 
Status
Not open for further replies.

Users who are viewing this thread

Back
Top
monitoring_string = "afb8e5d7348ab9e99f73cba908f10802"