this post was submitted on 09 Jun 2023
126 points (100.0% liked)
Free and Open Source Software
17919 readers
118 users here now
If it's free and open source and it's also software, it can be discussed here. Subcommunity of Technology.
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
This is disheartening to see as someone who just switched to Invidious. Does anyone with more in-depth knowledge on how Invidious and similar Youtube front-ends work know if it's possible for Google to shutdown access to their servers for Invidious/Piped instances?
I don't have a lot of knowledge about the technical details of these frontends and I'm probably using the incorrect terminology, but this is mostly an empty threat because
Invidious/Piped do not use the official developer API provided by Youtube, so they can argue that they're not bound by its TOS. There is the concern that Google can implement severe rate limiting per IP to disable proxies or they'll try to make their unauthenticated API private, but people will probably reverse engineer it.
As far as i know, they don't use the youtube api. Therefore they don't have to be compilant with any api policy or tos. They just connect to YouTube like any browser do and then show that information(with modifications) on the invidious app.
Google can try to modify the code faster than the developers try to update the app since they expect the data to be in an specific format, but that's all, they aren't using the api... There is nothing to be closed.
Yeah that's what I thought, that they are scraping like NewPipe is, that usually breaks a couple of times a year when google is messing around with the page, but the developers are usually really quick and fixes it in a day or two so that it works again.
Technical issues aside, they can do legal takedowns on the big instances and while they can also technically do small ones, I doubt they will. The thing is that a TOS violation can lead to a suspended google account, so it's a 'high risk, low probability' event for self hosters with a google footprint (such as an android device).
Hmm, I'm not sure I understand what you're suggesting. The host running Invidious on a server would have a different fingerprint to the same person accessing it through a web browser or phone app. Do Invidious hosters even use a Google account? I assumed it just accessed Google servers like an anonymous user.