Debatable. It is an incredible piece of FOSS, but whether or not it’s better than Plex really depends on your use case. Plex is much better for remote access and the “wife factor”.
The initial goal of a self-hosted video platform must be encouraging adoption. And you have to follow a “the customer is always right” (the actual meaning, not the bastardized Karen-screaming-at-customer-service version) mentality in regards to this; Even if you have the best Jellyfin server in the world, it’s ultimately worthless if your friends and family refuse to use it. Your service needs to be accessible to the average user, and the unfortunate reality is that the average user doesn’t even know what a port number or IP address is. When trying to encourage adoption, you’re facing a lot of social inertia in regards to people simply going “eh, I know Netflix isn’t perfect, but it already works.” You need to provide a service that is superior to other platforms in some meaningful way. And simply being free isn’t enough value for some people, because individuals will weigh the cost differently depending upon how heavily they factor it into the Cost:Convenience ratio that they’re willing to tolerate.
And this is where the wife factor comes into play: Is your spouse/partner going to be willing to use it? Does it provide enough convenience that they’ll be willing to ditch the streaming services? Now how about your extended family? And if you’re only ever planning on watching at home on LAN, Jellyfin may be perfect. But Plex’s unified login experience is much easier for the average user to understand. I can walk my mother-in-law through the account creation and login process over the phone, because it’s familiar. If she can figure out how to make a Netflix or Hulu account, she can figure out how to make a Plex account. You simply sign in, and your available libraries show up. Easy.
But Jellyfin will never be able to provide a unified login experience, because the entire platform is built to rebel against that; A unified login would require a centralized authentication server like Plex runs, and that’s specifically what Jellyfin is designed against.
_cryptagion@lemmy.dbzer0.com 3 weeks ago
That’s a whole lotta words to say you don’t know how to set up Jellyfin correctly.
My whole family loves it, they use it across quite a few different devices, and they enjoy the fact that they can get anything they want using Jellyseer. And since I’m not some paranoid nutter that thinks having my services exposed to the web is going to be the end of my life, they also enjoy the unified account experience that the LDAP server provides them, where they can manage their SSO password and 2FA from an easy-to-use web interface that in turn allows them to access all the other services on the server, and from any device anywhere in the world without needing to do stupid stuff like upgrade their router for Tailscale.
chiliedogg@lemmy.world 3 weeks ago
If it’s more difficult to set up, then it may not be better for everyone.
mic_check_one_two@lemmy.dbzer0.com 3 weeks ago
I’d agree with you on the surface, except for the part where virtually every single comment on Lemmy about Jellyfin’s remote access basically boils down to “lol just tell them to use Tailscale. It works fine for me ¯\_(ツ)_/¯”. Again, I’m talking about the average user.
And it’s not about being a paranoid nutter. Jellyfin has had multiple exploits in the past. Hell, it had a code execution vulnerability from unsanitized FFmpeg API inputs published just last week.
gnuplusmatt@reddthat.com 3 weeks ago
If you run it in a rootless container, expose it through a reverse proxy and keep it updated there’s very little risk