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

  • Fijxu@programming.devEnglish
    10·
    2 months ago

    If you have the resources, host your own to help and spread the load across public instances.

    • dan@upvote.auEnglish
      4·
      2 months ago

      They said:

      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.

      and I imagine that most people that host something like this do so using a VPS. Homelabs tend to be the minority use case.

      • irreticent@lemmy.worldEnglish
        1·
        2 months ago

        Plus, some ISPs might frown upon the increase in traffic when hosting a public service.

        I hate my ISP.

        • dan@upvote.auEnglish
          3·
          2 months ago

          Most residential ISPs would frown upon a large amount of upload traffic for a public service, and request that you switch to a business plan with a much lower contention ratio. Contention ratio is essentially the number of people the bandwidth is shared with. For example, if you have a 1Gbps connection with a contention ratio of 50:1 (common for residential ISPs), 50 people share the same 1Gbps bandwidth. That’s designed with the idea that not every user is using all their bandwidth at the exact same time. Constant uploads all day (like with a public proxy) breaks that assumption. Business plans usually have a contention ratio of 10:1 to 20:1.

          The CEO of my ISP (Sonic) explicitly mentioned that they don’t like people hosting servers on their forum:

          We don’t want folks hosting publically accessible servers on Sonic fiber. Primarily because while household consumption can be estimated and averaged, and is roughly limited by your ability to consume (how many TVs will you stream to, plus downloads and other activities, during the peak bandwidth usage time of the day?), when you host the usage is instead limited only by the REST of the world’s interest in what you’re offering.

          So while a family of six with five 4K TVs might see peak average usage under 100Mbps if absolutely every device is on and all consuming full-scale content – a single Raspberry PI web server with a single video hosted on it might swamp a gigabit port if that video file is something everyone in the world wants to see.

          While we can provide the fastest residential connection in America, it’s pricing relies upon typical use cases. That pricing is not sustainable if someone is hosting a popular website, sharing with neighbors, feeding a wireless ISP, acting as a TOR exit node, etc etc. Servers belong in data-centers (aka “the cloud”), for practical network scale as well as economic reasons.

          They don’t block it though, and they’re fine with low-bandwidth things like Home Assistant, VPNs, etc.