Aug 31, 2010
How to Deal with Twitter’s Mandatory OAuth?
Twitter is approaching her historical moment on August 31st 2010 when all basic authenticated APIs would be cancelled by official Twitter.com, most app developers have followed official recommendations and switch to OAuth authentication method.
As a matter of fact, sooner or later Basic Auth would be replaced by OAuth,
firstly it is necessary that we understand the features of OAuth:
- Security
Since there is no need to ask for account and password information from 3rd party, OAuth performs much safer than Basic Auth, by requiring a token key from official Twitter site, the optional limits of apps are narrow.
- For Developers
With the help of OAuth Auth, develops will get rid of login errors and bugs. They will be encouraged to develop more awesome apps from now on.
- Access
Under OAuth, apps would receive more APIs as well as 150 more requests than Basic Oauth.
However, in face of this modification, web designers may need undertake the necessities as follows:
1. Deactivating plugins and extensions using old Basic Auth in WordPress and Joomla!
2. Try to use Twitter RSS Feed or Twitter Goodies, which is always recommended offcially.
3. Apply for OAuth Authentication and provide extensions or apps with static login authentication channel.
Maintained by BPOVIA Web Design Team





Recent Comments