Dmitry Mottl
Dmitry Mottl
Ok, thanks The problem is this: each response has the `min_position` value (an id) that should be used to access further tweets using `max_position` GET parameter. The problem occurs when...
@kho7, the issue is with `min_position` as stated by Rahul: https://github.com/Mottl/GetOldTweets3/issues/3#issuecomment-439092370
You sure understand what Rahul has written about min_position?
It depends on your queries. The algorithm is this: query for results, get the _cursor_ to the next result, iterate: https://github.com/Mottl/GetOldTweets3/blob/34078e10e5d7b053c3495a1517e6b529a914fb37/GetOldTweets3/manager/TweetManager.py#L64-L69 So in a common case you can't get the...
If you split by dates then `--since` param of the next interval must equal to `--until` param of the previous interval (do not add 1 day!)
Yes, exactly. That's because `--until` date is NOT INCLUDED in results — this is Twitter behaviour.
@afzal646, do you see a location info near tweets in a browser?
Do you know a way to get all the retweets **in your browser**? p.s. Keep in mind that the total number of retweets of a tweet is already stores to...
>Unfortunately I do not know how how to get all the retweets in the browser (can you share?), actually I am a bit confused by this question.. By asking, I...
@elDudarino, you can experiment with the `filter:nativeretweets` and change the code accordingly. Here is the example url: https://twitter.com/search?f=tweets&vertical=default&q=bitcoin%20filter%3Anativeretweets&src=typd