this post was submitted on 09 Jun 2023
15 points (100.0% liked)
Free and Open Source Software
17977 readers
21 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?
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.
I'm mainly saying that from the hosting side, especially if you're hosting on a personal IP at home or something, the "nightmare" scenario is that google tracks you down based on information leaks and slaps you with a TOS violation and account suspension. They don't need any actual evidence to screw with you, they hold all the cards regarding their services once they've decided to cause you trouble.
The more likely scenario is that people serving invidious at a scale noticable to google will have their hosting providers slapped with some kind of cease and desist. (Yes, not all hosting providers will have to comply, but many will - why deal with big tech lawyers over something like this?). That won't stamp the service out, but it will make using it trickier and less reliable.