Hello, in previcious versions we used to filter with all tweets by popular recent and mixed . Now it is gone. Can you please bring it back

Instagram have recently given users the ability to remove followers instead of blocking them to remove them. I please request that Twitter also give us this option and not notify the users they have been removed from following us.

Emoji search is working fine for tweets, but not for user search.

Why don't we have the same kind of statuses/retweeters/ids endpoint but for likes, in order to get all the user ids who liked a particular tweet ?

With API v2 (Labs v2) launching last week, it seems incredible that some endpoints still require the use of oAuth 1.0 which is scarcely supported. This makes developing for the 'next gen' API feel surprisingly primitive - and is an accessibility barrier that is unique in the sophisticated landscape of 2020.

For drafted tweets to be synced with my account, whether I reinstall the app or change platforms, my drafts are synced throughout all platforms

Images in tweets should have their alt text available via API. Make it obvious. Here is where I would have expected to find it: https://developer.twitter.com/en/docs/tweets/data-dictionary/overview/entities-object#media

Giving us an alert when we are off our 3 day limit, because you guys give us one when we’re put on it but not when released from it.

Add files section to the search, lately I noticed a lot of people post files that could help me and it will be easier for me to find it if there was a filter for files

We need a way to manage muted keywords, similar to the existing endpoints for muted users:

GET mutes/keywords/list
POST mutes/keywords/create
POST mutes/keywords/destroy

When I try to hide a Tweet in a thread that wasn’t started by the authenticating user, I get the response:

(
[title] => Forbidden
[type] => about:blank
[status] => 403
[detail] => Forbidden
)

I understand that this action should actually be forbidden, but the error in the API response doesn't tell me why the action is forbidden (which is that the authenticating user is trying to hide a Tweet in a thread that wasn't started by the authenticating user)

Why couldn't we get our own data archive through API calls ?
Instead of having to download the whole archive (which is really heavy), it can be interesting to have several endpoints where we could request all the data between two dates for the authenticated user.

Tweet threads have become increasingly popular over the past few years. This API would enable developers to tap into the potential of threads by programmatically creating threads, as well as retrieving all Tweets in a thread.

In the app or on the web, we can access to the list of "Followers you know" of another user. It could be nice to have this information in expansions too.

Really often, people on Twitter define a choice on their poll just to let people not concerned see the result. Why not providing a simple button to let anybody see the result without having to choose an answer ?

The API should support limiting who can reply to a Tweet when Tweeting using POST statuses/update. This could be useful for publishing tools that can be used to schedule and publish Tweets across different accounts (e.g. a brand account in multiple languages).

What are other use cases where you would want to limit who can reply to a Tweet through the API?