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/destroy
Rodrigo Pombo
shared this idea
5 comments
-
Marthyn
commented
I saw someone requesting a service that would read all trending topics and then add them automatically to their muted keywords list. I think this could be a great service. Of course with an allowlist that would prevent keywords they actually like to be added to the muted keywords list.
And maybe also automatically then destroy the muted keyword as soon as they're not trending anymore. This keeps your Twitter from being flooded with what we call in Dutch 'de waan van de dag'. Not everyone is on Twitter for trending topics.
-
Colin Winhall
commented
Any update at all on this Aurelia? I don't understand why we have the ability to do this for users but not for words :(
I see there is /i/api/1.1/mutes/keywords/create.json for this but it has not been added to the api.twitter.com host and documentation.
I feel this could be a quick win here, please do consider this request :)
-
Thanks for the additional detail, Rodrigo. I have shared this with the Product team for consideration.
-
Rodrigo Pombo
commented
Use cases:
1. a chrome extension to select words from a tweet and mute them directly from the timeline (similar to the iOS app I think)
2. I also have an idea to recommend keywords to mute but I need to think about it a little more -
Thanks for the feedback! Can you help us better understand your use case? How would these endpoints help you?
