I don't know what planet you live on that you can display 1080 full resolution dots using 600 pixels, or 1920 full resolutions dots using 1024 pixels, but given that the Samsung Galaxy Pad (10 inch version) has 1024x600 pixels, it's complete marketing BS to claim it can play "Full HD". It can't even do 720i/720p, let alone 1080. This is akin to the "1080p" stickers on every TV at the TV store, when all those LCD panels are 1366x768 at the absolutely biggest (and most are less than that). Yes, you can decode content that has that many dots in it. Yes, you may even have some nice hardware scalers and fancy perceptual algorithms for de-artifacting scaled images. But "Full HD"?? Time for a class action lawsuit, is what I say.

WARNING

If you leave this unattended...
...you may get this result.

...and by the way, I'm not sure you can say the DNS is "broken" -- it may be in the case of OpenDNS, but I can definitely picture local DNS administrators implementing a staged IPv6 rollout by having some default IPv4 address returned when a DNS query otherwise only yields AAAA records, and then having a host on that IPv4 address that says "Sorry, you can't access that IPv6 site" or something to that effect.

Right. That is a much better test, because it's doing what I suggested: sending an IPv6 packet, and seeing if it gets through. You're still subject to possible shenanigans like traffic filtering which might block ICMPv6 ECHOs but allow TCPv6 through.

Ok.... but without IPv6 connectivity (I turned it off), I type ipv6.google.com in my browser address bar, my DNS lies to me, and my browser magically gets (over IPv4) the google homepage. Using ipv6.google.com in a browser as a test for whether your ipv6 connectivity is working is not a good test. I guess if you're testing specifically for the ability to fetch the bouncy logo from that address, that's one thing -- assuming that bouncy logo isn't available at the ipv4 site that opendns is magically making it look like I'm going to, or redirecting me to, or whatever it's doing (no time right now to sniff traffic and see). But the statement:

makes assumptions about your network and its services (like DNS) which are not guaranteed to be true.

Ok. So it's only ipv6 if your DNS provider doesn't return IPv4 records for it... It's still not a good test for IPv6 connectivity. A better test for IPv6 connectivity would be, you know, sending an IPv6 packet and seeing if it gets through.

...except that it's not:

[craig@Puck:~]$ host ipv6.google.com
ipv6.google.com is an alias for ipv6.l.google.com.
ipv6.l.google.com has address 208.67.219.132
ipv6.l.google.com has IPv6 address 2001:4860:800b::69
ipv6.l.google.com has IPv6 address 2001:4860:800b::68
ipv6.l.google.com has IPv6 address 2001:4860:800b::63
ipv6.l.google.com has IPv6 address 2001:4860:800b::6a
ipv6.l.google.com has IPv6 address 2001:4860:800b::93
ipv6.l.google.com has IPv6 address 2001:4860:800b::67

> The software's main advance is a user-friendly search tool that can scan multiple data sources at once, something previous search tools couldn't do

OMG! Did someone finally discover the hidden "UNION" conjunction in SQL?

...which is why Peak Oil is much less scary from the energy angle than it is from the Haber Process angle. Fertilizers and anti-biotics are far more important to maintaining the world's current population levels and density distributions than any particular form of energy storage.

I hope you dutifully backed up a copy of the HD-wiping virus!

It would sink to the bottom of the soup pot though, so as long as you just scoop from the top, you'll be OK.

So we end up with a computer simulating a human pretending to be a robot, that is disguising itself as a human!

Steps to reproduce at no effort:

1. Go to any hosting provider which uses VMs (let's say Amazon EC2).
2. Sign up for new account, get your root access on your own VM instance on the shared host.
3. Execute exploit; take control of any other VM on the same physical hardware as you.

There, that wasn't so hard now, was it?

This is why I always use blank passwords! Take that, keyloggers!

There's another "use case" too which is not a kernel crash or power outage (well, not in the sense you mean). I have seen many non-technical computer users power off their machines when they're done using them by just holding down the power button until the screen goes dark. Going through the whole "click menu -> shutdown -> wait 10 minutes" routine is too much trouble. And they're not wrong -- why should I sit there and wait for 10 minutes to turn my machine off when I'm done using it?