React to rate-limit being reached

[openjck]

When using OAUTH authentication, we are limited to 5,000 API calls per hour. We need to handle the case where the limit is reached.

[groovecoder]

Yes, big 👍 for this!

[darkwing]

Great idea @openjck . We may want to investigate a way to request/purchase increased rate limits as something like this would definitely, definitely limit scale. We may need multiple accounts to work around it, or something.

Anywho, this is a great starting idea!

[groovecoder]

Are we making the API reuqests with an oauth2 key/secret? We already have an MDN GitHub application; we could use its client/secret to increase our rate limit from 60/hour to 5,000/hour.

[Faeranne]

We are using an API token with the commenter, which should already give us the 5,000/hour on comments. Octonode, however, is not using the token.

[openjck]

We should still do this, but as it turns out, the rate-limit isn't the problem here. Comments fail to appear even when we are well below the limit. I'll open a separate issue for the real culprit.

[openjck]

Opened #104 for the issue that actually prevented comments from appearing.

[openjck]

limiter looks to be the best-supported node module for dealing with rate limits.