OAuth.net - Changing Auth Protocols

OAuth is an open source project which is working on developing an authorization protocol for web developers, mashup writers, and API managers to use so that they don't have to compromise their users' passwords. The beef here is that many websites ask for your email or IM password in order for you to say, find your friends on network or print photos, or have access to forums, and the list goes on. This in no way adds to your level of comfort, as your passwords could be recorded, stolen, and used to wreak havoc. OAuth presents an alternative meant to appease all of your worries. Their original goals were to enable Ma.gnolia members with OpenID accounts to be able to use Dashboard Widgets; and to enable Twitter to adopt OpenID as its current API requires the use of a username and password for access. Now they want to give users a sort of Valet key which gives a web service the ability to check your mail, or access your photos, etc., but not hijack your email and send letters to everyone in your address book. It makes surfing the web safer.

"OAuth is an open source project being developed by small group of dedicated individuals.
In developing OAuth, we sought to invent as little as possible, following the Microformats approach to pave existing cowpaths and relying on conventions already established in protocols like Google's AuthSub, AOL's OpenAuth, Yahoo's BBAuth and FlickrAuth and Facebook's FacebookAuth."

OAuth gives developers a means to publish and interact with secured data that's safer and more secure. For those working with mashups, web apps, and the like, OAuth allows you to give your users access to their data while keeping their account safe. It's that simple.

Will web developers adopt OAuth? With all the other major auth protocols out there, how is OAuth going to get its foot into the door?