Tuesday, July 21, 2015

The Vine Point or The “Where’s the l1z1wxAvx4t Door?” Point



When we saw this point, both Jason and I immediately thought YouTube. The TvCyd3MZWRh string is the exact format of youtube video IDs, an 11 character case sensitive hash. It turns out, it wasn’t exactly the same as YouTube, but more on that later. At any rate, we did a lot of searching around youtube to try to find something. The string itself didn’t work.

So we tried converting the string using the key that the CM gave us: underthemat. It has 11 characters, so it matches up well with the gibberish string from the first part of the clue. This is where things got a little sticky. We assumed the encoding was using a standard base62. It's a way to convert a very large number into a very small string by using 0-9, A-Z, a-z encoding. This was hinted at in the original clue's numbering scheme, and it's similar to YouTube's encoding format, which uses base64 instead of 62. We created a table where 0 = 0, 1=1, A=10, a=37, and z=61. This is a standard base62. I have no idea why we thought there would be anything standard about the encoding.

Decoding the lock and key using that system would never have worked, but it didn't really matter, since we didn't know the door yet anyway. The CM gave a series of clues that made it clear that it wasn't using a standard base62 encoding.

Maniac lob is an anagram of cobalamin, which is vitamin B-12. So our assumption that B=11 is wrong. B = 12. That meant that there had to be another character between 9 and A, so we threw the Zero in that spot. Now, decoding the lock and key gives us OjqdVw5EJ3b

Awesome! so now what do we do? We tried that at YouTube, nothing. I also noticed that the password was similar to the old Flocculent Abe password from a few years ago, so we started trying to log into twitter accounts that had previously been used for the code. Nothing. We were honestly stumped as to what to do with the code.

A note here - another codebreaker, Steve T, we'll call him, figured out the Marvin Gaye hint when nobody else did. He tweeted that right after the codemaster posted the original point. In fairness, as a child of the 80's, if he'd said "California Raisins" I probably would have gotten what he was referencing quicker. We also totally missed the twizzler and pitfall hints until after we figured out what we were supposed to do.

Finally, it was sorta dumb luck that ended up showing the answer. I was browsing around on my personal twitter account and I watched a Vine video from one of my friends. That's when I noticed that the URL of the video had the same 11 character base64 string that YouTube uses!

I dropped the decoded string into Vine and found this:



This is where things get messy. So we're supposed to watch this Vine and figure out a hashtag based on the pictogram in the video. Take a second to watch that. Obvious, right?

So it starts with a picture of twitter, so tweet at the codemaster. So far so good.
Bag of Almonds = Pound = Hashtag
Grate = Great
Nintendo = NES
A ceiling light dimming = Fades
A paper with "The" followed by Google's Source code = The Code or The Site
A creepy brown eye
the corner of a baseball card
ET =Et
A key turning in a lock = Turn
Al from quantum leap = Al

So we quickly realized it was something like "Greatness Fades Something Something Eternal"

We threw one at the wall:


That didn't work, so we tried another:


And another:

And another:


We have no idea which was right. Actually, we aren't even sure that we got this point. I'm not sure if anybody got it right, but it's possible that the CM just gave us the point for effort. Who knows. Either way, it was very frustrating to us, because it wasn't all that clear in the pictogram whether we got it right, and once we guessed, we were opening ourselves up to being sniped by another team. I still have no idea what the Eye and the corner of the card are supposed to mean. If the CM wants to chime in to let us know what he was thinking, we'd appreciate that.

5 comments:

  1. "We have no idea which was right. Actually, we aren't even sure that we got this point. I'm not sure if anybody got it right, but it's possible that the CM just gave us the point for effort."

    Pretty much sums up the point for me. :)

    This was in the middle of a "dark age" for us. We clearly weren't clicking as a team ... since the "Three Plus" point, Jim had grown frustrated and had all but withdrawn from this Code, and I was having to force myself to work on anything. I believe "pot-committed" is the correct term. This point nearly broke us.

    Like you guys, I immediately went to YouTube. I had heard of Vine, but had never used it (and certainly didn't realize how popular it is), so it just never clicked. I could say we were 'close', but that isn't fair. With these codes, you can be 'close' in Euclidean space, and still be a million miles away.

    Nice work on this one.

    ReplyDelete
  2. Also worth noting --

    I was 100% sure that the "door" for this point would be 'key.topps.com', as in the 2011 code. This point came out right along with the 2012 Willow Cove point, and another point featuring a 3x3 stack of cards (which I assumed would reference the 2013 Code -- looking forward to the solution for this one by the way). My overwhelming bias toward the topps.com website destroyed my ability to see anything else.

    ReplyDelete
  3. Never heard of vine. Still haven't. ;)

    Also, the pitfall image, all we got from that was "the vine looks like a backslash and the guy is to the right of the backslash".

    See what sort of non-sense you see if you've never heard of vine?

    ReplyDelete
  4. In defense of the CM on using Vine, it's probably at least as popular as Instagram, and a lot more relevant than OkCupid, at least for a bunch of married codebreakers.

    I think for me, I didn't think of it right away because I don't think of it as being a separate thing from twitter itself. And, like Grant, we were convinced for a long time that it had something to do with a previous year's code, and we spent a lot of time trying to figure out things related to yek.topps.com and all other things related to that year's code.

    With the Pitfall image, we were trying to figure out if the score was significant somehow, until we found that same image eventually in a google image search. We also spent a little bit of time investigating brain twizzlers. Interestingly, I drew a connection between losing my mind and twizzling my brain being similar, and didn't connect the grapevine and twizzler/redvine connection that the CM intended.

    ReplyDelete
  5. The endgame on this one was frustrating. It certainly didn't seem like a "when you know you'll know" situation. I tried looking for a quote that this was supposed to mirror but didn't find it. Was there a way to be sure?

    ReplyDelete