-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Youtube API quota #10570
Comments
YouTube is now asking for things like the physical address of our organisation. I had to put a bogus value, hopefully won't cause any trouble. |
After we got the most recent rate limit increase, we decreased the time we cache youtube badges for. Last time we had issues with this, we set them to cache for 2 hours which massively reduced our usage. We could always do this again For a service like youtube where we are presenting number of views/subscribers/comments/likes etc which are indicative stats (this isn't build status passing/failing) and usually presented as rounded numbers we can get away with cacheing them for longer than we do at the moment without much impact. |
Sigh. YouTube are claiming eight violations of their terms and conditions, even though nothing has changed neither on the Shields.io side nor in their policies since last successful audit. This is ridiculous, I'm pushing back. |
Latest audit has been approved, will go ahead and close this issue. |
We received a mail mid-August that I had missed:
And a couple of weeks ago:
We are currently performing between 70k and 80k requests on weekdays, yet we've not yet been rate limited despite the lower quota. However, to be on the safe side as there's little indication on whether they'll further reduce our limit, I'll submit their form a little later. The last audit was barely over a year ago and was a flamboyant display of Google's bureaucracy and appalling developer experience, I'm hoping this will go more smoothly this time around.
The text was updated successfully, but these errors were encountered: