I would say that finding that balance is up to the individual admin and application, really, which is where the defense in depth comes in. Yeah, it’s rare, and if those exploits are being used it means you’ve got the attention of someone you probably can’t really stop, but it’s something to take into consideration. Bad configs can cause data leakage across container boundaries, too, so without knowing the admin’s skill level, I tend to recommend against sharing that hardware with something that might have something valuable on it. AI has made it easier for script kiddies to find zero-days and exploit APT-level vulnerabilities, too.

PabloSexcrowbar
It masks the registration info, but it can’t mask the IP by definition, and that can still be traced back to you.
Replying to a post on tkohhh.social
38.5092, -121.4956
Accuracy 5 km
Replying to a post on tkohhh.social
It’s not about the container escape so much as the potential for someone to do a DNS lookup on your domain name and use that to locate you physically. Yes, it’s coarse location data, but someone on 4chan was able to locate Shia LaBoeuf from a single picture of a flagpole. It doesn’t take much.
I would NOT host a Lemmy instance at home unless you’re going to obfuscate your IP address. If you make it public, you’re inviting any whackjob that sees your username to find your physical location. Additionally, I wouldn’t host it on a PC that you actually intend to use for day to day stuff, just in case the instance gets hacked and someone manages to escape the container it’s in. If you wanted to do this, I would put it on its own box with Cloudflare in front of it, otherwise you’re inviting trouble where there doesn’t need to be any.