Changes in the new version of the Twitter API will affect all

Published release of the new version of the Twitter API (v1.1), in accordance with which we must bring our applications within six months. The most important concern has not been confirmed - the 100,000 barrier will apply only to applications that copy the basic functionality of official clients (eg, Tweetbot, Echofon, etc.). However, the rest of our terrible fantasies come true.

Their short review Further.

Increased request rate limits

Previously, the limit on the number of requests from one token (user) was 350 requests per hour, but now everything has become much more interesting.
First, the time intervals are divided not by 60, but by 15 minutes, and in each 15-minute interval only 15 requests are allowed to most methods (one per minute). The exception (180 requests / 15 minutes) consists of the following methods:

• GET search / tweets
• GET statuses / oembed (by the way, this method can no longer be called without an application)
• GET statuses / show /: id
• GET users / lookup
• GET users / show

And everything? Yes, that's all. All other methods you can call no more than 15 times in 15 minutes . Thus, we are aggressively encouraged to use the Streaming API .
')

Only json

Twitter API v 1.1 no longer supports XML, Atom or RSS due to its low demand.

All requests - only with the application

Now all requests to the Twitter API must be accompanied by authentication information in accordance with OAuth 1.0a. At the moment, all requests require a custom token, but within a few weeks support for authentication “in the context of the application” will be added - this is a type of requests that do not include the user token, only information about the application (for example, the aforementioned oembed or tweet search) .

Updated section of the Rules of the Road

A section that includes information for developers on what is possible, what is impossible and what must be done with content from Twitter. Short squeeze:

• When displaying tweets, you cannot change the content, change the names of actions and the essence of the actions themselves (replays, retweets, favorites, etc.).
• If you have more than 1,000,000 users, welcome to the negotiating table. And nothing else.
• Traditional twitter clients with more than 100,000 users - we are watching you.
• Never surprise users.
• Do not distribute content from Twitter. If your application stores any data from Twitter - you cannot transfer it to someone else, post it on other cloud platforms.
• Do not spam.
• Respect user privacy. Do not post publicly “private” content.
• Do not try to cheat the limits on the frequency of requests. Rules are rules.
• If you are advertising, make sure that it is clearly separated from twitter – content.
• No more than one application per service. No more than one service per application.

Recommendations for the design of steel requirements

There are a lot of points here. In short, tweets should look like they appear in widgets and almost nothing else. I recommend to get acquainted with the full list of requirements .

Changed default settings

The include_entities parameter is set to true by default (all information about links, photos, hashtags and videos comes with a tweet).
The include_rts parameter is set to true by default (retweets have appeared in the tapes).

I recall that version 1.1 will be the main March 5, 2013 . Time has gone!