[ZinniaZirconium]

Oh that's a shame.

> The API will continue to function until October 1st, to give time for any services relying on it to migrate to other solutions.

Aw no. I was thinking about using invidio.us in my own projects but now I guess I won't!

I have need of a YouTube streaming server, backend only, which I can embed on a web page. I made my own with youtubedown and bash but maintaining it is a pain since YouTube is always changing ciphers and also I forked youtubedown which means I need to adapt my changes to new versions when I upgrade.

So I was thinking of ditching my own and adopting an existing service. Trouble is existing services tend to stop existing. I made my own YouTube streaming server in the first place because I was using HMA YouTube proxy which was always breaking.

So this is a great reminder to me to keep maintaining my own YouTube streaming server.

[I'm using a different VPN today! Is it IP banned?! I don't know. Will this comment be [dead] on arrival?? I don't know!!]

[djeiasbsbo]

There are many alternative instances, that's the great thing about projects like invidious.

https://instances.invidio.us

For your own projects, I would recommend relying on multiple instances anyway because if one has downtime you could just use another one.

[ZinniaZirconium]

Yes except the whole invidious project is rapidly being abandoned according to discussion on GitHub. The next breaking change in YouTube could break invidious forever if the project is unmaintained.

I just need to remember not to be lazy and to continue maintaining my fork of youtubedown. The only obstacle for me is I really don't use YouTube frequently so mostly it's a matter of remembering to do the necessary maintenance.

[saurik]

Why did you decide to fork youtubedown?

[ZinniaZirconium]

I forked youtubedown because it has too many features. I don't want to download any files and I don't want to mux DASH formats. All I want is a script that prints the 360p video url as fast as possible. And JWZ broke support for premuxed video which I added back. And JWZ broke support for requesting a specific cipher which I added back. Basically youtubedown development went in a direction which diverged from my use case.