Closed Jamie1605 closed 9 months ago
Right now try to multiple accounts together if you want to do it every second, furthur search has 50 requests per 15 minutes rate limit , try using Twiiter List
Is a 'request' one tweet or one search i. e. would it help to limit the searches to a smaller amount of tweets?
one search request
So the amount of tweets is irrelevant to the rate limit?
making one request retrieve +-20 tweets.
And how exactly ist the tweety list different from a normal python list?
You mean python list
Right now try to multiple accounts together if you want to do it every second, furthur search has 50 requests per 15 minutes rate limit , try using Twiiter List
What did you mean by "Twitter List" here? Maybe I misunderstood
https://twitter.com/<username>/lists
, You can create a a custom timeline for specific users , it is called List on Twitter
The purpose of my code is to archive tweets of one specific user if they are deleted using app.search('from:username', filter_=SearchFilters.Latest())
so a list probably won't make sense for me
get_list_tweets
- Create a list
- add specific user in that list
- keeping checking for tweets in the list using
get_list_tweets
Function get_lists_tweets() has 50 requests per 15 minutes rate limit? Is there also 30 day limit for it?
- Create a list
- add specific user in that list
- keeping checking for tweets in the list using
get_list_tweets
Ah, okay. I still don't quite get how the way to do it with the list will be better for the rate limit than the normal search.
- Create a list
- add specific user in that list
- keeping checking for tweets in the list using
get_list_tweets
Function get_lists_tweets() has 50 requests per 15 minutes rate limit? Is there also 30 day limit for it?
get_list_tweets
has upto 500 request per 15 minutes rate limit
- Create a list
- add specific user in that list
- keeping checking for tweets in the list using
get_list_tweets
Ah, okay. I still don't quite get how the way to do it with the list will be better for the rate limit than the normal search.
get_list_tweets
has upto 500 request per 15 minutes rate limit and also returns more than 60 tweets in one request as compared 20 in search
- Create a list
- add specific user in that list
- keeping checking for tweets in the list using
get_list_tweets
Ah, okay. I still don't quite get how the way to do it with the list will be better for the rate limit than the normal search.
get_list_tweets
has upto 500 request per 15 minutes rate limit and also returns more than 60 tweets in one request as compared 20 insearch
Do you know how many requests tweet_detail
has? Thats the function I use to check if a tweet has been deleted. I run it for every tweet and if a tweety.exceptions_.InvalidTweetIdentifier
occurs I know it was deleted. I assume that plays a role too.
And if it's too heavy, is there a better way to check if a tweet has been deleted?
What would be the most efficient way to monitor new incoming tweets live?
Currently I run a search, save each tweet to a list, and then repeat the same search every few seconds, adding any new tweet that isn't already in the list, but that leads to a rate limit error pretty quickly if I want to do it reliably.
Is there a more efficient way to achive this that I'm missing?