fra.gl is a browser-based app for visualizing the relationships between the community artifacts of open source project such as repos, issues, pull requests and collaborators.
Most APIs will have some sort of limit on how hard you can hit them in a certain period of time, and should tell you about it.
GitHub's API, for example, seems to allow 60 unauthenticated hits per hour(?) while authenticated users get 5,000 an hour.
X-RateLimit-Limit:60
X-RateLimit-Remaining:0
After you hit the limit, you start getting back HTTP 403 Forbiddens.
This makes the OAuth authenticator (#1) that much more important, as the "just logging in" approach is probably a long-term solution, but should be kept on the back burner.
In the meantime, a little progress bar would show how much data the viewer (authenticated or otherwise) has left: it would be nice if the static example repo could keep it under this limit, and still be showing fresh data, but 60/hr will prevent many of the more interesting visualizations from working.
bollwyvl
commented
11 years ago
Most APIs will have some sort of limit on how hard you can hit them in a certain period of time, and should tell you about it.
GitHub's API, for example, seems to allow 60 unauthenticated hits per hour(?) while authenticated users get 5,000 an hour.
After you hit the limit, you start getting back HTTP
403 Forbiddens.This makes the OAuth authenticator (#1) that much more important, as the "just logging in" approach is probably a long-term solution, but should be kept on the back burner.
In the meantime, a little progress bar would show how much data the viewer (authenticated or otherwise) has left: it would be nice if the static example repo could keep it under this limit, and still be showing fresh data, but 60/hr will prevent many of the more interesting visualizations from working.