unforum

[zaeil]

The file seems to be in three sections:

• The Cube
  
• The margin-to-margin center. The greater-than/less-than symbols seem to be arrows...see how they change direction in alternating lines? It would seem that whatever code is in that section, it snakes around. Left-to-right on the first line, around the end to include that stray "5" that in between the two lines, then right-to-left on the second, around the end to the next line, and so on. This continues to the incomplete line that runs right-to-left right before the third block section.
  
• Block at the end. This looks to be its own section, reading left-to-right, line by line.
  

That's all I have so far.

[lotusflower]

It does definitely all unravel into one string, regardelss of whether that's what we're supposed to do with it!

[Zedix]

I'm writing a program to get the big string from beginning to end, should be done soon enough.

[Scott]

hi.

here's something:

there are no zeroes. nadda.

I have made a nice spreadsheet of the bastard. every character has it's own cell. enjoy.

[lotusflower]

This is the part of the string that is made up of the top face of the cube (it then leads down the left side) and all the bottom bits under the cube... I haven't don the beginning as someone else is working on that. So, this is actually half-way through the message, but might be worth getting a look at while we unravel the beginning...

Or I may just have wasted a lot of time ; )

EDIT: I must add, I did this pretty much by hand, so errors are HIGHLY possible : |

[brat-sampson]

In the chat people are working on unraveling it all starting from the top left of the image where there's a v and following the <,>,^ and v arrows for direction. As for how to decode the eventual string...

[Peapod]

Following the arrows the first 'line' looks like this:

49*9*7*v99*94*1+*v23*9*64*5+*v84*9*3*v29

removing directional markers:

49*9*7*99*94*1+*23*9*64*5+*84*9*3*29

If you go through the entire text until it looks like this, and assume * is a space and + is a word boundary, we may then be able to dechiper what is left. Of course, someone has to go through actually unravelling everything.

[cassandra]

If it's all one string, how did you get to the "78287568" string in the top face?

[BrianEnigma]

I think the talk on IRC is to start at the upper left corner of the file, then "walk" in the direction of an arrow until you reach another arrow, then walk in that direction. Eventually, you will find your way to the "@" at the end. In so doing, you en dup with a sequence of numbers separated by "+" and "*". See attached.

[Atrophied]

thank you Bri no more transcribing for these fingers...

[oliverkeers13]

Well at least we know what the markings on the side of the cube are now...

[BrianEnigma]

Also, if you guys want to know where the traversal path goes and doesn't go, there are a few numbers that never get touched. I doubt it helps, but I will add it for consistency. The red is what was visited while "walking" through the picture. The white is where we never went. Keep in mind that the data/html is pretty style-heavy, so takes a number of seconds to load.

[Zedix]

For what it's worth, here's my output in a text file, omitting all directional arrows and spaces. And yes, it does bypass some numbers, especially on the top left of the cube on the "I" face.

[fkeles]

I think it is Reverse Polish Notation.

[BrianEnigma]

P.S. If anyone thinks that can do something with my source for traversing the ASCII "picture," have at it. The C source is attached. Admittedly, it is not as efficient as it could be, but what do you expect from 5 minutes of development time?