Oh! Hello. This is my thing I made for usvsth3m.com. Hope y'all like it. HTML5 Webworkers made it possible - sandboxing user-submitted JavaScript so an accidental while(1) or document.write can't kill everything.

Do have a look at the source code. Oh, and try turning up your speakers and typing in the Konami code...

Oh, you, Tom Scott, made it? :D I'm a big fan.

A few suggestions, then:

1. Don't use i as the name of the parameter. A lot of people use that as the name of loop variables, and it means breaking habit or wasting time changing the name.

2. For test 3, try some multiple-extension files to make sure they did it right (some.file.multiple.extensions, should return "extensions")

3. For test 5, it says "integers". Try some non-integers during testing, to make sure that it's only checking for integers.

4. For test 5, it says "arrays". Try some objects to make sure they're not being lazy and using typeof thing === "object"

Anyway, thanks for making this. I love it!

If you alert() something inside an infinite loop it doesn't seem to be able to detect it (nor does it show an alert box!)

Nothing like figuring out another way to kill your browser :)

Hello. I'm Tom, and I made this -- more than three years ago. No idea why it's suddenly turned up here; it doesn't exactly fit under 'hacker' or 'news'!

It did once have permalinks, but adding translations in 2010 messed things up and I never got around to fixing the code. (Do try picking a RTL language, though, I'm quite proud of how that works.)

It should (I think) store the city you've requested in a cookie for next time, though. Maybe. It's really old and dodgy code.

Still, full marks for YQL for putting up with all the weather requests they've gotten over the years...

Interestingly the Hebrew version prints Dagobah as Dagobash (דגובאש), and apparently Johannesburg, SA doesn't exist as a city.

+1 for permalinks as well, it would make sharing this with others a lot easier.

This is really awesome! Not hacker, but really geeky :) Is there any chance of you cleaning this up and fixing permalinks?

Hello there! I'm Tom. I made this. I didn't expect it to go this far. A few notes for you, which I've also added to the original site:

Yes, I'm aware this is pretty meaningless - my original tweet was "Not sure if it's net-art or just a load of guff." It seems to have sparked some discussion, though.

No, I'm not selling the books. I try not to create too many useless physical objects. If you're hell bent on it, or want to see the full text, I've uploaded all the source files and there's a link at the bottom of the page. I ask that you don't sell anything you make with it, although given I'm ripping off Shakespeare and the JPEG algorithm that's probably a bit rich.

If anyone wants to commission a professionally bound hardcover set for some net art exhibit, let me know. I'll happily pretend to be a serious artist.

A bit of explanation: @iamdanw came up with this idea about 24 hours ago, and it was constructed entirely over a 3G connection in that day. It's shown up a few interesting issues with Amazon Lockers - including that items which don't have a confirmed size in Amazon's systems show up as being "too big". That's taken out a lot of our 'trinket' buying options...

Got encouraged to submit it here as it sort-of qualifies as a hack on top of a service that wasn't really designed for this sort of thing...

Hello. I'm the guy who put this collection together. I've since tried to update it, and to hit 'delete' on it to avoid spreading misinformation, but Exquisite Tweets is still caching the original version. Mea culpa: I didn't do the research before passing it on.

There's been a lot of back-and-forth over whether it's true or not (check @pof's timeline for such), and a hell of a lot of people sending it on without double-checking. Myself included.

There is clearly a big security bug here (see the video linked), but it's extremely questionable as to whether it can be activated from a web page or whether it requires a bit of social engineering too!

[Edited to add: and just as I write this, @jwheare has cleared the cache and fixed the bug in Exquisite Tweets. Hopefully that should nip this in the bud.]

I tried reproducing it using a "USSD" that works on my venerable Nexus One (radio debug - * # * # 4636 # * # *), but on entering dialler app the input box is empty. This might simply mean the debug activity was started and got focus before the dialler app had its focus set, so if another such code triggered factory reset, might definitely still work.

I wrote a trivial webpage (using the show IMEI USSD * #06#), served from my desktop with Lighttpd. It certainly can be executed via a simple web page using a frameset on both Chrome & Browser, and there's no prompt. Works on a Huawei running 2.3, a Galaxy S2 running ICS, and an HTC.