Change the rate limit for the recent search endpoint
Please consider changing the current rate limit for the recent search endpoint (v2 API). Currently an app can only fetch a total of 500k tweets in a monthly window, no matter how many active Twitter users it has, or if the requests are per-user. If an app has over 500k active user then there's no way for the app to function correctly due to this limit.
In my case we're offering people to fetch hashtagged posts from Twitter for free, which is very popular for all kind of events, such as weddings and virtual conferences. We're not able to provide this type of service for Twitter if this hard limit is not removed or modified.
A better solution would be to decrease the number of tweets a user can fetch in a 15 minutes window, e.g. 300 tweets instead of 900 tweets in the Standard Basic access.
Another concern with the current limit is that people will be looking for alternative solutions, e.g. using scrapers to bypass new limits.
Hasan Toprakkaya commented
It would be better if the limitation is based on the User level, not the App level.
Tweet Archivist commented
1000% agree. We have this same issue. The fact that the OAuth 1.0a User Context calls get aggregated as part of the 500k limit means that apps can't scale with their user growth, but instead have hard caps. This is pretty much a nail in the coffin for us.