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:

1. Ability to pick different tokens from my supply
2. Check for the token's availability (grey out if not)
3. Ability to use your key
4. (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!
5. 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.

Now it is pretty obvious that my current codebase is SHIT, and I don't think that we can do worse.

So for now, along with "Edit Front Screen" feature rolled out, I will be doing a full rewrite in a separate branch, with flexibility and reusability in mind. Full detail coming soon!

Every commits has reset, and reduced to atom. Well, it's for the greater cause!!

I also would love to talk more about the project,

I AM EXTREMELY BURNT OUT

I can't do much, assignments are ass and I don't like it much (it's becoming repetitive and harder to get through). I also tried out Roblox Studio with LuaU, it's alright but I don't like game development in general. Shushhh

I've noticed the issues randomly while just using it like normal, nothing fetched at all...
The JS that responds to all of this isn't it either, and 403 is mostly related to the API from which I'm trying to get the data. But here's the problem:

1. In my local machine with Dev Key (no restriction), I still got the issues
2. On the API dashboard, all of the requests that I've made so far are under 200 (since the bug started, the error % has been at 100%; in normal circumstances, it was within 2-3% only)
3. I've asked most of the people who work with API, and they have no idea what is going on with my case

So yeah, I don't know man... I'll keep in touch with virtually no one (think of this like my diary). Thanks!