Twitter Developer Labs
-
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)
11 votes -
Show when a Tweet is hidden in the Tweet payload
The Tweet payload should contain a field that indicates whether a Tweet has been hidden. This can help people maintain display consistency regardless of where they manage their Twitter accounts. Researchers can find the field useful to understand circumstances such as relevancy, confusion and abuse.
8 votesThanks for the feedback! We are actively considering this.
-
Retrieve a list of hidden replies to a given Tweet
Developers may need to retrieve a list of hidden replies for a specific Tweet. This can be useful to obtain a list of Tweets can can be unhidden, given appropriate user consent. Developers can also create aggregate reporting via this API (for example, count how many Tweets are hidden per conversation, or per time period).
7 votes -
Increase of Rate Limit
Hiding replies would be of massive value to our clients, but with the current rate limits, we wouldn't be able to meet their requirements.
Please can you provide forecasts as to when rate limits will be increased and what they will be increased to? Would this happen once the capability goes from Labs into live service?
Many thanks.
1 voteWe are actively looking into a new rate limiting configuration to better serve production use case. We will update this idea as soon as we make progress.
-
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.
-
Programmatically unhide a Tweet
Provide a way to programmatically unhide a previously hidden Tweet, given appropriate user consent.
3 votes -
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.
- Don't see your idea?