"new" Github API rate limit of 60/hr quickly exausted

garyhodgson commented 11 years ago

It seems back in Oct 2012 the rate limit for unauthorised api calls was set to 60/hr (http://developer.github.com/changes/2012-10-14-rate-limit-changes/). A few page refreshes of a githubiverse page will quickly exhaust this.

Need to find an alternative way to access the API.

o-jasper commented 11 years ago

If you can run a bash script or php, you could use thingiviews 'cached' javascript approach, here is a bit poor bash script that generates the data.(was too lazy to look at php for doing the job) Of course you can expect the .js files to be close to the size of the .stls

garyhodgson commented 10 years ago

The following is a workaround (recommended to me by Github a while ago) to increase the number of API requests from 60/hr to 5000/hr. I'm not keen on the fact that the oauth key is exposed, but as long as it is scopes of the token are limited the worst that could happen is someone abuse the token and exhaust your api rate.

Go to account settings in Github and choose Applications.
Generate a "Personal Access Token" and ensure no scopes are selected (it should say "public access" once generated).
Make a note of the token.
From the githubiverse project open up js/github/gh3.min.js
Search for the string a.service and replace it with a.service+"?access_token=xxx" where xxx is your token.
Commit and push to github.

garyhodgson / githubiverse-template

"new" Github API rate limit of 60/hr quickly exausted #5