RSS acquisition from Twitter will be closed on March 5, 2013


ByBisonblog

It was announced in August on TwitterSet the number of API requests within 60 basic times per hourOperation of Twitter API ver1.1 which revised usage rule, etc. Started from local time September 5 (Wednesday). Receiving this contract changeA client that finishes development as "Twit" appearedAlthough it is doing, etc., it seems that it is likely to have a big influence in the futureXML, RSS, Atom are not supportedIt is that.

New Twitter API Drops Support for RSS, Puts Limits on Third-Party Clients


Twitter announced that it will make API changes from August and earlier, and revealed three major points in August in August. that is

· Approval of all API endpoints
· Adopted rate limiting method for each endpoint
· Scheduling future developers rules, especially related to Twitter clients

More specifically, the number of API requests is basically limited to 60 times per hour (720 times per hour for tweet display and profile display, etc.), and guidelines (guidelines) are "display requirements (to protect It has been changed to "Required)".

It was thought that what was announced at this time would be a remarkable change point from API ver1.0 to ver1.1, but the change found at the final stage is "Abort support for RSS, XML, Atom"was. Since there is a transitional period for half a year from the release of 1.1, at the moment we can get tweets even with ordinary RSS readers etc.Until 5th March 2013It will be. According to Twitter, in the futureJSONSince it is said that it supports only, it is until the 5th of March 2013, which is the deadline of the transition period, that it is possible to acquire RSS with the current API.

Mashable TechChristina Warren has a sense of crisis that this will lead to disappointment of many users.

"XML has been deleted from Web related APIs, and JSON is becoming mainstream"On December 10, 2010PublickeyIt is a preface to the entries posted to, but as I mentioned here, as we have been slowly releasing XML support on Twitter over the past year and a half, it is easy to say "XML support is aborted" It was imagining. However, it is a major change that RSS and Atom support is aborted.

As feeds, RSS and Atom are major output formats. It is often used as a means to acquire posts and podcasts posted on blogs, and Twitter can get tweets with RSS and Atom.

Twitter has allowed developers access to the timeline and search queries using RSS. As a result, RSS has been used for displaying tweets with many aggregators (such as RSS readers). Also,FriendFeedWith the life streaming service like, it was possible to post tweets using RSS as well.

However, with Twitter API ver1.1, all endpoints require OAuth authentication. In other words, if you want to get data from Twitter you can say that you have to use OAuth. At the same time, Twitter explained who is acquiring data and how it is using it because Twitter is to prevent data abuse as a reason for requiring OAuth authentication, It is also possible to control it. According to Twitter, RSS API utilization was low, but it is not clear how many applications were used for data acquisition.

As an example of using RSS, there is a widget installed on a website or blog and displaying tweet streams of tweets and hash tags. Twitter, as an alternative to these widgets, is to prepare a function that can easily embed and install tweets and hash tag streams in the same way. The addition of this function itself is a good thing, but what kind of change will happen to Twitter due to the abortion of RSS support will be obvious unless we wait for March 2013, when API ver1.1 is mandatory not.

In addition, Warren's other concern at the change of the API is "I do not allow output to other cloud services etc. when I used Twitter data (show tweets) with the provided service In that point. In other words, the Twitter client can not post tweets to services other than Twitter. Warren is a social bookmarking service from Twitter clientPinboardYaInstapaperI am wondering if this issue will become a problem in the social news reader service area in the future as I use it to post to the same time.

blog"Book worm", Following the termination of RSS support in API v1.1, it says as follows.

Book worms: Twitter ends with Twitter API 1.1

With the introduction of Twitter API Version 1.1, Version 1 became deprecated. In 1.1, RSS is not supported. Twitter is now completely closed. It is the beginning of the end.

It is very important that RSS is provided. I do not want to check updates manually. I saw Twitter almost through RSS, but I can not do it in the future. There is no reason to do Twitter anymore.

Twitter is finally promoting wicked enclosure. He who has heart must run away quickly.

in Web Service, Posted by logc_nt