• coyotino [he/him]@beehaw.org
    link
    fedilink
    English
    arrow-up
    11
    ·
    edit-2
    4 days ago

    Until jellyfin can be 1 click accessed from anywhere securely over clear net it’s not a replacement.

    It can be, speaking from extensive personal experience. I followed their Reverse Proxy guides, now my tech-illiterate friends access my server over https via a duckdns url.

      • coyotino [he/him]@beehaw.org
        link
        fedilink
        English
        arrow-up
        3
        ·
        4 days ago

        Setting up a reverse proxy and dynamic domain is not one click

        Maybe not for the server administrator, but for users, it’s mega easy. Download Jellyfin app on TV. Enter URL for server. Login like a normal streaming service. Done. As far as I know, Plex requires these same steps, so if Plex works for your 89 year old grandparents, Jellyfin would as well.

        Jellyfin has also yet to resolve the unsecured api

        In what way is the API insecure? What types of attacks are you concerned about?

          • coyotino [he/him]@beehaw.org
            link
            fedilink
            English
            arrow-up
            1
            ·
            4 days ago

            I posted this below in reply to a similar comment. If you don’t like the way the devs have handled the raising of concerns, then fine, that’s kind of a judgment call and I can’t tell you what you should feel comfortable with. In my limited experience with the Jellyfin devs (including reading through the responses on that thread you linked), I do not personally get the impression that they are downplaying or refusing to correct issues. To me, it seems more like they are prioritizing some issues over others, and the outstanding security issues seem pretty minor for most use cases.