T-Mobile doesn't carry the iPhone in the USA as far as I know, so I don't know where the phone actually originated from. Am I wrong that a US T-mobile IMSI wouldnt unlock it, if they don't sell the phones?

A health club for CEO's maybe?

Good humor, met with a stone cold literal reply. Well played.

I think he just has a huge head.

Out in the middle of the ocean, it would take more impact on the environment to tow it than it would be to sink it with fuel on board (A tugboat pulling that much weight for that many miles would pour so much exhaust in the air it would outweigh the effort).

To those comments saying the chances are lower because more people are playing: Let me remind you that it's not a raffle, it's a lottery. Even if nobody played except for you, your chances of winning are just as slim. Now, buying multiple tickets with different numbers does change the odds slightly.

I googled it. I didn't click any links, but from what I read from the results page, it's some sort of cheese.

" an Infinity Blade II session while plugged in" apparently.

If the article is talking about the glasses he's wearing in the picture, those don't have lasers. They're LightSpecs LED reading glasses. I was given a pair by Dick DeBartolo (whom looks oddly close to the man in question).

I liked them before it was cool, now I think its dumb.

I bought 2 ipad2's last week, knowing there was a new one coming out... Of course it was because I got them at the $399 pricetag after my discounts including a few accessories, but still.

You're welcome.

That means it is off already, as mine is.

Simpsons win. +5 points.

I don't point out mistakes usually, but this post is unreadable until I can trust any of the numbers in it.

you use the therm 'information' rather loosely.

I've seen some legit levitation like this, but it is nowhere near that fluid of a motion. And the video has way too much CG vapor in it that it's hard to see exactly how much of it is faked.

Here's my boilerplate response:

That's what I thought too. But then I realized that the issue probably started with Android 1.6, and the case was most likely launched when 2.2 was the newest version. There is nothing to fix unless this is the case.

Wait... is this Geekologie?