Plex is starting to enforce its new rules, which prevent users from remotely accessing a personal media server without a subscription fee.

If anyone needs it: https://jellyfin.org/

  • Kushan@lemmy.world
    link
    fedilink
    English
    arrow-up
    25
    arrow-down
    15
    ·
    edit-2
    6 hours ago

    This is a "slippery slope’ argument and thus a fallacy.

    Let users decide how they want to run their own stuff. Right now if you have Plex pass this isn’t an issue. If it becomes an issue, then you’re in the exact same position you’d be in today if you decided to move away from Plex now.

    I moved away from Plex years ago, but I don’t blame users for sticking with it, it still has a lot of advantages over jellyfin.

    EDIT: Y’all are trippin’ over yourselves to complain about what other people choose to deploy on their own hardware.

    • ShortN0te@lemmy.ml
      link
      fedilink
      English
      arrow-up
      14
      arrow-down
      1
      ·
      8 hours ago

      If it becomes an issue, then you’re in the exact same position you’d be in today if you decided to move away from Plex now.

      I disagree. Right now you got time to do the research, plan the move and test it out with a demo setup. You do not know if you got the time if Plex decides to screw their lifetime users.

      Yes this is hypothetical.

      • moseschrute@lemmy.world
        link
        fedilink
        English
        arrow-up
        13
        arrow-down
        3
        ·
        7 hours ago

        The steaks are very high. I could lose access to my media library for 1-2 evenings (the time it would take me to switch to Jellyfin).

      • Kushan@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        arrow-down
        10
        ·
        7 hours ago

        It’s entirely hypothetical. Jellyfin could also close source tomorrow, hypothetically (It happened with Emby so there’s precedent).

        • festus@lemmy.ca
          link
          fedilink
          English
          arrow-up
          12
          arrow-down
          1
          ·
          edit-2
          6 hours ago

          Jellyfin can’t go closed source as it’s a fork of Emby from before it was closed source, licensed under the GPL. They don’t own that code so they can’t change that license, thus the whole project is GPL. In addition, Jellyfin isn’t being developed by just one company (it’s all volunteers), so every new contribution is also GPL licensed, owned by each contributor. The only way Jellyfin could go closed source would be to cut out the Emby backend and for every single contributor ever to agree to change the license, or have their code cut out. In short it’s not happening, and if somehow it did the project would just get forked regardless for everyone to switch to (the community did it once already!).

        • ShortN0te@lemmy.ml
          link
          fedilink
          English
          arrow-up
          6
          ·
          7 hours ago

          No, you have not understood anything. Assuming Jellyfin would go closed source, (ignoring the GPL license and so on) you would not notice anything. Your server and service would be unchanged by this.

          Emby is the best example, the community will fork it and you server lives on. Even if not, then the server and software is still yours.