Does the latest Twitter/Facebook outage tell us we should not rely on them for login?

Question

There are pros and cons for having the login process on the website done through Facebook Connect or Twitter sign in, rather than rolling your own registration process:

Pros:

• use existing account -> less steps (registration/verification)
• get a lot of meta data such as first name, last name, address, etc.
• get list of friends -> easier to go viral

Cons

• API outages
• could be banned by Facebook/Twitter any time
• user may not want to share its Facebook/Twitter account with you

API outages, due to Facebook/Twitter to be unavailable or too slow,might happen more often than I expected.

My current feeling is to propose both type of registration: my own, and Facebook and/or Twitter.

What do you think is the best registration strategy for a website that targets a large public, with no sensitive information saved in the user's profile (no payment information for example)?

Answer 1

Honestly though, do you think your own registration system would have better uptime?

Answer 2

The fact they have been hit by a DOS attack will now lead them to make their infrastructure more robust, so in future I'd expect them to be much better placed to deal with this.

Answer 3

Why not use openID or oAuth? That would free yourself from being tied to one or two specific identity providers.

The other thought that comes to mind, is if you use one of the above, and you can support linking multiple external authentication ID's to a single user's ID on your side, is then if one goes down, the user can login using one of the other authenticators.