Clarify 403 API "rate limit exceeded" errors in the application

[joeyespo]

This has come up several times (e.g. #15, #18, #45) and causes people to come here looking for answers.

Instead, Grip should handle this error inside the application. It can either provide instructions on how to run using --user / --pass or even better, a login form to accept the credentials without requiring a restart.

[sjackman]

👍

[sjackman]

I'm running grip --export from the command line, and the result is an HTML file composed of 403 Forbidden. Could a ~/.grip.conf file contain the username and GitHub API token?

[joeyespo]

@sjackman That's a good idea. Any chance you could open a separate issue for it?

[joeyespo]

Fixed with 88fcc3f.

Here's a screenshot of when you hit the rate limit with this change.

And here's a screenshot of when you hit the limit while using auth. There's less text because you'll probably only use auth after hitting the rate limit the first time.

These can be viewed and tested locally by visiting localhost/rate-limit-preview and localhost/rate-limit-preview?auth=1.