• 1 Post
  • 12 Comments
Joined 2 years ago
cake
Cake day: July 6th, 2023

help-circle
  • I’m not sure if you know this, but…that doesn’t fix most of the security issues in the linked list. All the reverse proxy does is handle hostname resolution and TLS termination (if you are using TLS). If the application being proxies still has an unauthenticated API, anyone can access it. If there’s an RCE vulnerability in any of them, you might get hacked.

    I run Jellyfin publicly, but I do it behind a separate, locked-down reverse proxy (e.g., it explicitly hangs up any request for a Host header other than Jellyfin’s), in a kubernetes cluster, and I keep its pod isolated in its own namespace with restricted access to everything local except to my library via read-only NFS volumes hosted on a separate TrueNAS box. If there is any hack, all they get access to is a container that can read my media files. Even that kind of bothers me, honestly.

    The overwhelming majority of Jellyfin users do not take precautions like this and are likely pretty vulnerable. Plex has a security team to address vulnerabilities when they happen, so those users would likely be a lot safer. I appreciate the love for FOSS on Lemmy, but it is scary how little most folks here acknowledge the tradeoffs they are making.





  • This will affect any server that does not already have a Plex Pass/ Lifetime Plex Pass. If your server does not have one, your remote users will have to pay. The service Plex provides is still worth it though, it largely just works on dozens of platforms and that shit isn’t free to make.

    Sharing a Jellyfin server with others remotely is still a lot more complicated than it needs to be to compete (no, it’s not as simple as opening a port, and if you think so then you’re either lucky or you aren’t sharing with lots of folks). I run both and I would never try to share Jellyfin with non-technical people. Honestly, I wish Jellyfin would start offering an optional paid relay service to fund their development. They could use the revenue to improve their approach ecosystem and still produce mostly open-source software. Homeassistant does this with Nabu Casa and it’s great!

    That being said, the new Plex Android app kinda sucks ass. If there was anything that would make me switch it wouldn’t be having to pay for software, or services it’d be a garbage experience on my most common platform.



  • Intro skipping works pretty well once you set it up and give it time to scan. Functionally, it identifies common audio to determine likely intros, so it can get confused with shows that have different intro music between episodes of the same season.

    Don’t have to change any folder structures unless you were storing optimized media alongside the original files in Plex. All the metadata for both Plex and Jellyfin lives in a SQLite database in your config dir.

    You may wind up transcoding even if you think you really shouldn’t have to. Browsers are weird about supporting some encodings, and both Plex and Jellyfin will automatically transcode to satisfy the client.

    Hardware transcoding is huge, don’t underestimate how impactful it can be. A single 4K CPU transcode could saturate my 72-core server, but one A380 can transcode 3-4 4K streams at the same time. This admittedly doesn’t matter much if you only have one user, but keep it in mind if you ever have to share. It’s so annoying to have a stream start hitching because 1-2 friends decided to start watching something at the same time as you…

    I still don’t have a good replacement for Plexamp either. I think Jellyfin can play music too, but I haven’t tried it myself. I spent a lot of time getting the metadata right in Plex and just haven’t felt like trying to find a way to migrate yet.


  • You can look at some of my other comments for more specifics, but from your language alone I don’t think you’re being objective here. OP states that Plex is flatly better than Jellyfin, and a bunch of Lemmy users hype it up because of a clear bias for FOSS. A reality check is a good thing, IMO; you can prefer a solution and acknowledge its faults, but people talking on the Internet tend towards extremes instead and that will disillusion anyone who tries Jellyfin expecting all the good parts of Plex but better.

    I prefer FOSS everywhere it’s reasonable, but I think a reality check is healthy here. Jellyfin is full of jank that you may run into because a bunch of independent devs are all doing their own thing to make it. Plex is a for-profit entity pulling in the same direction, so the experience is generally going to be more seamless and supported.

    I run both Plex and Jellyfin simultaneously. I use Jellyfin on my devices, except on Android TV because the app is painful to navigate. Plex is way better for sharing, but I usually offer both. I’ve yet to have anyone prefer Jellyfin, Plex tends to just work on their platforms of choice so they go with it. Unless they’re a technical person, it’s unreasonable to expect them to muddle through the edges of Jellyfin.


  • The performance of hardware acceleration in Jellyfin is markedly worse in my experience. My A380 can handle 2-3x more streams in Plex than it can in Jellyfin. My theory is that it’s the jellyfin ffmpeg port slowing things down, but I admittedly don’t have much evidence to back that up beyond the fact that Plex’s transcoder is built on ffmpeg as well.

    Plex Relays are a feature, but that’s sort of the point. You get that stability from Plex by default and it works on all clients. There is no realistic way you’re going to get all remote client devices on a VPN for Jellyfin. Maybe one day Jellyfin can offer that as a paid option, a la Nabu Casa for Homeassistant.

    Media servers tend to get shared around with friends and family and these edges will start to drive you nuts if you have more than a handful of users. I do not want to try to walk a family member through setting up a VPN on their smart TV.




  • There’s a really strong bias on Lemmy for OSS projects. I’m glad they get so much love here, but everything people say here about Jellyfin has to be taken with a huge grain of salt. It works and you can use it. Depending on your needs, it may even work perfectly for you. There are tons of rough edges though.

    Here’s a few:

    • A bunch of basic functionality most people are used to is missing by default. You can get things like intro detection and subtitle downloading to work with plugins, but you have to work at it.
    • Hardware acceleration still kind of sucks. You can get it to work, but the Jellyfin port of ffmpeg doesn’t work anywhere near as well as Plex’s.
    • The variety in app experience is bewildering sometimes. Apps look and feel very different between platforms.
    • Android TV app support sucks. The app is difficult to navigate and has a bunch of weird edges, like subtitle defaults not working. I have no idea what OP is talking about here, it sounds like they’re only judging the app on its animation speed.
    • Public network support is finicky. This is hard to quantify, but I’ve been on several remote networks where my Jellyfin connection dropped in and out and Plex did not. I suspect this is due to the Plex Relay service making up for bad routes between my house and the network.

    Jellyfin is improving all the time, and I hope the recent EFCore update improves performance and development velocity. I’m also holding out hope it will eventually lead to externally hosted databases and active-active servers.

    Disclaimer: I run Plex and Jellyfin and regularly check in on the state of things in Jellyfin. I donate to Jellyfin. I want Jellyfin to be better than Plex. I don’t think any objective measure bears this out yet.