Does jellyfin have known vulnerabilities for bots to exploit? It's been up for several years with, afaik, no problems.
System has usual steps taken to harden it, JF is behind an apache proxy, letsencrypt handles ssl certs, fail2ban is running, and users are required to have strong passwords with no option to reset or self-register.
What's the issue? I've run mine exposed for several years...
That would be amazingly impractical. May as well say "what if all website were forced to be .txt files".
Most website template frameworks (Bootstrap/Foundation) etc rely on Javascript for basic UI features. Imagine having to wait for the server to toggle a simple CSS class on your page any time the user wants to view a menu, togle a button, or view a popup/modal/lightbox/whatever.
Blah blah blah... Dude, just clean your damned dishes. Whatever you copy paste from articles it seems pretty obvious that leaving out food waste to reuse it is a pretty bad idea.
So you thought leaving food waste in brine was safe because it would only kill the bad bacteria?
Life started in the ocean, so logically this makes no sense.
Well that was disappointing. Not a single explosion?
Explain?
Apparently, you don't.
All these authors and no one has mentioned the Known Space series by Larry Niven!
Personally I would start with Protector, then Crashlander, then head into Ringworld and the rest.
It's a little dated in places and he's not great at writing women, but it's got some good heavy sci-fi ideas in. The Ringworld megastructure is a fun thing to contemplate.
Like the TV show Dead Like Me, although she was obliterated by a de-orbiting toilet from Mir space station breaking up
A VPN would not be practical for my situation, as the instance is used by various family members and friends. I'm happy for them to use my JF instance but I'm not providing VPN services as well.
If you're not referring to any specific vulnerabilities in JF then I feel confident there are no exceptional risks from allowing web access to JF? Just the usual ones?