Last week you may remember Twitter planned to enable the new Status ID generator - 'Snowflake' but didn't. The purpose of this email is to explain the reason why this didn't happen, what we are doing about it, and what the new release plan is.
August 31, 2010
Basic Auth has been deprecated. All applications must now use OAuth.
Don't fret! @twitterapi is here to help! Feel free to reach out to us directly, or via our Twitter Development Talk group.
The switch to OAuth is a good thing! You, as the application developer,
- don't have the burden of keeping potentially damaging credentials for your users (especially considering that a lot of people use the same password for multiple services);
- don't have to worry about the user changing their password — a user can change his or her password and the OAuth "connection" to your app will still work;
- don't have to worry about other applications masquerading as your application as only your application can set the byline with your application name;
- will eventually have access to more trusted APIs from Twitter that will only be available to "trusted" OAuth-enabled applications; and
- will be contributing to the web of trust between users, service providers, and applications.
Choose your authorization path.