Anyone?

The one you host yourself.

>>108347374
How will one I host be any better at not being blocked than those that have been hosted by experienced people for years?

>>108347611
It's pretty simple. You log in on the server, then you connect to it from another device anonymously.

>>108346638
It was already pretty unreliable back in 2020. Most of the time 720p was the best quality.
I'm sure google has made an effort to kill any proxies like these.

>>108346638
Youtube once again changed something so invidious doesn't work again for a couple of hours. I wonder how much money that's draining from alphabet

>>108347651
If it’s so easy to host why aren’t there more instances?

>>108347661
>>108347949
I disgusting how petty Jewgle are I doubt they even lose that much money by people using proxies and instances as the majority of people won’t even know anything about such methods as well. So it seems pointless going to such efforts to crack down on them unless done purely out of spite.

>>108348447
If it was about money they'd allow us to have some subscription that completely removes their data collection. I'd easily pay 10 dollops cold hard cash just to use it in peace.

>>108348473
Doesn’t Google make a lot of money from selling people’s data?

>>108349136
Openly they just sell ads that work through the collected money. However they'd make much more if they just make each user pay $10/m. They maybe could even kvetch for banner ads or non-personalized ads.

>>108347374
My Piped instance has been blocked for months, even with a rotating IPv6 block. As much as I hate Invidious for its lack of features, does it fly under YouTube's radar when self-hosted?

>>108349208
I didn’t know anyone had any problems with Invidious I always thought it was pretty good with nice features like being able to see annotations, that’s of course when it’s not being blocked.
Are there any front-ends are better and more reliable now?

>>108347611
>>108349208
It's all about IP reputation. Google has to have the best intel on IPs imaginable. Not too hard to imagine, that irregular behavior (caused by invidious instances used by multiple people) will flag the IP as suspicious and ban it temporarily or permanently. This also applies to IP ranges. Running it yourself at the very least allows you to use it normally (granted, you don't share your IP with non-normalfags) and for instance owners to remove some of the bandwidth.

>>108350002
I wonder why the mangers of the project haven’t found a way around this yet they must know what’s causing the problem yet it still persists.

>>108350002
>Google has to have the best intel on IPs imaginable
never happened. they struggle with bots and spam every single second of the day trashing their sites and they've done nothing about it for decades.

>>108351205
they are using proxies, but proxies get blocked constantly. My residential IP gets blocked watching youtube after ~10 videos, then I have to change IP, but without luck I end up with another blocked ip.

I also found out that google doesn't keep track of which ipv6 corresponds to which ipv4, so you can just switch to ipv6/ipv4 when the other one get blocked, but that only extends the issue.

Some people also tried using their google cookie, but it turns out google will block your cookie if it detects you're using a third-party client (or yt-dlp)

these are well documented on yt-dlp issue tracker.

Fixes are in progress:
https://github.com/iv-org/invidious-companion/issues/286
https://github.com/iv-org/invidious-companion/issues/274