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.
That’s a far cry from how most people watch movies and TV though. Most everyone I know uses it through some sort of app on a device in their living room, like a smart TV, fire stick, game console, whatever.
I mean if you don’t want to use it you don’t need to find an excuse, just don’t.
Otherwise, Jellyfin has apps for TV, smartphones and so on; you input address, user and password the first time and that’s it.
For the clients it’s painless, it’s the first time setup as the server owner that takes a little help. But I’m no computer wizard and I managed it just fine.
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?
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.
deleted by creator
deleted by creator
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.
That’s a far cry from how most people watch movies and TV though. Most everyone I know uses it through some sort of app on a device in their living room, like a smart TV, fire stick, game console, whatever.
I mean if you don’t want to use it you don’t need to find an excuse, just don’t.
Otherwise, Jellyfin has apps for TV, smartphones and so on; you input address, user and password the first time and that’s it.
Oh right on. Genuinely didn’t know this
For the clients it’s painless, it’s the first time setup as the server owner that takes a little help. But I’m no computer wizard and I managed it just fine.
deleted by creator
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.
In what way is the API insecure? What types of attacks are you concerned about?
deleted by creator
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.
Ya, I use Jellyfin at home but I left Plex up for my parents to remote stream. Plex is just superior in that regard.
deleted by creator