Um, NSA can still install malwares onto it. It will be slower and more complex for that to happen.
What about the independent parties?
Traditional companies have made is so going with them is not the long term job security it once was. If there's not going to be security, best to go for the big pay off.
As far as Napster goes, the government hastened its death but I'm not sure it would have survived in the long run anyway. The quality of the recordings was uneven and the peer to peer networking was unreliable. It was at times frustrating to use, and there was no guarantee that you weren't downloading some trojan horse. Somebody would have come along with something better. Just because you're first out of the gate doesn't mean you'll become that standard. Look at myspace.
I think part of the interest in bitcoin has been mining but that's become more and more impractical and other competing currencies have already cropped up.
Until there worth as much as those beenie babies people still think they can get money for on ebay.
It's not the tech geeks that will do this, we'll be happy to have a phone charger and a headphone jack. Or a tablet mounted to the dash, that shares phone data, something that will have a better interface (if sync is any indication, the rental I had with that was like they tried to make the interface suck, 3 layers deep of menu, 2 different areas with the same caption, just to get my bluetooth music to play, oh, and every start, it reset to voice only from bluetooth).
This will be sold so rich non-geeks can have Pandora (or the clearchannel one most likely) radio without effort at all.
The reason touch is so important, is not that it's a better device (though I think it is for web browsing on a small screen that's already in your hand), but because it allows double the screen size. Granted, you can add 20% to phone thickness to get the screen back, and have it giant, chunky, and oddly waited in keyboard mode, or you can give up half the screen for a keyboard.
The iPhone started with the premise "we have the tech to make a good browsing experience, let's find a way to add a phone" (at least that's what it seems like). This was a wacky premise if you did consumer research (it was a solid few years before I stopped hearing complaints about how I want a phone that's just a phone constantly), but it proved to be a clearly superior experience.
Touch isn't the killer feature, it's the enabler of a good screen.
So, what's a good way to protect against password reuse that doesn't cost more cognitive effort on the users than money saved?
Perhaps lock to DoS is too big a problem, though I'd think CAPTHCA a few times could significantly reduce that risk on a large scale (I assume CAPTCHAs still have some use, as I still deal with them regularly, and they dramatically drop comment spam).
Sitename in random part of password is better than not having it, as it should have low cognitive cost, and provide decent protection from password reuse attacks (when coupled with lock-out for bad password).
Agreed, if it weren't for Netflix, I'd drop my cable and just use my phone's hotspot function (2.5 GB free, and reasonable additional use, and all phone based usage is the secret truly unlimited separate cap).
I guess I buy PS3 games too, so it may stick around, but maybe not, $45/month buys me 4GB extra, if I played games online it'd be different though, the latency sucks on my phone, but the throughput is actually faster than Comcast in the evening (I get 20/10 on my phone).
The only real solution to password re-use (site to site) I can think of is requiring changes and making sure past passwords aren't used again.
Perhaps require the site's name to be part of the password (and not at either end), this won't add much entropy, but maybe enough that along with lock-out after a certain number of guesses it could be sufficient.
Two factor authentication, with a different token per site, but short one, around 4 digits, is the only way I can think to have memorable passwords AND site-to-site security. But that introduces it's own issues. Perhaps that plus a long password in a vault (similar to Google's lost my token password).
I read the XKCD linked, and it starts by stating that password entropy is NOT a problem, then goes on to explain why.
I guess what I'm saying is
Non data plans (in the US) have traditionally been allowed to use data without a fee to send and receive MMS.
The problem with an iris I suspect is taking the image of a random iris scan, and converting it to a number in such a way that it consistently gets the same number (in the sense that all data is numbers), but also introduces significant entropy.
You can't just take a picture of the eye, and use that to salt a password over the wire, and if your sending the actual scan of the eye over the wire to be compared, it begins to run into the security issues of a password in general.