We have to be careful about the articles we publish on TDWTF. We have a responsibility to our submitters, to protect their identity and anonymize the details of their stories. We have a responsibility to our readers- mostly to be entertaining.

Last weeks JSFk story failed one of our readers. Poor Blazej didnt find it entertaining- it gave him upsetting flashbacks to his own experience with a similar event.

You see, Blazej was pitching in on a file uploading site, specifically meant to share videos. While he did some backend work, the front-end developers wanted to make sure that it was impossible to ever learn the actual URL of a video, to prevent people from downloading it. They wrote some JavaScript to obfuscate that URL, but that introduced a new problem: somebody could just read their JavaScript!

Using the same principles as JSFk, but coupled with JavaScripts unicode support, they produced this:

http://thedailywtf.com/articles/javascript-obfuscation