Invidious used to work flawlessly up until about two years ago. Now it seems like Invidious instances always get served with "protecting our community" loading errors, as Google stamp out connections initiated from known instances.
It used to be that a solution would quickly be deployed by the Invidious project, but I get the sense that Google is winning this cat-and-mouse game.
So I've fallen back to using yt-dlp. For a while that worked, but now connections initiated by yt-dlp from my own IP addresses have met the same fate. Instead, I must now proxy yt-dlp, either with a VPN or torsocks. And depending on the exit node, even that can sometimes be blocked:
It used to be that a solution would quickly be deployed by the Invidious project, but I get the sense that Google is winning this cat-and-mouse game.
So I've fallen back to using yt-dlp. For a while that worked, but now connections initiated by yt-dlp from my own IP addresses have met the same fate. Instead, I must now proxy yt-dlp, either with a VPN or torsocks. And depending on the exit node, even that can sometimes be blocked:
The situation is beginning to look precarious for anyone who is adamant about avoiding direct, unsanitized usage of all things Google. I would rather stop accessing Google's content entirely than to acquiesce. What do you do?[ytdl_hook] ERROR: [youtube] AbCdEfGhIJk: Sign in to confirm you’re not a bot. Use --cookies-from-browser or --cookies for the authentication.
Statistics: Posted by Uptorn — 2025-03-04 15:42 — Replies 7 — Views 247