-
-
Notifications
You must be signed in to change notification settings - Fork 335
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
Investigate alternative video info API (used for determining if a video is new and whitelisting) #751
Comments
If you're able to do OAuth signin, the YouTube data API has videos.list; if you call it with a However I think this approach does require registering your app with Google and there's a quota on it; by default you can only query this API 10,000 times a day, although you can ask Google to get that raised. (Although considering the nature of this extension they probably wouldn't be particularly happy to.) |
They don't like that it "modifies the YouTube UI", so refused my quota extension, so it will have to be through an unofficial API. |
Yeah, that's unfortunate, but expected. Oh well. Hopefully you can find something... I've noticed that YouTube is lately very aggressive about detecting anything that looks like data scraping and they're going out of their way to prevent it. I wouldn't be surprised if they purposefully made the channel ID take longer to show up just to prevent things like this from working well. |
You could give my API a try: The channel id can be found in I also have servers in 3 locations which should help you with latency, wherever it is. |
@FireMasterK Thanks, but I don't want to leak the videoID to any 3rd party services, since the extension now uses ajayyy/SponsorBlockServer#25 to prevent leaking the videoID to the SponsorBlock server. |
In that case, you could consider using the innertube api for this which should have this information. |
zerodytrash/Simple-YouTube-Age-Restriction-Bypass@1874086 This might only work or the initial video. |
Adding |
The API previously used to get channel IDs doesn't work anymore (#741). Right now, it is reading the channel ID from the page, but this is slow as that part of the page loads late. It also does not work on Invidious embeds.
Another method to determine this, such as by an API call, would solve this.
The text was updated successfully, but these errors were encountered: