As the maintainer of a relatively large OSS platform (OpenFaaS), I also wrote up about this last year too. For anyone who can't relate to omarroth's statement, it might help with perspective: https://blog.alexellis.io/the-5-pressures-of-leadership/
It's written in Crystal.
It's a viable alternative to Spotify IMO as one use.
It's basically free Youtube Red. Really sad to hear this, hope the creator is better off for it though.
Anyway, Invidious was an extremely useful tool, thanks to the author for making it.
If it's a small channel, you can just copy the channel ID. Visit their YouTube channel, look at the URL, and construct your URL like this:
https://www.youtube.com/feeds/videos.xml?channel_id=CHANNEL_ID
You can also export all of your channels as OPML, which is actually documented (https://support.google.com/youtube/answer/6224202?hl=en) and upload it to your RSS reader.
Indeed. I've been using it to play background music for D&D, no more annoying adds.
I may well wind up hosting an instance following this.
Hopefully the community will pick it up and continue development. Projects like invidious, nitter and bibliogram have turned clicking youtube, twitter and instagram links into something I actively avoid (especially twitter which for which some thing's always gone wrong and I have to refresh) to being a joy to browse again.
https://github.com/iv-org/invidious
> Invidious is an alternative front-end to YouTube
Interfacing with YouTube in any unofficial way is fraught with peril by its very nature because YouTube is always trying to stop it.
Invidious I found to be uniquely and particularly convenient because, for a while at least, it ran like any other website and I could skip the steps needed to self host.
> I can't help shake the feeling that somewhere, the software I use is being developed solely by volunteers who would rather quit, but don't have the ability to say "no".
I've witnessed a number of developers similarly burn out in the last years. This suggest either the opensource movement attracts people prone to such burn-outs or that it produces them. The general reaction tends to be a bit of sympathy mixed with a hard-nosed "Well, it's difficult. Some make it, some don't" attitude. Yet given the trend we seem to ignore a fundamental flaw in how we're working, interacting, consuming, supporting, and rewarding one another. Even Shuttleworth cited a kind of opensource community fatigue when he killed off the phone project. It disappoints me to think that the opensource world talks a lot about freedom at the same time we have Omar's suggestion that those working in it really are not free.
Someone just a couple years ago wrote up an opinion piece in which they asserted that the standard oath for volunteers should be “I promise not to burn out”.
They seem to host a lot of other services as well, such as searx, nitter and bibliogram. I mainly use their searx instance and it is my primary search provider.
They also have hidden .onion instances iirc.
> 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!!]
For your own projects, I would recommend relying on multiple instances anyway because if one has downtime you could just use another one.
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.