Evalai: 403 Forbidden response from Github API

[deshraj]

See the screenshot below for more details about the error:

[DakshMiglani]

Hi, to fix these we need an authentication token from github, so i'd request the team leaders to create a client id with a secret and then we can request the api url which will look like:
https://api.github.com/users/whatever?client_id=xxxx&client_secret=yyyy

[aka-jain]

Thanks @DakshMiglani for the suggestion.
@deshraj, @RishabhJain2018 any action on this?

[deshraj]

Hi @DakshMiglani, thanks for the suggestion. We would like to leave it as it is for now. We cannot expose the client_id and client_secret since we are requesting from the client side. We would love to have suggestions from the contributors for various workarounds for this problem.

[adamstafa]

@deshraj Currently unauthorized users (user is determined by his IP) can make up to 60 requests per hour so for normal usage this won't be a problem.
Another option is to create a view in backend to access the API with the token. The limit would be 5000 per hour but for all users. We would need to limit the refresh-rate of these stats then.

[deshraj]

@Obtin please feel free to take this issue. :)

[deshraj]

@Obtin: I just thought about a new way of doing this. Can you integrate the https://buttons.github.io/ for showing the fork and star button? It will help us to remove the dependency of Github API and just use this service.