• dependencyinjection@discuss.tchncs.de
    link
    fedilink
    arrow-up
    8
    arrow-down
    3
    ·
    5 months 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
      2
      ·
      5 months 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
      2
      ·
      5 months 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.

    • rudyharrelson@lemmy.radio
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      5 months ago

      Setting up remote access for Jellyfin felt pretty trivial for me like 2 years ago when switching away from Plex. No hiccups that I can recall whatsoever. Except for maybe the nginx reverse proxy configuration, but the documentation made it decently straightforward, but that step isn’t strictly necessary to get remote access working; that was just something I wanted for my particular setup.

      And I wouldn’t call the Jellyfin UI janky at all. I use it every day and can’t think of any common issues I encounter when using it. There surely are quirks with some features, but I find them few and far between. I recall Plex having its own UI quirks back when I used it.