Important 2025 Plex Updates
www.plex.tv
Personal Media and Beyond You’re going to be hearing a lot from us this year—we’ve got a ton of exciting...

We are also changing how remote playback works for streaming personal media (that is, playback when not on the same local network as the server). The reality is that we need more resources to continue putting forth the best personal media experience, and as a result, we will no longer offer remote playback as a free feature. This—alongside the new Plex Pass pricing—will help provide those resources. This change will apply to the future release of our new Plex experience for mobile and other platforms.

    • MachineFab812@discuss.tchncs.deEnglish
      15·
      12 hours ago

      No idea what Flatpak is, much? Jellyfin is open-source. If your distro isn’t providing you a .deb or tarball to your liking, that’s not on the Jellyfin project.

      • LainTrain@lemmy.dbzer0.comEnglish
        51·
        12 hours ago

        Why would you ever bother to use either option when you can just access it via the WebUI on Firefox?

        • Synestine@sh.itjust.worksEnglish
          15·
          12 hours ago

          Because that basically requires transcoding for modern codecs. H265? Transcode. Subtitles? Transcode. The JF client on the same hardware can usually direct play.

        • MachineFab812@discuss.tchncs.deEnglish
          31·
          12 hours ago

          Don’t ask me? I’ll ftp before I’ll WebUI like so, but for online viewing, I’ll take streaming please. My kids, wife, and mother-in-law find that a million times more convenient.

          Meanwhile, there’s a dude in these comments hating on the notion that Jellyfin’s app will download the Raw file for offline viewing purposes. Please, do not ask me to pretend to care what is going on in that person’s head. In my world, using VLC to play my files is a perk. Gimme that yummy 2x or slow-mo as I see fit, please.

          • Chewy@discuss.tchncs.deEnglish
            3·
            10 hours ago

            I use Findroid for its great UI but also its ability to download and watch offline. It’s a better experience and I was surprised Jellyfin Android didn’t support it.

    • Luci@lemmy.caEnglish
      9·
      11 hours ago

      Flatpaks aren’t the worst, at least it’s not a snap only

        • NuXCOM_90Percent@lemmy.zipEnglish
          6·
          11 hours ago

          Part of it is that Ubuntu/Canonical so aggressively pushed Snaps which became a huge culture war. So you have people who hate the idea of those style of packages because they hate Snap AND people who hate flatpak because they are Team Ubuntu for some reason.

          And the other aspect is that it is incredibly space inefficient (by the very nature of bundling in dependencies) and is prone to “weirdness” when it comes to file system permissions and the like. And many software projects kind of went all in on them because it provides a single(-ish) target to build for rather than having a debian and an arch and a redhad and a…

          • Dojan@lemmy.worldEnglish
            4·
            11 hours ago

            Ah, I see. I’ve not tried Snaps, been avoiding Ubuntu because of Canonical’s weirdly corporate angle. Once they baked in Amazon into Ubuntu I was out.

            I like the bundling of deps. Sure it’s inefficient, but it runs, and storage comes cheap nowadays anyway.

            • NuXCOM_90Percent@lemmy.zipEnglish
              31·
              11 hours ago

              Storage is cheap until it isn’t.

              On my desktop where I have something like 6 TB of NVME storage because I am a sicko? The only thing that makes me think twice about a flatpak is if I need to give it access to devices or significant parts of my filesystem (yay permissions weirdness).

              On my laptop where I can have one drive and replacing it involves opening the entire laptop AND reinstalling Fedora (or dealing with clonezilla/dd)? Yeah… I very much care about just how much bloat I am dealing with. And, as the other person pointed out, flatpaks can balloon REAL fast.

          • mutual_ayed@sh.itjust.worksEnglish
            2·
            11 hours ago

            A lot of flatpaks early on wouldn’t survive a major point release upgrade or worst case would hold on to dependencies and the user would end up with an unbootable mess after an upgrade.

            I haven’t seen that recently though.

            However I regularly run appimages on my fedora silverblue system so take what I say with a grain of salt.

            • NuXCOM_90Percent@lemmy.zipEnglish
              2·
              11 hours ago

              If dependencies are articulated (and maintained…) properly, it is very doable and is intrinsically tied to what semantic versioning is actually supposed to represent. So appfoo depends in libbar@2:2.9 and so forth. Of course, the reality is that libbar is poorly maintained and has massive API/header breaking changes every point release and was dependent on a bug in libbar@2.1.3.4.5 anyway.

              Its one of the reasons why I like approaches like Portage or Spack that are specifically about breaking an application’s dependencies down and concretizing. Albeit, they also have the problem where they overconcretize and you have just as much, if not more, bloat. But it theoretically provides the best of both worlds… at the cost of making a single library take 50 minutes to install because you are compiling everything for the umpteenth time.

              And yeah… I run way too many appimages too.

          • anamethatisnt@sopuli.xyzEnglish
            1·
            11 hours ago

            The space inefficiency is definitely there.
            I find that clients, such as Jellyfin, Moonlight and Signal, works just fine as flatpaks but with those three apps my /var/lib/flatpak/ lands on 6.4GB.
            When I temporarily had Discord installed it grew to 6.7GB, so the inefficiency is frontloaded and lessens the more of them you use.