unforum

[Nighthawk]

Won't be able to see show tonight; guess I'll have to wait 'til its up on the Hulu beta.

[Rift]

New video on the Enitech blog. Looks like Anna is in trouble after all.

[Rift]

I emailed the Resistance the other day expressing the concerns brought up about whether helping Dyson was a good idea or not and a few minutes ago I got this response.

[resistor]

I thought the same thing, but didn't say anything because technically, we could say/think that about a lot of things in the game, and I'm just going to go with it... but I totally understand what you mean.

[thebruce]

haha ok two things - new blog, with new diagram

and BlueCom is now "Dyson Foundation Neural Network"... and the result of "one" through "six" is now different, and the -image- in the original flash is now text, which is updated with the response from the value checking PHP

*cough*meta*cough* seems someone may have uploaded the wrong version of bluecom? this may also explain the "one" through "six" solution, hehe

It's now much more consistent with what it intends to do... other than the random generation


eta: the central character now is random from between ascii 33 and 122 (! and z - meaning it includes: all numbers, all shift-characters, lower and uppercase letters)
eta2: ok hold on that... the code says that, but the results show special characters; odd


ok, seems the diagram is the same but the character is different. Not sure why it's showing more than 33 through 122... unless it's unicode or something.

[thebruce]

OK! - we're getting somewhere... but I think there's still a bug...

3 of the GPS coordinates match the patterns... but 3 others don't - and what are the three that don't? the coordinates given to us to find the cameras...

can vpisteve, rosekitty, and madeatdark verify the GPS locations they sent for their photos (since these are gps locations of the cameras)?

We have (using comma, no space):
1) 34.261553,-118.496448 LA (vpisteve)
2) 40.714924,-73.991906 NY (zoltan - check!)
3) 37.947057,-122.570434 SF (enitech -check!)
4) 30.474281,-97.885428 TX (rosekitty)
5) 28.683445,-81.396604 FL (madeatdark)
6) 37.894244,-122.528222 SF (enitech -check!)

[bryanflurry]

[thebruce]

yeah it doesn't match slice 4 or 5...

vpisteve's reported GPS coordinates are right actually (quoted in [url=http://enitechlabs.com/blog/?p=78]enitech's blog[/b]), not the camera location, so now we have 4 working coordinates:

1) 34.046935,-118.250688 LA (vpisteve - check!)
2) 40.714924,-73.991906 NY (zoltan - check!)
3) 37.947057,-122.570434 SF (enitech -check!)
4) 30.474281,-97.985428 TX (rosekitty)
5) 28.683445,-81.396604 FL (madeatdark)
6) 37.894244,-122.528222 SF (enitech -check!)

rosekitty and madeatdark - can you quote us the GPS coordinates you sent to enitech with your photos??

(sorry, not 'madetoorder' as I typed previously haha )

[MrToasty]

30.474281, -97.985428
Rosekitty's from here:
http://enitechlabs.com/blog/?p=84
One number off?

[thebruce]

yeah, tried them both already... forgot to correct that 2 posts up, it should be 9

I think she just quoted the GPS location of the camera... rosekitty and madeatdark I believe were the two with pictures already on the camera. How would they know the photos' gps coordinates?

[thebruce]

heh, well sure enough, I found ascii strings that produce the right slice layouts... by adding single ascii values to digits (0 through 9) and iterating through them for the TX and FL locations, this set of numbers produces an identical diagram to what we're looking for... but obviously the two values are incorrect.

* 34.046935,-118.250688 LA
* 40.714924,-73.991906 NY
* 37.947057,-122.570434 SF
* 99.999999,-99.997428 TX (+48 from 30.474281,-97.985428)
* 99.999999,-99.997604 FL (+48 from 28.683445,-81.396604)
* 37.894244,-122.528222 SF

the TX and FL locations have an ascii sum difference of +48.

Doesn't help much. But at least it satisfies the spec that the diagram can look right even though the values are wrong. It would be too much work to try any feasible digit variant corodinates to find the right two. I think we need to wait for word from Dyson.
and with that I'm done for the night.


edit: corrected 0-9 ascii order and difference sum

[hauser]

"Know your enemy"

Perhaps the model numbers of the Terminators?

Or, if not that, how about a number designation of the word RESIST? 6 letters, 6 numbers?

I'm not a numbers guy, just looking at it from a way that anyone may figure it out.

[Nighthawk]

Well, I could theoretically "brute force" this in no time at all...

Let's assume that at least the whole numbers of the latitude/longitude are correct. So we can mathematically narrow down the possible values to a handful because we know what they're supposed to add up to.

So... should I?

*EDIT*

When you hit the PHP post page directly, you get this slow typed on to the screen:

[Nighthawk]

thebruce: How are you getting those two missing numbers?

"30.474281,-97.985428" to me adds up to 1030
"99.999999,-99.997428" to me adds up to 1078

That's a difference of 48, not 33...

[thebruce]

blah, yeah it's 48. I don't know why I was thinking 0 was higher than 9 in ascii... *smack*

30.474281,-97.985428
99.999999,-99.997428
=
6,9,5,2,5,7,1,8...2,1,2
=
48

so yeah, both coords are 48 ascii less than the correct sum. or, with 16 digits in each coordinate, each digit is effectively 3 less than the right value (if spread evenly). strange...