Twitter API Lead Alex Payne has just tweeted that OAuth support for third party applications is now in public beta. Support for the authentication protocol has been frequently requested for many months, and was finally made available to a limited number of developers last month.
OAuth allows developers to create third party apps that can access a user’s account information without requiring them to hand over their login credentials. Before now, Twitter applications have required users to enter their usernames and passwords. This typically hasn’t been a problem (and most users haven’t seemed to mind given the vast number of popular apps using the Twitter API). But handing third party developers login credentials, and in turn full authorization to access and store a user’s account information does open the door to abuse, should something happen down the line that exposes user data. OAuth removes some of this risk, though users are still potentially open to phishing attacks.
looking forward to this getting integrated to many client apps.
finally some credibility boost for developers, more signups to come…
TechFilipino
Well it’s about time! This is great news for developers.
@Francis +1
Sweet!!
was OAuth suppose to link to somewhere? cause if so, the link isn’t working.
Yep, had a typo. Fixed now. Thanks for the heads up.
You can try Twitter OAuth on Tipjoy for twitter payments: http://tipjoy.com/twitter
It’s about time.
I had been wanting this ever since there’s 3rd party Twitter services.
I hope developers will take the time to incorporate this over other improvements as soon as possible. I had been reluctant to try many of the 3rd party services due to their requirements of me to provide my Twitter credentials.
This is great news!!! Lots of buzz about OAuth lately. Excellent!
Its about damn time!
This one is a great news! We have been waiting for this feature to integrate funpiper.com with twitter without users really sharing their login credentials. Kudos and thanks to Twitter team!
“has been frequently requested for years”… Well if the OAuth Core 1.0 final draft was released on October 3rd, 2007, then that would be over one year ago. Not even a year and a half ago… So if it’s a spec that’s not even 2 years old, then it’s really a stretch to say that is has been requested for years… Requested for many months maybe.
Its about time that Twitter must embrace OAuth, it will allows developers or third party to create third party apps that can access a user’s account information without requiring them to hand over their login credentials. This could be a breakthrough for twitter developers. But Twitter must take serious about opening its door to third party developers.
But one of the issue is that OAUth won’t work correctly on constrained device (typically mobile) as it usually require browser interactivity.
Tha’s one of the reason why Facebook release his cocoa library, to bypass browser limitation
So it’s half a good news
Twitter oAuth support is working great. We’ve already implemented it in our beta site for TimePoke: http://1.latest...ev.appspot.com/
http://www.timepoke.com
Finally Twitter, Geez Louise.
Is anyone else having trouble registering an existing Twitter application for the oAuth? Also, their example application in the documentation does not work.
Was told today by Twitter support that OAuth for existing apps (mine is http://krumlr.com ) would be rolled out gradually and that there were still many issues with which to deal.
http://twitterfall.com rolled out an oAuth implementation today after receiving word that it was in public beta. It was ready yesterday but Twitter were having replication issues with their ‘oAuth client’ configuration stuff. Pretty pleased with it