Is your Twitter client using basic user name and password authentication? If that’s the case, it will stop working on June 30, 2010 — the countdown has begun (nice retro JavaScript animation, incidentally!)
Basic authentication will be switched off in the Twitter API and OAuth will be the only option from that date. Fortunately, there are several benefits to using OAuth:
- you don’t need to worry about storing or accidentally revealing credentials
- user password changes are handled automatically
- there are many other applications which also use OAuth
- there is plenty of documentation and code examples.
Unfortunately, it doesn’t matter whether you’re convinced or not: the OAuth change must be implemented or your Twitter API calls will fail.
There’s no need to panic if you’ve not used OAuth before. Twitter’s developer documentation provides several good resources:
- Authenticating Requests
- OAuth libraries for languages including JavaScript, PHP, C#, ActionScript, iPhone Objective-C/Cocoa, Python and Perl.
- Twitter Development Talk
I suspect the change will keep many developers busy during the next few weeks. Will it affect your application?
Craig is a freelance UK web consultant who built his first page for IE2.0 in 1995. Since that time he's been advocating standards, accessibility, and best-practice HTML5 techniques. He's created enterprise specifications, websites and online applications for companies and organisations including the UK Parliament, the European Parliament, the Department of Energy & Climate Change, Microsoft, and more. He's written more than 1,000 articles for SitePoint and you can find him @craigbuckler.