Find ways to avoid hitting the API limit

[jdm]

Possibly alternate between two accounts for each time the webhook is invoked?

[jdm]

It would be useful to log times when we hit the API limit, too.

[wafflespeanut]

Could this be behind #110 and #112, since we don't know what else is causing such "unpredictability"?

[jdm]

I don't see how it could be responsible for #112.

[wafflespeanut]

Okay, I (must've) misread it. It shouldn't cause #112

[wafflespeanut]

Are we currently going for all events? Because, then, we could associate some set of events to an account - say pull_request for "highfive" and issue for "highfive-2"?

[jdm]

There's no account associated with receiving events. Highfive is in control of which account details are used with each API request it makes.

[wafflespeanut]

This pops in often these days :sob:

[jdm]

Note: rate limit responses look like a 403 Forbidden response code, with an x-ratelimit-remaining header with value 0, with a JSON response with a message field that states that the rate limit was exceeded.