Well I already have jellyfin running in a container, just have to figure out how to get mum’s TV to work with it I guess

<edit> log in on a local IP and not the network name and it’s working again. but I’ll be moving to jellyfin from now

  • kadu@scribe.disroot.org
    link
    fedilink
    English
    arrow-up
    73
    arrow-down
    1
    ·
    edit-2
    13 hours ago

    Remember when Plex tried to sell you a subscription to use outdated versions of open source game console emulators?

    Plex wants to be a profit-driven company, but their business model is piracy. They’ll squeeze you for subscriptions, while making your experience worse to try and broker a peace deal with content owners.

    • James R Kirk@startrek.website
      link
      fedilink
      English
      arrow-up
      10
      arrow-down
      48
      ·
      edit-2
      6 hours ago

      idk I find $2/month to be very reasonable. I don’t feel squeezed.

      EDIT: Just to be clear there is no amount of condescending replies form trilby wearing neckbeard keyboard warriors that will change my opinion.

      • TeddE@lemmy.world
        link
        fedilink
        English
        arrow-up
        7
        arrow-down
        1
        ·
        8 hours ago

        Setting up ddns takes 15 minutes for a professional (mostly setting a 1-line script to reload a simple url every ten minutes)

        and poking a hole in the firewall takes maybe half an hour (since every router puts the relevant page in a different spot)

        And for this you think it’s reasonable to pay ~$25/year for the rest of your life? You’re not wrong in the sense that you’re welcome to choose your own values, but I … disagree with you on the value position.

        • Mic_Check_One_Two@reddthat.com
          link
          fedilink
          English
          arrow-up
          2
          ·
          4 hours ago

          I mean, you just listed the most insecure way to host Jellyfin. Poking a hole in your firewall will technically work, but that doesn’t mean it’s the correct way to do things. A good setup would use a reverse proxy, and some sort of authentication wall like Authentik or Authelia.

          All of that would only take about 15 minutes for someone who knows what they’re doing. But the vast majority of people setting up Jellyfin for the first time won’t know what they’re doing. And seeing the inevitable “lol just open your firewall” comments only serves to scare them away, because even the noobs have heads that’s the wrong way to do things.

        • vithigar@lemmy.ca
          link
          fedilink
          English
          arrow-up
          5
          ·
          6 hours ago

          I would be ashamed of myself and be tempted to leave the industry in disgrace if setting up DDNS and allowing a single port through a firewall took me 45 minutes.

          • TeddE@lemmy.world
            link
            fedilink
            English
            arrow-up
            3
            ·
            6 hours ago

            Shhhhhhhhhhhhh. I want the newbs to feel accomplished when it only takes them 2 hours to figure it out. 😉

            But seriously, you and I have it on reflex, but there’s merit to the notion that we also have our mise en place - we’ve read the manual, we’ve saved or memorized the script, already know our local equipment passwords, etc - all things we took the time to do before and now have at the ready.

      • Lka1988@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        44
        arrow-down
        3
        ·
        edit-2
        12 hours ago

        To stream remotely from your own server?

        If I chose to use Plex’s plex.tv services to expose my server to the internet, that’s one thing. But I have my Plex server exposed through my own infrastructure (NPM + Let’s Encrypt), so fuck that shit.