Open jacobmas opened 4 years ago
Such a good idea! I think it can would be better if works standalone (instead of based on pages). If you can update documentations too we I can merge.
The problem is that without the pages functionality, you lose flexibility of cutting off early in case a particular account has done a massive amount of tweeting over the time period (in which case your end application will slow down).
On Wed, Feb 12, 2020 at 12:39 PM Buğra İşgüzar notifications@github.com wrote:
Such a good idea! I think it can would be better if works standalone (instead of based on pages). If you can update documentations too we I can merge.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/bisguzar/twitter-scraper/pull/106?email_source=notifications&email_token=AEW57PZWTB2NIZJIHUCLMGLRCQX6DA5CNFSM4KSOOOJ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELRWEQQ#issuecomment-585327170, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEW57PYL3FRHN5PBLPPCMULRCQX6DANCNFSM4KSOOOJQ .
-- -Jacob Alperin-Sheriff
I see, but documentation still needed.
adds timedelta parameter, i.e. allowing scraping of only the most recent tweets instead of pages alone. Note that it still cuts off based on pages