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#media27 votes
Thanks for the feedback! While we are aware of this ask, we will not be able to prioritize this in the near future. Please keep voting for this idea if it resonated with you.
Currently there is no way to only return promoted tweets. With a "filter:promoted" filter option, it would be possible to only return promoted tweets combined with other search terms.
This feature would help researchers and increase ad transparency.17 votes
We appreciate the feedback, but this is not on our roadmap for the near-term future. Hence marking as “closed”.
Add a field to know when media is being withheld by country8 votes
The standard search API is somehow regarding screen name as part of text body and therefore is also searching in screen names. That can cause the search results to contain irrelevant tweets. For example, searching the word "nature" can return @human_nature's tweets whose text bodies don't contain the word "nature".
A similar issue applies to user mentions. For example, searching the word "nature" can return tweets which contain user mention @human_nature and don't contain the word "nature".
Please consider implementing an option which prevents the standard search API from searching in screen names and user mentions. Thanks.6 votes
It appears that the user-auth rate limits in the labs API is shared among all users.
I could see however that app-auth limits are separate, so there is distinction between app-auth vs user-auth, just not working as expected6 votes
Get all bookmarked tweets by me4 votes
Is there any plan to allow access to the cropping rectangles that are associated with each media image? These are called focusrects and are nested under the originalinfo property of extended_entities.media and could be passed along with the rest of the media info in the API request.4 votes
While I understand the motivation for the separate "expansions" in the GET Tweets endpoint, I wonder if you have considered using GraphQL to allow the user to determine the shape of the tweet data returned?
In adding support for the labs endpoint to twarc  I found that I wanted to knit back together the data that is separated out into tweets. If GraphQL was used I don't think this would be necessary.
I would be curious to know if Twitter Labs considered switching to GraphQL for fetching tweets and users.3 votes
- Don't see your idea?