[Bug] "This helps protect our community." · Issue #4734 · iv-org/invidious
github.com
Update 21/09/2024: #4734 (comment) EDIT by @unixfox: The Invidious team is aware of this issue. It appears that it affects all the software using YouTube. Please refrain from commenting if you have...

cross-posted from: https://discuss.tchncs.de/post/22423685

EDIT: For those who are too lazy to click the link, this is what it says

Hello,

Sad news for everyone. YouTube/Google has patched the latest workaround that we had in order to restore the video playback functionality.

Right now we have no other solutions/fixes. You may be able to get Invidious working on residential IP addresses (like at home) but on datacenter IP addresses Invidious won’t work anymore.

If you are interested to install Invidious at home, we remind you that we have a guide for that here: https://docs.invidious.io/installation/..

This is not the death of this project. We will still try to find new solutions, but this might take time, months probably.

I have updated the public instance list in order to reflect on the working public instances: https://instances.invidious.io. Please don’t abuse them since the number is really low.

Feel free to discuss this politely on Matrix or IRC.

  • ShepherdPie@midwest.socialEnglish
    251·
    1 month ago

    If you do this, I would be fully prepared to lose access to all your Google services along with anyone else who may use Google services on the same IP. Gmail, Play store, Chrome, etc, etc can easily be wiped out with a ban from Google and this can seriously fuck people’s day up if they’ve used Gmail and have 2FA setup on any external account.

    • zlatiah@lemmy.worldEnglish
      91·
      1 month ago

      I guess I forgot to take that into consideration… I’m not worried about Google banning my IP since I essentially don’t use any Google services at all and my home IP is hidden behind a wireguard tunnel, but yes that is a valid concern

      But I mean someone can just spin it up on their home network so… No way 192.168.0.1:3000 can get someone into trouble right

      • curry@programming.devEnglish
        5·
        1 month ago

        Like any other web services, Google can see the public ip your personal invidious instance is using to access youtube servers. The local 192.168.x.x ip are for internal access.

    • r0ertel@lemmy.worldEnglish
      5·
      1 month ago

      Cory wrote about this in his essay, "Unpersoned". I’ve been using gmail as a spam catcher for all the sleazy sites you need to register with, but didn’t realize how I’ve made a trap for myself when, for example, my prescriptions need 2 factor authorization via my gmail. This is going to be a hard one to detangle.