The new OAuth authentication

As some of you might know, since March 09 Twitter stopped accepting new app registrations for the old authentication APIs. Now every new app must use the OAuth protocol to authenticate users, this means that now you authenticate directly with Twitter and not with the third party app.

What does this mean?

  1. Better security: since third party apps don’t have access to your login information it is less likely you’ll have security issues outside of Twitter. Most people use the same password in all or most of all services and making them more vulnerable to attacks. The only data exchanged between Twitter and your applications are access keys to allow access to your account.
  2. Worst user experience: the increased end-user security results in a worst experience since now you need to go to Twitter’s webpage to allow access to that app and then return to the app. After that the app can store your access keys with less risk for you.

Since Switter was registered last month we’ll be forced to use OAuth, you’ll have a slightly less good experience but you’ll be much more secure.

You can find mor information about OAuth here.

, , , ,

1 Comment

Welcome to Switter Dev Blog

Hi, my name is Bruno Silva and I’ll be your host for the next few months as we go through development of Switter. I don’t want to spoil anyone with much details, but Switter is all about great experiences turning your everyday tweets into pure fun!

Stay tunned, a beta should be coming in a few weeks.

1 Comment