I thought Apple patched the exploits used by jailbreakme.com ages ago.

Sounds like a great idea, but it seems like NTFS support is still experimental. Has anyone tried this?

Let's see some other custom pages for HTTP errors. I think designers could really have some fun with 410 (Gone), 401 (Unauthorized), 403 (Forbidden), and 418 (I'm a teapot).

Looks like the MobileMe logo went up for auction and Best Buy won it. I wonder if Apple cares enough to bother sending out a lawyer or two.

Plus, if they actually get the television and Blu-ray player connected to the Internet, that's a step or two beyond what most consumers would do. (Of course, being on ./, I'd save my $150.)

2010, the year of that win you First National Lottery of Nigeria, headquartered in an English-speaking embassy for purposes translation. To claim the money, please use our secure website [paypal.com] with your name, address, bank account information, and Social Security number to claim you're prize.

That makes things hard to troubleshoot. Try naming everything after the currently-logged on user. Try looking at IP addresses to track down John Smith's computer. </sarcasm>

My old university/job used a three letter department code, and then the last six digits of the asset tag. You'd get systems like ITS-26301 and MTH-31415.

This is pretty solid, especially because:

1. Machines rarely if ever change departments. Even the laptops. Entire departments can change buildings without issue; sociology moved across campus, and we were like, "Wait, when did you guys get the fuck over here?"
2. The first four digits of any asset tag (in the foreseeable future) are fixed, so just prefix it with 7802 and look it up in the online database (or Mac OS X dashboard widget made by yours truly, for the two other people in IT who have and use Macs) for more information than one cares to know.

Your mileage may vary.

We already have a pi number, though. It's a little more than three.

I knew someone would do this. You bring up ATM machines, PIN numbers, and the HIV virus, and acronyms get no respect.

That's an excellent client-side solution.

In the interest of asking, though, what about a server-side solution? One could use HTTP Accept headers and content negotiation in the HTTP server, if you'll excuse the slight dip in performance. For example:

1. Browser requests /path/to/video.
2. The browser sends the Accept header (or X-HTML5-Video-Accept header, if you want it that way), which contains video/mp4;q=0.9; video/ogg;q=0.8.
3. The server sends /path/to/video.mp4.

Likewise:

1. Browser requests /path/to/video.
2. The browser sends the Accept header (or X-HTML5-Video-Accept header, if you want it that way), which contains video/ogg,*;q=0.1.
3. The server sends /path/to/video.ogg.

Something like that, at least. In fact, were browsers to add video MIME types to their Accept headers, one could implement this yesterday. This solves the issue of codecs, as long as content providers make it available in as many formats as possible.