Hacker News Reader

Comment by myoung8 | Hacker News Reader

erik, maybe you should give them a clue where to start...

it's 500 bones brosuf...i can't just give it away. I will add some more clues next week.

Given that people on HM should be fine with decoding from base64, we're trying to break this code:

    @(2=(!+Y0NTI;C+U;Y-LV,(73*DP#P&3FNS.#%<O<)H3O4=-DX;FE(&:-'40
    #?)%AB8;P#@2<!ZNCSS$?=H*7EJ,!"ULVF:6IF'J "2GFT*FH,>40*W(T @-
    Y5LF$32/#"#.?!OWI429U;$2LS8VH/A+QZF7HI0(;*#9EJ<G%->?LS<6HE&V
    5Y/;I.3TD%I*2O?K>-?-IGN?Z38WH T?-SBTD1A0*/2WN35UJ1CN64/=4:79
    RFAJC2S,@;-90 9+"W%T:)6ILRI/JB'"$D%".HNI6I+$C(.*WA.;>*MX?;*L
    S;@11K/2<EO>UW-;4>4GHEL&

I'm trying to make sure I'm seeing the correct things.

the reason i base64 encoded it is that wordpress was trying to be smart and changing characters for me...which in a coded message is...not a good idea.

I'm aware of those problems, however I'm trying to confirm if the above is the same as what I should be trying to decode. It's a waste of time to decode the wrong string.

I get the same thing FWIW (using python's base64.decodestring.)

Just a note, this is not correct. It is the result of having spaces in the string from the line breaks.

See https://gist.github.com/747869

I gave some clues of sorts in the comments.

Reply on news.ycombinator.com