Difference between the result of Twitter search screen and the return value of API
In some cases, the result of a search set to include a specific word in the advanced search of twitter is slightly larger than the return value of the API. However, some tweets only appear in the return value of the API.
Why is this? Why aren't they unified?
This is the advanced search screen I am talking about.
https://twitter.com/search-advanced?f=live
We want the same result as searching for AAA in the advanced search screen, so the API rules are:
"(AAA OR bio_name: AAA) -is: retweet"
Please let me know if anything is wrong.
Thank you
APIテスト用
shared this idea
2 comments
-
APIテスト用
commented
>2. In Labs, streaming endpoints are limited to 50 Tweets per second.
This is not the case because the current observations do not set keywords to which so many tweets come.So, if there is a cause, I think it is here.
>1. The streaming endpoints in Labs exclude high-confidence noisy content similarly to our enterprise endpoints.In other words, you need to adopt what I have proposed here.
https://twitterdevfeedback.uservoice.com/forums/921790-twitter-developer-labs/suggestions/39689107-filters-other-than-the-rules-i-createdthank you.
-
This is expected:
1. The streaming endpoints in Labs exclude high-confidence noisy content similarly to our enterprise endpoints.
2. In Labs, streaming endpoints are limited to 50 Tweets per second. If your filtering rules are expected to yield high volumes of Tweets, only the first 50 will be returned through those endpoints.
For future reference, it would be better to ask this type of question in our community forums: https://twittercommunity.com/
This platform is intended for feature requests and feedback *only*.
Thank you!
