The last remaining Invidious instance seems to have stabilized. Unfortunately watching 24/7 livestreams without using a browser (using VLC or etc) seems to only end in IP bans. Nobody has a solution to that and nobody wishes to do the cat and mouse game regarding it cause it "overcomplicates" things.

There's quite a disconnect when dealing with Twitch has become so insanely complicated the uBO project says it is no longer within the scope of the uBO project... Yet YouTube is about to get just as complex or even more complex than the code to support Twitch.

"WHY NOT LEARN CODING AND DO IT YOURSELF?!?"

Have you scrolled back and seen my emotional state of recent? I know it sounds like venting, but try to at least see that it's trying to find a solution for someone struggling, rather than a ignorant cry for help for not understanding how many hours it takes to code a solution.

#fuckyoutube #invidious #livestream #coding

No, asking the source providers of some 24/7 streams to go elsewhere or provide an alternate method is not an option.

Their response will 100% be this:

"Why are you questioning a platform that provides bandwidth for free?"

This clashes with autistic deep rooted values some hold of "Kinda have to make sure it's perfect" which is countered with the general consensus "Why do you need it to be perfect? Compromise a value or two if it's affecting you this severely..."

You have no idea how hard it is for some people to hear they need to compromise their values.

#fuckyoutube #autism #asd

Also, no, proxying through a Invidious instance a 24/7 livestream is only going to kill instances faster, and make you a target for intense scrutiny. Piped already had issues proxying livestream segments, so Invidious enabling that would put far too much bandwidth burden.

#fuckyoutube #invidious

Oh, and if the Invidious instance you are proxying through uses a static VPN endpoint, a livestream will kill the downstream VPN endpoint for everyone.