Youtube API quota

[PyvesB]

We received a mail mid-August that I had missed:

To verify that all use of the API is in compliance with the Terms of Service (including the Developer Policies), we are conducting a periodic audit of API developers. Please complete the audit form, linked below within the next 30 days to ensure continued access to the service. For the reason for filling this form, please choose "I have been selected for a Periodic Audit".

And a couple of weeks ago:

Because we have not yet received your completed form, the API quota allocated to your projects has been adjusted as follows:
--
Project shields-io-XXXX from 200,000 to 66,600 units
Please complete the form as soon as possible. Your original quota will be restored after successful completion of the audit.

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.

[PyvesB]

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.

[chris48s]

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
#9372

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.

[PyvesB]

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.