MaggiWuerze

https://github.com/jellyfin/jellyfin/issues/5415

The magic bullet in that sentence is VPN not reverse proxy

Doesn’t do shit when large parts of the Backend are not authenticated

Because Plex handles the initial connection for you allowing the clients to lunch through CGNAT and other shit. Also they handle the authentication, which I would fully agree would be nice to have independent, but that’s the reason

They can stream content from your server or map out what you have on there by using a rainbow table. Depending on the country you live in they can and will use that combined with your IP to start litigating you

After setting up an elaborate VPN scheme

The giant unsecured barn door that is the Jellyfin backend

Yeah, no way. Jellyfins Backend is like an open barn door. And with the kind of content most of us here offer through either Jellyfin or Plex, I wouldn’t want to open up like that.

Yeah and expose the unsecured Jellyfin Backend to the whole world. Nice

Honestly yeah. The Jellyfin Backend is basically unauthenticated for a large part, allowing anyone to map and stream your content as soon as they guessed the ids, which isn’t that hard, since they are based on the paths on your device. So if your movie sits in /mnt/media/movies/the_bee_movie that is pretty esay to guess and calculate the id from, allowing anyone to stream that content from your server

And they actively refuse to do anything about them because it would force clients to update. You could just just as well open an unsecured ftp server to your content

External servers are shared with you, they can just check which owners have libraries shared with them. That’s not some nefarious logging, its information they need to offer that function

Exactly, most people that share co tent with others already have the Plex pass so this doesn’t do anything to them or their users.