antibot4navalny
My feedback
-
11 votesstarted · 2 comments · Twitter Developer Labs » General features · Flag idea as inappropriate… · Admin →antibot4navalny
supported this idea
·
-
13 votesstarted · 4 comments · Twitter for Academic Research » APIs & Tools · Flag idea as inappropriate… · Admin →antibot4navalny
shared this idea
·
-
7 votesacknowledged · 0 comments · Twitter for Academic Research » APIs & Tools · Flag idea as inappropriate… · Admin →antibot4navalny
supported this idea
·
-
12 votesacknowledged · 0 comments · Twitter for Academic Research » Documentation & Resources · Flag idea as inappropriate… · Admin →antibot4navalny
supported this idea
·
-
14 votes1 comment · Twitter for Academic Research » Additional data types · Flag idea as inappropriate… · Admin →
Thanks for your feedback.
We are currently developing more simple and scalable ways for developers to get back impression and engagement data on their owned content. Check out this space for more information soon.
More detail is included in our Developer Platform Roadmap: https://trello.com/b/myf7rKwV/twitter-developer-platform-roadmap
Note that while this work is planned, the engagement solution we are working on may not be immediately viable for research use cases.
antibot4navalny
supported this idea
·
-
22 votesacknowledged · 1 comment · Twitter for Academic Research » General features · Flag idea as inappropriate… · Admin →antibot4navalny
supported this idea
·
-
19 votesplanned · 4 comments · Twitter for Academic Research » APIs & Tools · Flag idea as inappropriate… · Admin →antibot4navalny
supported this idea
·
-
54 votes
We are working on defining ways of retrieving a thread using a specific endpoint.
In the meantime, you can use the full archive search endpoint to retrieve an entire conversation thread (https://developer.twitter.com/en/docs/twitter-api/conversation-id).
antibot4navalny
supported this idea
·
-
39 votesplanned · 10 comments · Twitter Developer Labs » General features · Flag idea as inappropriate… · Admin →antibot4navalny
supported this idea
·
An error occurred while saving the comment An error occurred while saving the comment antibot4navalny
commented
Please make permissions required for Hide Replies API calls as atomic as possible.
Mass users are reluctant to allowing any write, and often read permissions. This is major stopper for Blocktogether.org broader adoption, for example.
-
2 votes
Thanks 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.
antibot4navalny
shared this idea
·
-
2 votes
Thanks 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.
antibot4navalny
shared this idea
·
-
3 votes
Thank 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.
antibot4navalny
shared this idea
·
To add to the original suggestion, the permissions required for "Hide Feature" recently announced should be also as atomic as possible: https://twitterdevfeedback.uservoice.com/forums/921790-twitter-developer-labs/suggestions/39308614-make-permission-for-this-as-atomic-as-possible