YouTube legal team contacted us · Issue #3872 · iv-org/invidious
github.com
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 ...

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)

  • Evkob@lemmy.ca
    3·
    2 years ago

    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?

  • comfy@lemmy.ml
    2·
    2 years ago

    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.