On August 31, the Twitter API team will shutdown all basic authentication on the Twitter API. If you are using any of the third-party Twitter-based applications that uses basic authentication, the application you’re using will no longer work as of August 31.
Twitter has given developers enough warning of the switch. In fact, Twitter has postponed the cutoff date at least twice in the past few months to accommodate developers into adopting the OAuth authentication protocol. This time, the cutoff date will most likely stick. What this means is there will be a number of applications that will no longer work after the deadline.
How does this affect you? If you are a WordPress user and you are using a Twitter-based plugin that requires authentication, there is a good chance your plugin does not use OAuth authentication. There at least 250 Twitter plugins written for WordPress. A number of them do not require authentication, but some require authentication.
If your plugin requires authentication, better check.
One way of finding out which plugin uses OAuth is to check the plugin’s Option pages. If you’ve entered your Twitter credentials such as username and password, then you are using the older and soon to be obsolete basic authentication.
If you’ve entered a consumer key and a consumer secret key, then you are using OAuth authentication protocol.
Another way of finding out if your plugin uses OAuth is that the login process should take you back to the Twitter’s login page such as the example below.
To be sure, check for updates of your plugin. If the developer does not plan to update the plugin, better start looking for an alternative.
I didn’t get a chance to look at each plugin because of the sheer number of Twitter-based plugins in the Plugins directory. One plugin that supports OAuth is Twitter Tools.