Solutions for HEX data

[Shota]

In pictures, single bytes typically represent less than a dot, this is not entirely true, but for simplifications sake lets assume a 10 by 10 pictures is made up of RGB codes. This means you get 1 RGB code for each pixel, or 10*10 = 100 RGB codes. As you can see, trying to fill square holes that are many pixels is gonna take far more than a few random bytes.

Now any one who knows more about how these files are made will know that this is grossly oversimplified, but I do believe the general principle still applies, this data is insufficient to fill these holes.

[d.b]

Another interesting fact. The blue box has another CSS class compared to the other. All boxes have the “unlocked” class whereas the blue one has the “unlock me” class. So this one must be special
Link: Imgur: The magic of the Internet

[NeoKamuro]

No i got the same too on an other Location. I guess thats just simply the sqare “youre” Code unlocked

[toddumptious]

Could our Citizen Scientist codes have ANY correlation? Probably not, sourcing and matching up everyones unique citizen ID with their decoded numerical string, would take FOREVER!

Keep up the hard work guys, hoping something pops up I can help with soon

[fphenix]

the “unlocked me” is the one you decoded and that is highlighted for you (hence everyone (rather every group) has a different one).

[arpoja]

Wow… this is way over my knowledge… good luck guys!

[d.b]

Yes this is definitely “your” code on the HEX Tab with all boxes but there is this second blue box always placed at the same position under the dataset word in the Picture Tab.

[fphenix]

it displays both your code in the hex tab and the piece of the picture (highlighted rectangle) that you decoded (corresponding to your code).

get rid of the hex, and hover over that rectangle, you’ll see your code appear in a small text box.

[Oholiab]

That is what I was thinking. There are three numerical sequences relative to our emails:

• Citizen Scientist number
• the initial Unique Code
• the cypher of the initial unique code

Is there any correlation or other significance?

[PeacefulGamer]

These look like hex colour codes that provide RGB values. RGB has been a theme. I would look in that direction

[Malveka]

@NeoKamuro

The holes contain hex Code when you hover with youre mouse over:

A77E1DE 583A095 55D4994 64F6F90 3CB6135 A0D6816 303F9E1 EA41CB3 E142C4A 80627EC 2A9A503 923022D 41056BB EA23B80 67E2FB5 A01F12E 10AF838 6D40BD1 333EE87

@Shota

Another oddity I noticed is that in the HTML source of the page all Hex codes are listed as having an ID of “byte-14399” ~ “byte-15422” (they are in ascending order, the first is 14399, the last is 15422).

Running with these ideas, if we do the lookup in the page source for bootsector.wakingtitan.com, we get this:

A77E1DE => byte-14547
583A095 => byte-14559
55D4994 => byte-14694
64F6F90 => byte-14699
3CB6135 => byte-14709
A0D6816 => byte-14987
303F9E1 => byte-15016
EA41CB3 => byte-15070
E142C4A => byte-15026
80627EC => byte-15074
2A9A503 => byte-15097
923022D => byte-15162
41056BB => byte-15215
EA23B80 => byte-15280
67E2FB5 => byte-15322
A01F12E => byte-15323
10AF838 => byte-15329
6D40BD1 => byte-15366
333EE87 => byte-15372

Is it possible we could use these as offsets into a file somewhere and extract the corresponding bytes?

[Shota]

Possible yes, the bytes of 1 file could form a message or another file. The question remains, which file? If you want to run with this it needs to be a file with a size of at least 15.4kb.

[Malveka]

@Shota

The question remains, which file?

That is the question, isn’t it!

I’m rather new to this endeavor, having mostly missed phase 1. Are there any existing files in the data collected so far to which this approach could be applied?

[Shota]

Most of the image files at least. I mean, even both decoder ring wheels are about 200~300kb in size. That being said, there is no particular reason to suspect those. The most likely candidate I can think of right now is the image of the notebook that’s behind all the hex codes. Maybe I’ll try that later

[PeacefulGamer]

Perhaps the numerical gap between these figures is something?

[Shota]

I object to your conversion of these numbers to RGB codes.
RGB is a 3 byte entity, that requires a 6 digit number in the form of #AABBCC the numbers you input are 7 digits, so you’re just leaving out a random one, that is not a proper conversion.

[d.b]

Just tried to pick the byte values mentioned by @Malveka from the background picture. Got this : 24 05 3F 21 A2 9C 4E A1 19 05 F6 4E FD 8D 75 FD 06 F1 3B
With the byte index sorted ascending: 24 05 3F 21 A2 9C 4E 19 A1 05 F6 4E FD 8D 75 FD 06 F1 3B

[Thumister]

I’ve been thinking for a couple of days this looks like this is probably 3x16-bit RGB + an 8-bit mask. If it’s an image, then it’s 32x32 = 1024 which would probably make it an icon file (possibly).

…or we could be being completely stupid and it’s a boot sector (because we’re on bootsector.wakingtitan.com).

[NilClass]

This is probably nothing, but I couldn’t resist playing around with the data on the site. I used the jquery on bootsector.wakingtitan.com to pull the title attribute of all tiles and join them, then saved those results to a local file, and used Ruby to convert them from hex. I’m a fan of using the *nix file command to identify file types, but had no luck with those bytes as-is. When I reversed the file, though, I got:

wt-data.bin: PGP Secret Key -

It didn’t import to my keyring, though, with the following output:

gpg: packet(5) with unknown version 96
gpg: read_block: read error: Invalid packet
gpg: import from 'wt-data.bin' failed: Invalid keyring
gpg: Total number processed: 0

So, like I said, probably nothing. Just thought I’d share anyway.

[PeacefulGamer]

Well then. Seems the byte data is more relevant anyway