[sondh]

I think this is a step backward. The OAuth specs were designed to make it easier to work with different services and now we have to utilize yet another service to communicate with those services?! Via a priority protocol even!

As a developer, I understand the pain when you have to deal with more than a handful of providers but this approach is a no-go IMHO. Would be a better idea to use something like HybridAuth and handle everything from your servers.

Relevant xkcd: http://xkcd.com/927/

Apology to OP if this comment appears to be offensive.

[nadiac]

Oauth has been made to avoid to store passwords, but it is not a simple protocol to implement. I just think you are talking here about the main debate between protocol versus applications/platforms.

- Protocols provide standardization, and independance, often as recipe/instructions to follow. Protocols keeps things open, into nodes not hubs.

- Applications/platforms provide easy comsumption, with a user design but also dependancies. It is like a menu to order, as you choose what you want to eat but you don't have to care about how to do it (the recipe). They mutualize things as code librairies, CPU etc... but are hubs, not node and close the network in counterparty of user experience.

To see in depth the difference of design between a recipe and and a menu, more explanations in the Donald Norman book " The Design of Everyday Things"

Edit: To see the difference between a protocol and an application, why people are using Gmail instead of STMP? User experience vs implementation