“…the acid-throwing remark had been reported as a passing comment, not a threat…”

Excuse me, but in what context is that not a threat?

Introducing: RHEL but worse!

Introducing the Protecting Children From Woke Groomer Computers Act in 3… 2… 1…

I agree with the folks saying reverse proxy of some kind + WAF. That way end users don’t have to deal with the VPN, but your home system is not directly exposed.

I’ve been doing something similar with SSH local port forwarding and a $5/month VPS. Haven’t come anywhere close to my network quotas, and performance has not been an issue for home use with 2-5 concurrent users most of the time. I forward the local caddy ports to unprivileged ports/user on the VPS, then use the firewall on the VPS to forward that port to 443 and lock down the rest.

Oh no! “It could also further erode public trust in the tech.” Don’t threaten me with a good time.

That said, VPN would be much more manageable if I was trying to really push performance or scale out the network.

Hoping Vaultwarden comes out unscathed—at least for a while!

FWIW it seems Jellyfin has some application-specific authentication/security bugs that complicate things a bit. Of course the same concepts should generally apply, but some considerations will be different depending on what application you’re exposing.

Could do it by absolute value, so things that rise also cost more? /s

Those democrats and their “branding” JFC

Do you have a link to that blog post, by chance? I’d like to learn more!