Yup already addressed this in another thread.
You have to take on supporting them now... supporting family is just like loaning money to family... or renting to family... or anything else with family. Stressful.
But even silly problems like what happens when their wireguarded phone connect to the wireguarded home wifi vpn... I can't imagine that it wouldn't cause problems that you're going to get blamed for.
But even then this is still jellyfins problem. It's clear the platform is MEANT to be public, otherwise there would be some integration with these other features that just don't exist.


It's not FUD if it's real. I could say the same shit for people screaming Jellyfin at literally every chance they get when the topic is Plex. Instead I further the discussion rather than telling other people they're spreading FUD.
It's an MD5 hash of the file path. Not randomly generated, and not a proper UUID.
Edit: for others that might not understand... Docker files will standardized the path side... *arr suites and general human nature will standardize the file name.
So a generally guessable file path exists for a LOT of users out there... It's absolutely possible to guess that many people running jellyfin would store their version of bigbucksbunny as /movies/bigbuckbunny (2008)/bigbuckbunny.mkv or similar conventions and I've probably already nailed the path to generate the MD5 for a lot of people running Jellyfin just now.