• dependencyinjection@discuss.tchncs.de
    link
    fedilink
    arrow-up
    0
    ·
    17 days ago

    Each to their own but think you should highlight the failings of Jellyfin.

    Mainly:

    • Remote access is not a trivial feat, especially when compared to Plex
    • The UI is janky.
    • naticus@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      17 days ago

      And that’s why I do Emby instead. Cloud connections are not that difficult to setup, though not as streamlined as Plex. However, I refuse to go back to Plex because of some serious privacy concerns from the last couple years. I have had a lifetime membership with them since like 2014 and it was great for a long time, but I don’t need it tracking activity of my friends.

    • normonator@lemmy.ml
      link
      fedilink
      arrow-up
      0
      ·
      17 days ago

      Interesting. I switched to jellyfin from Plex because the Plex interface was fucking terrible after the redesigned it and jellyfin was so much better even when unfinished.

    • Zink@programming.dev
      link
      fedilink
      arrow-up
      0
      ·
      17 days ago

      The first point is valid, but it only applies to you as the server admin and not the remote users. And honestly it was stuff worth learning for me, as somebody who is not on the IT/web end of things.

      But the UI being janky? I don’t know about that. Static images of the screens may look better to you on the Plex side, and that’s just preference. But when it comes to lag, hitching, did that click register, having the server scan the media library, and just about every other performance thing I can think of, Jellyfin seems SO much better to me.