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 ?

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

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.

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 ?

Ability to categorize bookmarks and have a search bar included in that feature as well. This will permit users to access their favorite saved posts quicker and more efficiently. Organization is rooted in the most common reasons of dislike while utilizing social media applications, so with this tool you would be killing two birds with one stone. Simply by gaining attention from current and new users as well to compete with other applications while getting rid of this nuisance.

Create endpoint for get "quote tweets" by other to Tweets authored by the user. Like endpoint statuses/retweetsofme.

Currently we can access 1on1 DM via Twitter API but not group conversations. If we forcibly set the group's conversation_id, Twitter API returns forbidden. Allow this.
ref
https://developer.twitter.com/en/docs/direct-messages/sending-and-receiving/api-reference/new-event

Can be interesting to split in two the type of medias in user profiles.
1/ Personal pictures of the user (where he is tagged)
2/ All the rest (gif, memes, etc.)
Currently it's a little bit messy when you want to check the medias of a user.

It's a pity to not be able to create a poll providing images on the same tweet. Why not adding it, like you did for retweet few years ago ?

The evolution of this week was really interesting, but I would go further and like Facebook, let the user decides WHO can see a tweet (everybody, only my followers, our only the mentioned users).

I would like to recommend building a conversations API that enables developers to track updates to full conversation threads. This API would retrieve the entire conversation that a Tweet is in, and return all Tweets and replies within a given thread. This API would enable developers to go from a Tweet of interest to all replies in the thread, without having to recursively search for Tweets with the correct "inreplytostatusid".

It would be really helpful to have an analytics endpoint in which the entity was a media ID (in my case a video ID) and you could request engagement & video metrics aggregated at the video level, even if that video appeared across many different tweets. Right now this is possible through the Engagement API for video views only, but it would be great if it were available through the Ads API & included seconds/minutes viewed, percentile completions, call to action clicks, etc.

I suggest you to add hot trends.. Which has highest tweets in the world beside country trends it just suggestion named World hot trend... I feel it will get more contacts between people over world

Already used through third-parties, an Asking feature would allow a new channel for interaction between users, with possible permission control such as ""follows/mutual followers only".

Implementing a search bar solely for your timeline will save users from wasting time trying to remember tweets when they refresh the app. Instead of having to scroll down, search for the tweet with words that are constantly used in the atmosphere, and for those that may have forgotten to bookmark it immediately upon sight.

Having access to an API for Twitter native polls would enable developers to create and schedule polls, as well as get back engagement data such as impressions, responses, Retweets of the poll, and their resulting responses, reach, and total engagement.

Surface is the first tweet in the hashtag, to know the founder of the hashtag, it is his right; and also there are those who use the hashtag for no purpose intended for topic of the hashtag (no objection to it), but you are tired to reach the news for which the hashtag was founded due to the large number of tweets outside the same topic.