Hi,

With oauth you have to make the round trip but I think it works quite well.

What I don't think is going to work well is we will all need to develop an account managment system with new passwords etc and also prompt existing user to now assign a password to their account (which will probably be their twitter password, because users will think we are asking for that.)

The twe2 way of doing it is to ask you to use the oauth "acceptance" process, I.e the part where twitter takes you credentials and you as the user allow twe2 to access your data as the new sign-in process; to login. However, Alex mentioned that is not the use-case for oauth so using it that way may cause problems; it works pretty well though.

Paul



On 1 Mar 2009, at 17:29, Petermdenton <petermden...@gmail.com> wrote:


Say I'm twitpic, does OAuth mean a user is going to have to make that awkward round trip to sign up?

And does recurring login mean apps are going to have to store credentials?

I'm just curious.

On Mar 1, 2009, at 6:19 AM, Paul Kinlan <paul.kin...@gmail.com> wrote:


Hi,

I am still concerned that the introduction of oAuth is going to cause a lot of problems for applications that use twitter username and password as a login and account registration mechanism for their services.

I would like to start a list of the services that primariraly use twitter details as a form of login to their services.

Starting with:
Twe2 (although we do support oauth right now)
Twollo

What I am keen to also get accross is that if we have to introduce a new username and password mechanism for our services I bet that 80% of users will still use the same password as their twitter account, negating the use of oauth.

If anyone wants I can provide you with a secret link for twe2's oauth implementation to show you what we are doing (no username and password - but re-requesting access to your data if you need to login).

I look forward to hearing back and seeing a list of all the services in the ecosystem that use twitter credentials as account authentication and validation so that it is clear the how prevelant the problem will be.

Regards,
Paul


Reply via email to