Twitter Developer Labs
-
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…
3 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.
-
Consistency for "Likes" and "Favorites"
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".
13 votes -
Recommend and endorse a good Twitter library
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.
9 votes -
Add an option to forward a tweet
To enable one to send a tweet to a group
4 votes -
Programmatically unhide a Tweet
Provide a way to programmatically unhide a previously hidden Tweet, given appropriate user consent.
3 votes -
Richer Direct Messaging API to enable creating more powerful BOTs
To enable a truly rich bot experience on Twitter, the API is missing things like:
- Cards message type (image + text + buttons +swipe left/right)
- Buttons and menus as part of message (not only Quick Replies)
- A more integrated webview, that is an integral part of the bot experience (for example the bot sends a "pick your seat" button which opens a small size web widget right in the chat to pick the seat, and then goes back to the main chat bot flow)
And most important:
the fixed limit of 15k DM regardless of number of…4 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.
2 votesThanks 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.
2 votesThanks 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.
-
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 voteThanks for the feedback! We will not be changing this in the near future, so I am going to close this suggestion. Please continue to vote for this idea if it resonates with your needs.
-
Trending spots
Add more trending stations/places, like for north Indians its only Delhi.
3 votes -
Build a more accessible version of the engagement metrics API
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.
11 votes -
Fully adopt OAuth 2.0
I would like the Twitter API to use OAuth 2.0 instead of OAuth 1.0. OAuth1.0a is fairly specific to the Twitter APIs at this point in time. It's complicated to implement, and there is a dwindling number of developer tools that support it. OAuth 2.0 is less complicated and easier to build into an app than OAuth 1.0.
9 votesMarking as “closed” as we are unable to invest in fully migrating to OAuth 2.0 at this time.
-
Access to Image Crop Information
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.
6 votes -
GraphQL
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.
4 votes -
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?
-
labs/1/tweets and Get labs/1/users rate limits
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 expected7 votes -
Add premium endpoints for the following/followers endpoints
At www.contexto.io and www.graphext.com we provide our customers the possibility of mapping and expanding Twitter communities leveraging the social graph. This allows us to get really contextual, relevant and different insights that most social media analytics tools offer (they mostly count keywords that matches a boolean query).
We currently use the free API following/followers endpoints for this right now but with the new policy starting this month we cannot make more than 100K requests/day which prevent us from scaling our product. We would be very happy to pay for a premium endpoint like this!
6 votes -
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.
-
Help developers filter out spam or other noisy content
There can be a huge upfront effort to sift through the volume of Tweet data in order to get a data set that is interesting and valuable. It would be great to add more upfront filtering options to reduce the amount of data needed for statistically relevant analysis.
6 votes
- Don't see your idea?