No, he's saying it reduces the chance your finger will overlap 2 keys, which is true. By adding triangular dead space between keys (and by staggering the rows of keys), the design does this. However, as far as software is concerned (on most devices), your finger IS an single pixel, placed at the point where the touchscreen thinks the pressure is greatest.

Now, considering that the error in one's ability to aim tends to be circular (it's equally easy to miss by 1cm in any direction), these keys ought to be round and staggered.

This is exactly what the Maemo version of xkbd has been doing on my N800 for a few years...

(what happened is Slashdot 2.0 is smart enough to auto-terminate my <em>!)

Hmm, they fixed it now... Anyway, the problem seems to be Slashdot 2.0's too-long-title-chopper. The original title:

Nintendo Announces New <em>Mario Bros</em>, <em>Mario Galaxy</em>, <em>Metroid</</a>

It chopped off PART OF an </em> tag!
(just seeing what happens of I put an unterminated <em>...) -->

Probably easier to stick a small camera on a trained, live vulture...

Oops, formatting problem on that post...

>Thus, the fact that you did not return the program within a reasonable period operates as powerful evidence that you accepted the EULA.

Or possibly just that I had to OPEN the box to read the EULA, and no store will accept returns on opened software.

>Thus, the fact that you did not return the program within a reasonable period operates as powerful evidence that you accepted the EULA. Or possibly just that I had to OPEN the box to read the EULA, and no store will accept returns on opened software.

Secure data destruction could also prove interesting, if you follow today's standard of destroying the medium it's on. Time to replace those hard disk shredders with atom smashers!

As I recall, you would need computers about a trillion times more powerful than today's fastest supercomputer in order to break AES. So it'll be quite a while -- at the very least, you'll have fair warning and more than enough time to migrate all your data to a new, better encryption technology and/or shred it.

The other possibility is if a major flaw in AES is found. This can be handled by encrypting the data using multiple ciphers, say AES+Serpent. If one of them is broken, re-encrypt the data with a different pair of ciphers.

>unless you assume access to some yet-publicly-unknown method of cryptanalysis

Rubber hoses come to mind...

But then you don't get the wobbly windows. What good is any of this without wobbly windows?