As long as the technical person does all of the setup on their end, the non technical person only has to enter a domain and port in their jellyfin client.
Comment on That's all folks, Plex is starting to charge for sharing
chaospatterns@lemmy.world 1 week agoIts not difficult for technical people like you or me, but my friend who just wants to watch their favorite show on my Plex on their TV won’t know how to traffic engineer the traffic over a Tailscale network to my network.
ada@lemmy.blahaj.zone 1 week ago
PP_BOY_@lemmy.world 1 week ago
thundermoose@lemmy.world 1 week ago
If you want to be on the hook for all IT requests from folks you share with, this is a fine approach. There are people out there who honestly don’t have a problem with that and more power to them. I doubt they are the majority, and a lot of selfhosters completely ignore this aspect of software. There is a reason non-free services exist beyond just “capitalism bad.” I mean, capitalism indeed bad, but your time is worth something.
ada@lemmy.blahaj.zone 1 week ago
I guess I haven’t noticed that. The non technically literate folk I know use smart TVs, or can download Jellyfin from an app store. Then they just use the URL when the app asks for it.
There’s no other configuring to do on their end.
catloaf@lemm.ee 1 week ago
They also need to run a VPN client.
Because you’re not putting bare jellyfin on the internet, right? You shouldn’t be doing that for most services in the first place, but doubly so for something that has a bunch of APIs that require no authentication: github.com/jellyfin/jellyfin/issues/5415
ripcord@lemmy.world 1 week ago
I’m also not particularly happy with giving a bunch of people VPB access to my setup. Or other potential complications that come with that setup.
I know enough to be able to lock it down, but I dont want the hassle. And other people will want it less.