Post #3352431

2026-06-19 08:34 UTC

This shit isn’t hard 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.

Replies (2)

@makeshift0546@lemmy.today 2026-06-19 08:46

This is peak Linux nerd shit. No. I payed $200 and Plex is better. My needs have been perfectly met for the past 10l5 years and foreseeable future. Second, fuck off with this attitude. I came here answering a question how, ‘ohhhh it’s so fucking complicated why normies might want to pay’ with 2 concrete use cases and you immediately go off with that nerd bullshit that 8 need to contribute more. I had 3 prs hit main in Apache last week. Fuck off, your nerd shit isn’t helping adoption asshole.

Open ##3352502
@Ghoelian@piefed.social 2026-06-19 15:55

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.

Open ##3354848