So I saw this on mashable.com awhile ago, and was wondering what bug caused this.  But I'm too lazy to do some timestamp math and see if I can get the same weird answer displayed on the page.

I thought I also had one from Netflix that involved an incorrect content-encoding like the classic smart/“real” apostrophe problem (see “Garbled Tweet”), but I can't find the screenshot.  I think it actually involved the word “über-spy” and the umlaut being messed up.  Ah well.