Please ease the restrictions on getting their own friends/followers data.

Twitter's API restrictions are getting stricter every year, and starting with Twitter API v2, I understand the data that users will be able to retrieve via the API will decrease by 80%.
Previously, with a single API call, users could retrieve 5,000 friends (or followers), but in the future, users will only be able to retrieve 1,000 friends (or followers). https://developer.twitter.com/en/docs/twitter-api/users/follows/migrate

I understand that this decision has been made from the perspective of sustainability of the service, but please reconsider restricting users from controlling their own data.

As one solution, how about separating the rate limits for when users retrieve their own data and when users retrieve other data?

Enable creation of dedicated "bot" accounts, solely for posting tweets or other automated activity. These would display with a 🤖 robot emoji by the name (instead of a blue checkmark) so they are easily distinguished from regular users.

Self-selecting into the "bot" category could come with a different, more restrictive set of permissions - no web login or posting (OAuth only), cannot Follow others, or whatever other limits Twitter wants to impose on them. On the flip side, bots could enjoy different categories of moderation, suspension, or flagging rules as they are no longer being confused with "human" posters. No need to tie them to a phone number, for example, or provide other human identity verification.

The idea is to carve out a space for developers of purposeful "art bots", away from the current discourse surrounding bots as foreign agents, disinformation tools or political weapons.

A rule operator of "no more than X tweets per second" is very similar to sampling. However, if it existed, it could theoretically set on every rule. This would allow knowing that no rules could absorb too much of total allowed volume, and to make sure that low volume rules aren't sampled, while higher volume rules still are. It would also mean that a rule that has a sudden burst of activity would not absorb all available volume at once. Without this operator, monitoring the volume on rules must take place, and sampling must be applied dynamically when volume increases or decreases.

Our product allows users to search for and aggregate content from Twitter to display on websites/apps in embeddable feeds. An issue we’ve been having recently are Tweets appearing in our dashboard search results, but where the media/video doesn’t play.

We are aware of Twitter Amplify and Twitter Media Studio - and how publishers can geo-restrict videos, which we understand to be the cause of this issue.

Currently we are forced to completely remove any/all Amplify-powered Tweets from our systems (removing any video where src contains “video.twimg.com/amplify_video” ) which means that we are also removing Tweets that are not withheld, but are posted to Twitter via tools such as Tweet Deck.

So it would be really useful to have a programmatic way to determine whether the Media itself (rather than the Tweet) is withheld/restricted - very similar to withheld_* fields for Tweets in the API. With this, we would be able to filter these results from our dashboard (and eventually pass on the restrictions so that we can support geo-restrictions ourselves).

Could this be made possible?

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.