Without this field as part of a tweet, it becomes very expensive in the form of API calls to manage a conversation. If this was available, it would be easy to manage hide replies because if the reply was already hidden, why make an api call that affects thresholds. Good for you because less processor time spent servicing requests.
Of course all this is null and void if there is a is:hidden operator on search api that I am not aware of (standard product)
2 Likes
I thought this would have been in reply_settings object?
Tweet object | Docs | Twitter Developer Platform (I haven’t checked this, just occurred to me that would be the place for it)
There’s definitely no is:hidden operator
reply_settings is a string in the tweet json and in the docs.
1 Like
Came to TwitterCommunity with exactly the same request: to either have a search operator
[filter:hidden]
or a APIv2 field in tweet JSON
{"hidden": "true" / "false"}
For me, it’s now an essential part of how malicious actors behave: what replies do they hide, and why.
1 Like
The best way to suggest this would be to use the API Feedback platform so that the product team can prioritise the suggestions. Thanks.
