News for hackers. Stuff that matters.
Re:The Dirty Truth About Web Passwords by dholowiski on Tuesday December 14, 2010 @11:04AM (#2004545)
While I do agree with the sentiment of the article, as a developer I see it as a risk to hand over user authentication to a third party. Once I do that, I'm subject to their terms of service (which usually say 'we can do anything we feel like, any time we want'), their outages, and their bad business decision (What happens to all the Facebook connect accounts when Facebook goes bankrupt?).

Would I even trust Google to handle Authentication? Maybe, but remind me again how I contact Google Tech Support when my authentication mysteriously stops working?

On the other hand, I had left comments on Gizmodo using Facebook Connect, so from a user perspective it worked out well for me.

Re:The Dirty Truth About Web Passwords by andreyf on Tuesday December 14, 2010 @12:49PM (#2004979)
What happens to all the Facebook connect accounts when Facebook goes bankrupt?

Government bailout. Too big to fail.

Re:The Dirty Truth About Web Passwords by JeremyBanks on Tuesday December 14, 2010 @12:53PM (#2004997)
OpenID delegation is useful for this purpose. If you have any domain you can use it as your OpenID and specify it to delegate the actual authentication to another service provider, that you can change at any point. I used to use MyOpenID, now I use Google, but it's the same login.