Twitter disabled Basic Authentication on the Twitter API August 31 2010. All authenticated API requests now require OAuth.
OAuth makes a lot of sense for applications that make Twitter API requests on behalf of other users, such as and including SuperTweet.net, which uses OAuth itself. For one thing, with OAuth, the user's password is never exposed to the third-party application or web sites.
However, there are downsides too, especially in cases where we want to write our own apps, using our own Twitter IDs. The original Twitter API was incredibly simple to get started with. Poking around at the API was as simple as running curl on the command-line. However, by requiring OAuth, Twitter lost that simplicity and substantially raised the barrier to entry.
SuperTweet.net is the answer! Simply Sign-up via Twitter to authorize the MyAuth API Proxy SuperTweet.net Application and then assign a password of your choosing (not your real Twitter password) that your applications can use with the http://api.supertweet.net API.
You have complete control. You can revoke your http://api.supertweet.net credentials and you never have to expose your real Twitter password to any third-parties - Learn more.