529
submitted 1 day ago by [email protected] to c/[email protected]

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.

you are viewing a single comment's thread
view the rest of the comments
[-] [email protected] 35 points 14 hours ago

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 healthy

[-] [email protected] 9 points 7 hours 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.

[-] [email protected] 4 points 6 hours 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

load more comments (1 replies)
this post was submitted on 22 Sep 2024
529 points (98.4% liked)

Technology

58164 readers
3196 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 1 year ago
MODERATORS