We have recently experienced a security incident that may potentially involve your Plex account information. We believe the actual impact of this incident is limited; however, action is required from you to ensure your account remains secure. What happened An unauthorized third party accessed a limited subset of customer data from one of our databases. While we quickly contained the incident, information that was accessed included emails, usernames, securely hashed passwords and authentication ...
In general, for self-hosting, we hardly rely on remote service/server. The whole idea of self-hosting is to shun dependency on external service/server, and run everything on your own hardware and network. So that every aspect of the service is in your control. I don’t think self-hosting comes with much risk, unless you make your service available on Internet.
Jellyfish cannot to setup to securely and safely be exposed to the Internet. It is only safe to access through a VPN. That rules it out as an option for sharing with friends, family, or even my own spouse. You call it phoning home to the mother ship; I call it paying Plex to manage user authentication for me. Until Jellyfin’s security holes are patched and it becomes clear that the Jellyfin developers actually care about security, it stays locked down to my LAN. Setting up a VPN is difficult for the average user on a good day, impossible in some circumstances on even the best of days, and is not access I want to hand out (and support) to all the people I share my Plex with anyway.
https://tailscale.com/ This is essentially a mesh Wireguard Tunnel connectivity that ensures only you can access your service remotely.