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)
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.