this post was submitted on 26 Nov 2025
94 points (97.0% liked)
Technology
40769 readers
295 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.
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?
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.