Twitter Developer Labs
-
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=liveWe 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
2 votes -
Filter tweets by users list
It could be great to be able to use the "list:username/list-name" search parameter into the filtered stream endpoint, to watch tweets from a list of users rather than chaining "from:usernameX" parameters until the 10*512 chars are used.
Especially since the new endpoint will replace the current one that currently allows to watch up to 5k users (the "from:xxx OR " method will only allow to watch 250 to 400 users depending on the average username length ; that's more than 10x less than before).
7 votesThanks for the feedback. This is not on our roadmap for the near-term future. However, we understand the problem that you are facing and we will bear this in mind going forward.
-
Filtered Stream monthly limits
I read in this announcement https://twittercommunity.com/t/new-filtered-stream-endpoints-available-in-labs-and-the-future-of-statuses-filter/129888 that the new Filtered Stream endpoint, available in Labs, will be subject to monthly limits on the amount of tweets retrieved.
Do you think that this kind of limitation will also be present in the version released in the future?I didn't find this kind of limitation on the old endpoint "statuses/filter".
In this answer on stackoverflow https://stackoverflow.com/questions/34962677/twitter-streaming-api-limits
, the idea of a limit on the endpoint "status/filter" based on the amount of tweets delivered within a certain percentage threshold compared to the totality of tweets generated on twitter was mentioned.
I find that…3 votesThanks for the suggestion. This is not something we are likely to prioritise in the near future. However, please continue voting for this idea if it reflects your needs.
-
Change Filter Rules API, Lengths and Limits
Currently 1 rule is limited to 512 characters, and there are 10 rules.
The rules API would make more sense if there was a limit on operators and a number of them, rather than the character length of rules. For example: when using multiple
follow:userorfollow:idit can get unpredictable due to the varied length of screen_names and user IDs created before 64bit snowflake user ids.To make the rules API more useful, there should instead be a limit on the number of specified operators, not rules or rule character lengths.
This way, i should be able to specify…
1 voteThanks for the feedback! We are aware of this ask, but we will not be making any changes to this in the near-future. As such, I am going to close this suggestion. However, please continue to vote for this idea if it resonates with you.
-
Filters other than the rules I created
The following is written on this page.
"The stream leverages some of our content filtering technology where we exclude high-confidence noisy content."
https://developer.twitter.com/en/docs/labs/filtered-stream/faqThis is a different filter than the one I created.
To make sure that my filters work properly, I need to turn off content filtering technology.
I want to create an option that does not use content filtering technology.
It is up to each user to get the data to determine which tweets are noisy.Thank you.
1 voteThanks for the feedback! We will not be changing this in the near future, so I am going to close this suggestion. Please continue to vote for this idea if it resonates with your needs.
- Don't see your idea?