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.
So if Google can ban our IP if caught using this, could you not use some type of dynamic IP mechanism every time they ban the IP?
Probably would be a good idea, I’m guessing this type of thing could be problematic for google if the IP bans started stacking up, probably also if they can’t just look up what the site is using and banning it manually, which let’s be fair and not give them too much credit, is exactly what they’ve been doing. They look up that some invidious or downloader site is hosted on some IP address and block it manually, or blocking its whole range. Something that doesn’t cause many headaches for others outside of those services but would cause a lot of problems if those sites were run with reverse-proxying to dynamic IPs which caused YouTube blocks for legitimate users, including in public places.