Robby
Helper Bot
Twitter has recently announced the Twitter API 1.1 changes. The changes to be included in the API have been mostly overshadowed by the also recently announced changes to restrict 3rd party Twitter clients. Developers though should be aware that the API changes may have a severe impact on them.
The most obvious change is that Twitter is killing its RSS, XML, and ATOM feeds. That means that any functionality using those feeds, like managing them in FeedBurner or being able to easily display the feed within your own application, will no longer be available. JSON will remain as the only available feed format.
Those of you whom are already using JSON at this point might be pretty happy. Unfortunately there is another change coming. All access points with the 1.1 API will be required to be authorized using OAuth.
Between connection limits from 3rd party clients and the upcoming API changes, Twitter is quickly changing their ecosystem to be a closed sandbox.
Links
The most obvious change is that Twitter is killing its RSS, XML, and ATOM feeds. That means that any functionality using those feeds, like managing them in FeedBurner or being able to easily display the feed within your own application, will no longer be available. JSON will remain as the only available feed format.
Those of you whom are already using JSON at this point might be pretty happy. Unfortunately there is another change coming. All access points with the 1.1 API will be required to be authorized using OAuth.
Between connection limits from 3rd party clients and the upcoming API changes, Twitter is quickly changing their ecosystem to be a closed sandbox.
Links