I am dumb enough not to know any current way to minimize quota impact (Google gave me 10K to work with) and it usually uses a lot of them.
As the problem only grew over time, I had to think of a bandaid solution to mitigate the problem- A window popup where users' API (yes you!) can be put in your own YouTube API V3's token to use it (assuming that you like my stuff).
Concept
Okay, so you probably are thinking, why is it so ugly?? I'm sorry for it, but this is the best I can draw...
Into the features:
Ability to pick different tokens from my supply
Check for the token's availability (grey out if not)
Ability to use your key
(Subject to availability) Not sure but let's throw in the "If user consent, donate your API token so others can use it!" WHY NOT!
And best of all, IT WON'T LOG YOUR API KEY IF YOU DON'T WANT!
Once again, this is just a bandaid solution, I'll constantly look for ways to get the quotas down to their knees.
I am dumb enough not to know any current way to minimize quota impact (Google gave me 10K to work with) and it usually uses a lot of them.
As the problem only grew over time, I had to think of a bandaid solution to mitigate the problem- A window popup where users' API (yes you!) can be put in your own YouTube API V3's token to use it (assuming that you like my stuff).
Concept
Okay, so you probably are thinking, why is it so ugly?? I'm sorry for it, but this is the best I can draw... Into the features:
Once again, this is just a bandaid solution, I'll constantly look for ways to get the quotas down to their knees.