Sharing and remote streaming, plain and simple. I have no problem setting up accounts for friends, but choosing your server is a pain for some. But the bigger problem is that the first thing anyone will say is: Don't expose Jellyfin to the Internet. That's a bit of a problem.

And they'll then say, "Oh it's not so bad just set up wireguard and..." This is the ramblings of a lunatic. I've been working with tech a long time. Tech is my job. It is my hobby. I do all of it from repairing my own hardware to administering servers to running my own home lab to doing open source development. Wireguard is not friendly. It is not something I'm going to set up at every friend and family member's house so I can share my library.

I've got a more secure but imperfect setup in sticking Jellyfin on the Internet behind a proxy that requires login. But this is not something most people are going to want to deal with. They want to stand up their server and then share it with people.

[–] akilou@sh.itjust.works 8 points 5 days ago

Couldn't have said it better myself. Very Give a Mouse a Cookie vibes when talking to someone explaining how Jellyfin is a drop in replacement for Plex when they're on step 6 of setting up remote access

[–] FundMECFS@anarchist.nexus 5 points 5 days ago (1 children)

Realistically what could the jellyfin devs do to make this easier?

[–] psivchaz@reddthat.com 7 points 5 days ago (1 children)

One thing is prioritizing security. There's a number of known flaws, of varying severity, which is why most people would recommend not exposing Jellyfin to the Internet.

Perhaps they could set up a second project, a Jellyfin meta-library, whose whole goal is to be exposed to the Internet. You stand that up, give it access to other Jellyfin servers, and it handles the work similar to STUN of connecting you to media on those servers. This would make it so people could share easier.

[–] FundMECFS@anarchist.nexus 3 points 5 days ago

Interesting. It would still be complex I guess but mean that it’s less risky to expose.

I’m still a bit out of my depth on networking I just use jellyfin locally. Ive set up websites and stuff but never had to play with reverse proxies.

[–] waz@feddit.uk 1 points 5 days ago (1 children)

I would have done this, but set up ‘meshnet’ to make the remote computers look like they’re all on the same network, but nordvpn just pulled the plug on meshnet and are decommissioning it in December. Goodbye

[–] rainwall@piefed.social 3 points 4 days ago* (last edited 4 days ago)

Tailscale has this same functionality, and is free for something like 100 hosts. Uses wireguard as the backend tech. It also has apple tv and android clients, so you can setup the Tailscale app on an end client for a user, then setup the jellyfin client and they should be good to go. That client device will just "see" your jellyfin server as a local client on the same network, albeit a tailscale wirrguard overlay network.

I haven't actually deployed it as I don't share my media server currently, but I was investigating it a bit ago.