- cross-posted to:
- technology@lemmy.world
- foss@beehaw.org
- cross-posted to:
- technology@lemmy.world
- foss@beehaw.org
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.
I appreciate the cogent context and solution oriented post.
I’d also say though that from a privacy standpoint self-hosting invidious is still allowing GeoIP info to be attached to downloaded videos, which is a fingerprint which can be used by data mining. Admittedly rather abstract as in this case the primary point of deplatforming might just be to de-ad, or give better video control, etc, and not obfuscate for privacy sake.
As I said though great points!
i feel like this makes it on par with eg newpipe right? since newpipe doesn’t have a server, so all requests are direct to youtube
people seem to be okay with the fingerprint trade-off… and a vpn (as in, an external vpn that invidious routes all traffic through) would help with that