Include message lifetime reach (unique impressions) and profile-level daily reach metrics for messages. This provides better insight into the number of individuals that saw a specific tweet or content associated with a profile/brand.

As a new developer, I want a lightweight way to make an API call within the documentation with little setup involved. I need to see and evaluate quickly what a request and response looks like for a specific endpoint.

It would be great if we can have another endpoint for metrics that would provide stats like the 28hr end point, so we can have more detailed metrics (link clicks, profile clicks etc) as well as hourly metrics

Support for the sample: operator. Many use cases would benefit from random samples. For example, sample:10 would return 10% across each hour...

Language consistency would be helpful.

• API Representation uses "favorites", but the current Twitter interface uses "likes".




• In the documentation for "Account Activity API" notes "likes", while in "Search Tweets" notes as "favorites".




• Perhaps not all of us are aware that "favorites" is a precedent of "likes".

I was trying to summarize a conference in a moment with over 64 tweets. Trying to organize those manually moving them up and down 1-by-1 on the site was a pain (as many people tweet things not quite in chronological order of the conference or if you sorted once and want to add more later, it's hard).

It'd be great to expose the API for creating/editing moments so that other tools could help push the experience of capturing events or help to correlate topics and insert into proper places.

As hiding criterias tend to change over time (eg global grey-list of unwanted commenters to hide), I wish my app would be able to retroactively access (and hide/unhide) historical replies to historical tweets of subscribed users with a depth of eg at least a year from now.

At least, to access the list of replies my app had previously hidden.

Allow a free-plan developer to serve 10Ks-100Ks of users subscribed for a "hide replies" allowing to hide tweets nearly real-time as they happen (provided that an app is capable to deal with such a firehose).

This at least requires easy access to a stream of direct and indirect replies to the users subscribed.

The following is written on this page.
"The stream leverages some of our content filtering technology where we exclude high-confidence noisy content."
https://developer.twitter.com/en/docs/labs/filtered-stream/faq

This is a different filter than the one I created.
To make sure that my filters work properly, I need to turn off content filtering technology.
I want to create an option that does not use content filtering technology.
It is up to each user to get the data to determine which tweets are noisy.

Thank you.

Twitter could include a list of approved Twitter libraries for different programming languages in the documentation. This would equip developers with robust resources and help them know which resources they can rely on to use the Twitter API.

It would be useful to be able to retrieve more than 100 results calling GET statuses/retweeters/ids
The current limitation doesn't make sense.

Gnip PowerTrack has a "Profile Geo" enrichment [0].

Adding this to the filtered streams API would make migrations easier.

[0] https://support.gnip.com/enrichments/profile_geo.html

From the operator reference [0], the filtered streams appear to lack the proximity operator, that existed in Gnip PowerTrack.

Having this in the filtered stream API would make it easier to migrate from Gnip.

Additionally, in PowerTrack the maximum proximity value is 6. Increasing this limit would make the operator extra useful.

[0] https://developer.twitter.com/en/docs/labs/filtered-stream/operators

Provide a way to programmatically unhide a previously hidden Tweet, given appropriate user consent.

Add more trending stations/places, like for north Indians its only Delhi.

Twitter could build a more affordable version of the enterprise Engagement API, which would provide developers with Tweet metrics for owned Tweets.

Engagement data returned by the API includes number of Likes, Retweets, replies, impressions, and engagements (for example, number of link clicks). This API would enable developers to better understand their reach and impact on Twitter.

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 [1] 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.

[1] https://github.com/docnow/twarc

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 expected

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.