The same reason most foss projects are barren. Plex focuses on ease of use and giving people what they want. Users mostly don’t care about the sub. It’s easy to use and works.
Meanwhile jellyfin doesn’t have a remote first interface that isn’t absolute dog shit and I need to set up a reverse proxy and potentially idp to get the ability for my family to log in.
This shit isn’t hard. The answer to the community is, make the product better, and start bundling shit in. But I’m sure I’ve already offended some nerd who thinks this is all just so easy and requires no work to tell me I just need to learn Linux better. And that putting in a reverse proxy by default will make maintenance a pain and I just have to put portainer and LE to fix it.
Well it certainly would be hard for me, as I don’t know anything about the UX needed for these features, and very little about networking in general, and probably close to zero about the networking concepts required to make something like you describe work.
But it sounds like you know a lot, jellyfin is a project that is 100% volunteer developed. Maybe you could contribute your expertise either via code or by providing a concrete action plan to the jellyfin team?
It really, honestly, is super easy to get going. All you need is a folder with your media and a compose file you can find in plenty of tutorials.
The thing we Linux nerds often forget, I think, is that we know what we’re doing (most of us at least I hope), and regular people don’t.
I can read a simple compose file and pretty quickly notice if there’s something off.
If you wanted to do that, you’d first have to read up on containers and compose and all that stuff. You can, of course, just grab a compose file and run it, but that’s generally not a great idea if you don’t know what you’re doing.
The same reason most foss projects are barren. Plex focuses on ease of use and giving people what they want. Users mostly don’t care about the sub. It’s easy to use and works.
Meanwhile jellyfin doesn’t have a remote first interface that isn’t absolute dog shit and I need to set up a reverse proxy and potentially idp to get the ability for my family to log in.
This shit isn’t hard. The answer to the community is, make the product better, and start bundling shit in. But I’m sure I’ve already offended some nerd who thinks this is all just so easy and requires no work to tell me I just need to learn Linux better. And that putting in a reverse proxy by default will make maintenance a pain and I just have to put portainer and LE to fix it.
The shit y’all are bitching about is the problem.
Well it certainly would be hard for me, as I don’t know anything about the UX needed for these features, and very little about networking in general, and probably close to zero about the networking concepts required to make something like you describe work.
But it sounds like you know a lot, jellyfin is a project that is 100% volunteer developed. Maybe you could contribute your expertise either via code or by providing a concrete action plan to the jellyfin team?
Be the change you want to see and all that.
It really, honestly, is super easy to get going. All you need is a folder with your media and a compose file you can find in plenty of tutorials.
The thing we Linux nerds often forget, I think, is that we know what we’re doing (most of us at least I hope), and regular people don’t.
I can read a simple compose file and pretty quickly notice if there’s something off.
If you wanted to do that, you’d first have to read up on containers and compose and all that stuff. You can, of course, just grab a compose file and run it, but that’s generally not a great idea if you don’t know what you’re doing.