this post was submitted on 22 Sep 2024
710 points (98.4% liked)
Technology
59495 readers
3050 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
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.x
ip are for internal access.google probably can detect how invidious accesses their site
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.
At least until they start blacklisting IPs using Invidious.
One of the positives of nat
CGNAT at least.