Handles loops to request more data about pstwitterapi HOT 4 CLOSED

Interesting, the documentation makes it seem like posting more than 100 at a time would be doable.
It looks like each key is limited pretty steeply -
Requests / 15-min window (user auth) | 900
Requests / 15-min window (app auth) | 300

So it looks like if we were hitting the other limit of 100 users per run we would hit the requests failure window extremely fast (and need some automatic method to rotate through keys.)

Do we want to implement that on the invoke-twitter api layer since retry logic seems like core functionality? (or am I just missing where we do that?)

from pstwitterapi.

Some of this implementation is already done.

This is why you would set more than one OAuthSettings. When doing a Get-TwitterOAuthSettings, it sorts by the one that has more rate limit available.

This implementation should be reviewed, and see if there is a better way of doing it.

from pstwitterapi.

Ahh that makes sense, I saw the token stuff but didnt suss it out right away.

from pstwitterapi.

Wrong PR

from pstwitterapi.