Proposal: cursor handling

[DanielaSfregola]

Just a quick note to keep track of ideas.

This has been inspired by DanielaSfregola/twitter4s-demo#30
Should this library handle cursor? The "next-cursor" pattern is quite popular in the Twitter API.

PROS:

• I assume people do this quite often, so it would be useful to have it in the library

CONS:

• You could really hit your rate limits by querying lots of pages that you really do not need.

...do our users want this feature?

[TheConner]

I may need this for my research work actually. If I find that pulling 500 tweets/request isn't enough for my needy needs, I will follow up with a PR of some kind. Is there any particular design pattern you would like to follow here, or should cursors be handled on a case-by-case basis?
(otherwise for the time being I just handle the cursors myself)

[DanielaSfregola]

You can do the cursor by hand, of course. The idea is to maybe have a chain of requests and stop either when rate limits are reached or when "enough" data has been collected