On the 30th June the Twitter REST API will stop supporting Basic Authentication and instead switch to OAuth. This means all user authenticated requests to the API must be OAuth signed, preferably using OAuth headers.
If you're a WordPress plugin developer (or less specifically a hacker of any kind) who's playing with the Twitter API, be sure to upgrade your code. There is a number of plugins out there (including mine) that are not using oAuth but just sending login and passwords in HTTP requests because, well, it's just easier for the lazy :Þ
To get you started on the oAuth authentication mechanisms:
- Authenticating Requests on dev.twitter.com
- oAuth libraries in PHP
- and already several plugins using oAuth you could check
Want to share or tweet this post? Please use this short URL: http://ozh.in/rw