Why Your Social Website Should Support OpenID
2008 April 12
On Twitter I bitched about GitHub not supporting OpenID, and both Chris Wanstrath and Giles Bowkett chided me for not making an better argument for it than “it makes my life easier”. Â The benefits of OpenID seem self-evident to me; but if I have to spell it out, here goes.

This work, unless otherwise expressly stated, is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 United States License.
When I go to a site that supports OpenID:
Â- I don’t have to spend even a millisecond wondering about how good their password security protocols are. With OpenID, they will never see my password.
- I don’t have to weigh whether to use one of my standard web passwords.
- I don’t have to make up a new password and remember to write it down somewhere.
- I don’t have to use some 3rd-party program or Firefox extension to generate and manage random password, only to be locked out when I have to access the site from a public terminal and my thumbdrive is in my other pants.
- On many sites, I don’t have to type in my name, email address, and zip code for the hojillionth time, because they are automatically fetched via OpenID.
- Lastly, if I ever decide that I made the wrong decision about my password policy, I don’t have to remember and revisit the site in order to change my credentials.

This work, unless otherwise expressly stated, is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 United States License.