3 ms·

So if you're making a small site as a side project, is it worth integrating Openid? I'm assuming here you can't get away with the StackOverflow approach of req

So if you're making a small site as a side project, is it worth integrating Openid? I'm assuming here you can't get away with the StackOverflow approach of requiring all users to use it, so you still have to manage passwords for some users, anyway. As an end-user, I think I'm at the point where I'd prefer to use something like OpenID for new accounts. (I wasn't using it for HN, and I lost my password about a month ago, so now I have this account linked to gmail.)

mtrichardson 17y ago
Depends on how easily it is to integrate into your project. For instance, for Django applications, there's django-openid-auth (see http://blogs.gnome.org/jamesh/2009/04/14/django-openid-auth/ http://blogs.gnome.org/jamesh/2009/04/14/django-openid-auth/ and https://launchpad.net/django-openid-auth https://launchpad.net/django-openid-auth ) and Simon Willison is almost ready with his new plugin at http://github.com/simonw/django-openid/tree/master http://github.com/simonw/django-openid/tree/master . These plugins are just drop in and go for the most part. When you have tools like this, seems worthwhile to do so.
wmf 17y ago
I think OpenID is great for small sites because you probably can't afford to do password security correctly so using OpenID is probably easier and more secure.
- evgen 17y ago
  Since both OpenID and secure logins for small sites are but a plugin away for the frameworks that such sites will inevitably use this assertion just does not hold water. Given the fact that the two are roughly equivalent for the server provider (albeit with an increased number of potential failure points for the OpenID system due to reliance upon third-parties for authentication) the determining factor should probably be usability. On this point OpenID fails miserably.

3 ms·

So if you're making a small site as a side project, is it worth integrating Openid? I'm assuming here you can't get away with the StackOverflow approach of req

by csbrooks 17y ago

mtrichardson 17y ago
Depends on how easily it is to integrate into your project. For instance, for Django applications, there's django-openid-auth (see http://blogs.gnome.org/jamesh/2009/04/14/django-openid-auth/ http://blogs.gnome.org/jamesh/2009/04/14/django-openid-auth/ and https://launchpad.net/django-openid-auth https://launchpad.net/django-openid-auth ) and Simon Willison is almost ready with his new plugin at http://github.com/simonw/django-openid/tree/master http://github.com/simonw/django-openid/tree/master . These plugins are just drop in and go for the most part. When you have tools like this, seems worthwhile to do so.
wmf 17y ago
I think OpenID is great for small sites because you probably can't afford to do password security correctly so using OpenID is probably easier and more secure.
- evgen 17y ago
  Since both OpenID and secure logins for small sites are but a plugin away for the frameworks that such sites will inevitably use this assertion just does not hold water. Given the fact that the two are roughly equivalent for the server provider (albeit with an increased number of potential failure points for the OpenID system due to reliance upon third-parties for authentication) the determining factor should probably be usability. On this point OpenID fails miserably.