Limit is inconsistent with -l flag

[taspinar]

Limit is inconsistent with -l flag

[taspinar]

Hi @patrickdundas
The scraper stops scraping when 'at least' the no_limit number of tweets have been scraped.
The infinite scroll of Twitter updates the page with batches of 20 tweets at a time.

So when you set the limit to 30, twitterscraper will stop scraping after two batches of 20 tweets, hence resulting in 40 scraped tweets.

If it a big issue, I can adapt the filewriter so that only the first no_limit number of tweets are written to file and the remaining tweets are disregarded.

[patrickdundas]

It would definitely be nice for there to be a way to just grab a certain amount of tweets, rather than a certain amount of batches. Since that's the case, wouldn't it make more sense for there to be a "true limit" flag which would just give a specific amount of tweets and a "batch limit" flag, which would use the current batch behavior of --limit? Such as --batches and --limit, or --limit (as it as now) and --tweets or --truelimit (which would download x amount of tweets)? I think that the way the documentation is worded right now makes people assume that --limit actually just gives you that number of tweets, rather than an unpredictable number of batches. Thanks very much for the clarification, but I think either the documentation on --limit needs to be reworded, or there needs to be a better way to grab a specific amount of tweets.

[taspinar]

Hi @patrickdundas ,
Is the current explanation in the readme sufficient?