It's not ironic at all. At 35 feet viewing distance, a 120" 1080p HD image is indistinguishable from a 120" 480p standard def image. It all has to do with the distance at which the eye loses the ability to sort out an individual pixel. Since you're normally viewing your phone from less than 12 inches, and your 40" TV at 10 feet, even if they have the same number of pixels, the TV probably has better visible pixel density.

http://s3.carltonbale.com/resolution_chart.html

From the Charlie Miller interview mentioned elsewhere in this thread...

Another question from the Twittersphere: What OS/browser pairing to you use? Do you do anything special (beyond default settings) to secure yourself while browsing?

You're not trying to pwn me are you??? Have you ever heard the saying about the cobbler's kids not having shoes? That's me, I'm afraid. I use Safari on OSX with no special settings. This isn't the most secure combination, by any stretch of the imagination, but I like it. It's designed by Apple engineers to be easy to use and 'just work' and it does. The risk of malware is low, and hey, I'm a security expert right :) The risk of a targeted attack is real, except I don't think I'm important enough to be targeted! So I rely on security by obscurity, I guess

Well, Me, for one. Try squeezing full raster 10 bit HD-SDI through an ethernet cable in real time. 3Gbps != 1Gbps. Fiber channel on the other hand...

I use a similar method, but then apply an additional layer of obfuscation by putting my password that I've generated with my algorithm through something like an MD5 hash. If I can't remember the password, I can always recreate it, but the chances of anyone stumbling across it with anything other than brute force are miniscule. You could even write your passwords down and it wouldn't make a difference. All you're giving them is the seed. You can also apply simple encryption to them, such as having a deviation pattern from the password you've written down (i.e. first character is to the left of the one I've written down, second one two characters up on the keyboard, etc. I've also had success just keeping a list well hidden such as making a file called .nothing_interesting_in_here (for example) and hiding it down in /var or /etc somewhere. The chances of some miscellaneous laptop thief getting root and going ls-la through all of your config directories is relatively small. You just have to remember where you put the file.

We actually did this on a network that I ran for a while. Servers were birds of prey (kestrel, hawk, eagle), internal servers were flightless birds (kiwi, ostrich, etc.) Mac workstations were waterfowl (mallard, egret, swan, flamingo), laptops were rodents (rabbit, woodmouse, groundhog), fileservers were large herbivores (rhino, hippo, etc.) Linux workstations were types of deer and related species (ibex, impala, moose) and I reserved the entirety of aquatic invertebrates for naming Windows workstations (cuttlefish, octopus, squid, sponge, sea_cucumber) but that might just be personal prejudice. The other aspect of this that worked nicely, is that I reserved names for various floors in the building or remote locations for different geographical areas, so I knew that hippo was a fileserver on the 2nd floor of the main office (Africa) while bison was a fileserver on the 1st floor (North America). This requires a bit of pre-planning since you are allowed more linux workstations in Africa than in South America, but on the plus-side, almost all of those names are your spellchecker, and a lot of them, people have actually heard of which mean fewer errors and questions. It also gives you a simple way to physically identify the host -- I put little pictures on the cases.