people who host publicly-facing servers at home (not on a VPS), do you just directly use your home IP address w/ port forwarding or use a tunnel to a VPS (or a service like CF tunnels) with a reverse proxy?
@norm back when I did this I had a Linux box as my router so I had a reverse proxy running on that proxying over to the server at home (so it can have a dhcp lease and everything), which came with the extra funny added benefit of being able to reverse proxy direct to containers if THEY go through dhcp and get picked up by dnsmasq etc, though I think what allowed that to work has been broken since
@norm Its kinda mixed here lol. I tunnel through a VPS but not for privacy.
My privacy is fucked by having that imprint (government mandated) on my sites. I tunnel I can have IPv4 Traffic to my home. Otherwise I would just the IP at home as is.
@norm Mix of both. IP gets tunneled in from a friends router bc my provider only gives me a single dynamic /64. Im lucky enough to not sit behind CGNAT so my Legacy IP is native
@norm why would you tunnel unless you don’t have a public IP, or you can’t be arsed to setup a ddns resolver? there are very few reasons not to just use your IP…
@domi@norm i'd never host on my home ip despite having a public one bcs it's basically a free doxx [small local isp] also the VPS is a nice point to cache things so a fedi post going viral doesn't destroy my home internet
@wolf480pl@norm@snow with this sort of threat model you should be tunneling ALL of your traffic through a vpn of some sort. there’s plenty of ways an attacker can discover your home IP otherwise.
@norm (nice hostname btw) I am using @eleboucher 's instance of towonel on his VPS: it gives me the convenience and comfort of Cloudflare Tunnel, without giving them data or allowing any decryption of the traffic outside my home (it stays encrypted until it gets to my hardware), and I am supporting an important open source project!