-
Notifications
You must be signed in to change notification settings - Fork 146
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Soundcloud API rate limit #248
Comments
it was inevitable that requests max out. those keys are everywhere now. i've reached out to soundcloud to ask about applications. best case scenario, applications open up again, and we can write a little guide to show people how to generate their own API keys, and add them to the script. worst case scenario, we lose access to the API as SC works out what we're doing with them (i imagine this is against TOS of the site to be honest) |
I would have volunteered to give out my keys but they would ended up the same way |
:( |
In #247, I attempted to make travis happy, but travis is not happy
:c
(neither is github actions for that matter)
As HTTP response code
429
is supposed to indicate a too many requests situation, I figured I go and generate a new API key. However:But regardless of soundcloud not providing new keys at the moment, what seems kind of puzzling is that both travis and (for the most part functionally identical) github CI setups fail, but I can runnosetests
locally as much as I please!!?Any ideas about how we can make travis happy?
The text was updated successfully, but these errors were encountered: