Facebook Connect vs Twitter Anywhere vs OpenID for third-party login/registration system?

Question

We want to streamline the user registration and login process. The goal is to reduce the time and effort for users to register and login to our site.

At the same time, we don't want to overwhelm users with choices. We don't like how some web sites present registration/login options via multiple channels (e.g., Facebook, Twitter).

What are the pros/cons of each of these systems? Which do you use, and what are your main gripes?

Answer 1

Offer all of them, don't take the time to ask "why?".
It's always worth it to get users on board.

Answer 2

The biggest (IMO) pro is that you are no longer storing passwords in your db. Leveraging one of those other site's authentication service relieves you of this. It doesn't relieve you of having a secure design. I'm also not sure that your average end user really cares. If your service is highly aligned with one of those services, maybe. However, if you are not targetting those end-users, then probably not.

Rob Conery did a recent write up of his experience with OpenId. This might be a good read:

http://blog.wekeroad.com/thoughts/open-id-is-a-party-that-happened

Hope this helps.

Bob