Twitter Developer Labs
1. See what other ideas have been submitted and vote for ideas you like.
2. If you have an idea that isn't already listed, create a new post.
3. Include only one idea per post.
Thank you for participating!
-
Add endpoints for muted keywords
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/destroy2 votes -
Sensitive content filter?
The sensitive content filter seems to work on very strange principles. It censored this tweet- https://twitter.com/ringo0120mkt/status/1232618349521072128, blocking a harmless image of stuffed animals. It has also blocked images from video games containing absolutely no sensitive content. I have read on how the filter works (basically, if a user keeps posting sensitive content and not labeling it, all their tweets are labeled as "sensitive"- at least part of this process appears automated), but it still seems strange, especially since many of these are foreign language tweets whose creators may not have read the (English) rules.
The bothersome part…1 vote -
API response should contain descriptive error messages for actions that are forbidden
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)
3 votes -
Filters other than the rules I created
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/faqThis 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.
1 vote -
API endpoint for getting bookmarks
Get all bookmarked tweets by me
3 votes -
Add the “order” of the image
Retrieve tweets using Labs’ Recent search API.
I referenced the images in the order included in mediakeys, but obviously not in the order displayed on twitter’s web.
But, the order of the images is not included in mediakeys.How do I know the order of images if tweet has multiple images attached?
For example, if a manga with a single story is posted with four images, like this:
(TwitterWebURL)/shiromanta1020/status/917652272804380672
This doesn’t make sense unless you read it in order.In order to reproduce this “order”, it is necessary to add the “order” of the image as a response…
1 vote -
Who to follow API
Add an API version of the popular "Who to follow" link seen at lower right on the home page: https://twitter.com/<...>/whotofollow .
(Currently it uses non-public APIs under the hood.)1 vote -
Geo enrichment
Gnip PowerTrack has a "Profile Geo" enrichment [0].
Adding this to the filtered streams API would make migrations easier.
1 vote -
Proximity operator
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
1 voteThanks for the suggestion. We are currently considering this. Can you tell us a bit more about why this feature is important to you?
-
Longer queries in filtered stream
Queries can only contain a limited number of terms and characters. It would be very useful to increase this llimit.
2 votesThanks for the feedback! We will be increasing rule length once we graduate out of the Developer Labs programme.
-
Wildcards in filtered stream
Wildcards would be very nice to have in filtered streams: Customers want them, and there is no way to emulate it on our side.
When a query term contains a
*character,*would match any character in a tweet, one or more time. When a query term contains a?character,?would match any character, exactly one time.For example,
Tw*terwould matchTwitter,Tweeter,Twiter,Tweetter.3 votes -
First Tweet containing a hashtag
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.
1 voteThis is already possible with the Search API (full archive). You can use the counts endpoint for example to find out when a hashtag was mentioned for the first time on Twitter.
-
Add "name" and "screen_name" to the response data of Recent search API
In the published standard search API, these parameters are in a single tweet object.
・User object
Screen_name and name are important elements in User Object.
Now we have to expand. This is very inconvenient.Please add "name" and "screen_name" to the response data.
1 vote -
Add support for "sample" operator
Support for the sample: operator. Many use cases would benefit from random samples. For example, sample:10 would return 10% across each hour...
2 votes -
Allow to access historical replies for a depth of a year for subscribed users
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.
1 voteThanks for the feedback! This is not currently on our roadmap, but keeping track of the replies that have been hidden by your app should be fairly straightforward to do on your end. It would be helpful if you could give us additional insight into why this feature is important for you and tell us more about your use case.
-
Allow to serve 10Ks-100Ks of users subscribed for a HideReplies app
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.
1 voteThanks for your suggestions! We are currently considering higher rate limits. Additionally, you can already access a stream of (in)direct replies to a subscribed user with the Account Activity API.
-
Hide Replies and Block Users should be combined in a wiser way
Currently, there is an easy way troll farms already circumvent the "hide replies" feature:
1) post a disinfo/harrassmt reply to a target account
2) then immediately block (blacklist) the target account
3) now the abusing reply is visible for everyone, but neither attacked account nor anyone else can do anything with it.I don't have a solution that will surely fix this. I understand that this is actually feedback on how Hide Replies works for users, not how it should be available via API. Any better place to post feedback on user feature and to be sure it will be…
2 votesThank you for this feedback, and appreciate the level of detail. Your voice is heard here – We’re passing this to the team working on Hide replies for users so they can review.
-
Filtered Stream monthly limits
I read in this announcement https://twittercommunity.com/t/new-filtered-stream-endpoints-available-in-labs-and-the-future-of-statuses-filter/129888 that the new Filtered Stream endpoint, available in Labs, will be subject to monthly limits on the amount of tweets retrieved.
Do you think that this kind of limitation will also be present in the version released in the future?I didn't find this kind of limitation on the old endpoint "statuses/filter".
In this answer on stackoverflow https://stackoverflow.com/questions/34962677/twitter-streaming-api-limits
, the idea of a limit on the endpoint "status/filter" based on the amount of tweets delivered within a certain percentage threshold compared to the totality of tweets generated on twitter was mentioned.
I find that…2 votesThanks for the suggestion. This is not something we are likely to prioritise in the near future. However, please continue voting for this idea if it reflects your needs.
-
Need a way to manage compliance (deleted Tweets) while using Sampled stream
I currently use the statuses/sample endpoint to stream 1% of Tweets and related compliance events for those Tweets. Having the deleted Tweet events helps me know when Tweets I've received are no longer available so that my database and application stay compliant with Twitter's policies.
Please give me a similar compatible and convenient way to keep the data received from Sampled stream compliant.
1 voteThanks for the feedback! As part of Twitter’s API v2, we are looking into how we can better support compliance use of our APIs. More information to come.
-
Programmatically unhide a Tweet
Provide a way to programmatically unhide a previously hidden Tweet, given appropriate user consent.
1 vote
- Don't see your idea?