quartern -
this is a VERY interesting puzzle you ran into!
You were using PHP^, yes? :oops: Its
json_encode() escapes slashes.
It actually took "double whammy" for this to happen - your second mistake was not doing
parse_json() on the downloaded JSON but instead using .shift() & .pop() shenanigans to get rid of the quotes. Which left the \/ inside, something parse would have taken care of.
That's why i am amused by the case, it's a "twofer" that popped in completely unrelated place (base64 decoding).
(^) Friends don't let friends use PHP!
On the other hand, were i in this trade, i would actively encourage my competition to use PHP and MySql...
