They don’t understand that we never agreed to any of their TOS/policies, they don’t understand that we don’t use their API.
What now?
Things will continue normally until they can’t anymore.
Assume it’s just the start.
Assume they’ll ask GitHub to takedown the repos (if so go to our Gitea https://gitea.invidious.io/iv-org ).
Assume the team wont be able to work on Invidious.
You know what you have to do.
May Invidious live and prosper, with, or without us.
PS: We won’t do anything unless we have to.
PS-2: If we are forced to quit, any funds remaining will go to Framasoft (and maybe some other organization working on FOSS/privacy)
Jesus its like Elon Musk was the prophet for the Fuckheads Who Will Ruin The Internet For Money. Big Tech can suck my asshole.
Google and Youtube have been sucking [insert preferred pejorative metaphor here] for ages; Musk just says the quiet part out loud.
But at least people are listening
They’ve all been waiting for the first domino to fall for a while. No one wants to be the first one to make a naked money grab, but once someone does, everyone gets to move.
deleted by creator
I didn’t know Invidious existed until this happened. Barbara Streisand effect in full swing
deleted by creator
Reposting the classic:
I just want to say the maintainer who wrote that appears to have handled this gracefully. It gives me hope.
They’ve made a transparent public announcement, making it clear what we should and shouldn’t expect from them, and how we should handle it. They understand the FOSS paradigm (no, I correct myself, the digital paradigm) and have given their blessings for the community to do what they do best. I’d guess the smart thing to do is play along with the cease notice to avoid consequences, go underground and make YouTube play whack-a-mole with sock-puppets and hostile jurisdictions.
Cut off one head and three shall take its place. Wind in your back lads, wherever you go.
Oh my, good luck to the Invidious team, I hope this will be resolved quickly and without the need of lawyers.
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
The only way Youtube could [restrict access to Invidious/Piped for good] is by making a Google account required to watch videos. Logged out users on Youtube’s official services like its website and mobile app currently use the same API endpoints these frontends use, so breaking those endpoints would disable its actual services for users without an account as well. You’ll notice that you cannot perform any logged in actions with a Google account on these frontends, and that’s because the frontends only use endpoints that don’t require authentication like watching videos and reading comments. This is the same reason why Twitter hasn’t shut down Nitter (the read-only privacy frontend for Twitter) yet, even though they would really want to.
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.
Does that mean they will also be targeting Piped?
I really hope not. Piped has been the only way I use youtube for a while now and it’s a far better experience then actually having to use their web app.
Google and the rest of these types of companies are constantly targeting possible competitors/alternatives with their legal wing. They’ll just sit and collect as much data as they can until they feel its the right opportunity to hit them with a DMCA or some other legal crap they can get away with since they have legal teams on the payroll.
Wow! I just setup my own instance of Invidious. Interested to see how this shakes out.
Best of luck to them.
Death To Reality.
