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.
The elites don't want you to know but "[y]ou may be able to get Invidious working on residential IP addresses (like at home)"
Following their guide gives a local Invidious client, don't forget to 1) copy their production compose file instead of using the one on git and 2) change "hmac_key"... from my experience setting up cron (
crontab -e) to restart the docker container once per day keeps the Invidious docker healthyEdit: here are some alternatives for popular Google services. Not in anyway related to the above (smirk
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.
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.
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
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.xip are for internal access.google probably can detect how invidious accesses their site
At least until they start blacklisting IPs using Invidious.
One of the positives of nat
CGNAT at least.