Could you please *translate* the rate limits into the modern day equivalents: 400 keywords, 5000 screen_names... it looks like you are crippling the API
This Tweet is unavailable. Learn more
Conversation
This Tweet is unavailable. Learn more
This Tweet is unavailable. Learn more
👋 ! To translate: limits are at the Tweet level only. You can stream up to 500K Tweets/month (up to 50/sec). Rules are separate, so you can use as many keywords as you like as long as their length is less than 512 characters. But wait, there’s more!
2
2
The Filtered Stream preview will introduce a much more powerful set of operators than statuses/filter, so you will be able to filter beyond just screen names or keywords. Check out , we will soon share more deets about this upcoming preview!
2
4
Ok, 512 characters per rule multiplied by 10 rules equals 5,120 characters in total. I currently follow 5,000 screen_names and 400 keywords. It appears that I won’t be able to pull the same amount of data under the new implementation. Is that correct? Cc:
1
1
It looks like they're putting a hard cap on the total tweets per month when before the cap was 1% of the firehose level for the filter stream. If I understand this correctly, this is a HUGE reduction in the amount of data researchers could get with filter streams.
1
5
8
As of right now, you could get millions of tweets per day with the filter stream. If they change it to 500,000 per month maximum, that limits it to ~11 tweets per minute on average per month.
So it looks like they're crippling the filter stream.
1
3
5
Indeed. I’m more concerned about the inability to follow 5,000 usernames and 400 keywords. These numbers have remained static since Twitter first released the API, even though the data stream is now 1,000x larger. So yes the API is being crippled.
1
1
2
It also looks like they may cripple the search endpoint.
Those limits only apply to the Labs version, and are not meant to reflect a potential future state. Remember, Labs allows you to test things before we release them to the general public; it also helps us understand feedback like this.
4
7
We do listen to the needs of the Academic Research community. That’s why we have a dedicated feedback channel:
twitterdevfeedback.uservoice.com/forums/922918-
1