• Virtvirt588@lemmy.world
    link
    fedilink
    English
    arrow-up
    15
    ·
    2 days ago

    Jellyfin is FOSS. Taking a single step towards the Plex route will be going against the ethos of Jellyfin as a whole. It is community owned - rather than private, and if there are unethical practice’s involved, then people can and will jump ship forking the whole project at nearly 1:1 scale.

    Because of the way jellyfin is built and the underlying philosophy. It can’t enshitify that easily as Plex - it will need a massive community effort to change it.

    It is also useful to read on the history of jellyfin as it does highlight some useful pointers.

    • rumba@lemmy.zip
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 hours ago

      That’s all correct, but… we aren’t absolutely in the clear. JF could absolutely be forked, DB changes enacted, security added, but you also need all those client devs to come along.

      It’s not quite like most Foss where a couple people could jump in and do a better job, JF has a LOT of moving parts supported by a number of individuals.

    • phx@lemmy.world
      link
      fedilink
      English
      arrow-up
      9
      ·
      2 days ago

      Also, Plex controls the login/authentication through their portal, and can also receive data back from your host regarding the content being shared/watched.

      Jellyfin is 100% locally configured accounts

    • Scrollone@feddit.it
      link
      fedilink
      English
      arrow-up
      7
      ·
      2 days ago

      Jellyfin itself is Emby. Emby was owned by a company and it enshittified at the speed of light, and that’s when Jellyfin was born (by forking the last open source version of Emby).