this post was submitted on 10 Jun 2024
1 points (100.0% liked)
Late Stage Capitalism
5615 readers
1 users here now
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
So I’ve been looking at invidious, and like lemmy (until Apollo shut down) I was intimidated by the sheer number of instances and not really knowing what’s the difference
Any quick advice
They're all instances of running the same software, with a few tweaks here and there. Google has been trying to stomp out Invidious recently because google hates human rights and all that, so it's an arms race to keep the instances running while google blocks domains, ip addresses/blocks, vps hosts, and apis. Everyone running the instances are trying to keep invidious up and some are having more success than others.
libredirect is a browser plugin that can set a customizable list of working/preferred invidious instances. If one doesn't work, you can click a link on the video page to switch instances. I have pretty good luck with yewtu.be , inv.tux.pizza , inv.nadeko.net and invidious.drgns.space
If you host your own invidious instance on a network with a non-static IP then a ban will only ever be temporary. It happened to my private instance many times. I found that setting the channel refresh interval in the config to 2 hours makes it less likely (or basically 0% if you're the only user) for them to block your IP.
How easy has it been to find (presumably?) vps hosting able or willing to accommodate the IP bans from google? I feel like at some point google is going to go hard against the hosting on these ip-rotated instances.
My instance is running on a Server in my homelab. The dynamic IP is just how my ISP works. I've been running this instance since late 2019. So far Google has only ever blocked my IP whenever I hit their Servers with too many API calls too quickly. Last time they blocked me though was probably 1/2 - 2 years ago. The current version of Invidious does try to minimize API calls which helps a lot. Honestly Google changing API calls/value names and patching the source code is more annoying to deal with than IP bans.
The only way I can see them permanently blocking instances with non-static IPs is if they go down the Twitter route where you can't even view anything unless you're logged in.
Is it a public instance or just for you and your fam/comrades? But yeah, mandating a login requirement is what I've been afraid of. I would just stop using yt altogether if it came down to that.
It's a private instance. Maybe I'll open it up, not sure.
Same. Once they go that far I'll just
# zfs destroyInvidious and move on to PeerTube. I hope more people will move as well when that happens.Thanks for the crash course :D