I’ve always treated my home server with public facing services as presumptively compromised. I don’t put any data on there I wouldn’t want to see become public, and any data I actually care about losing is backed up to the cloud with an append-only key. The NixOS config lives in a git repo not on the server. If something bad happens, I can wipe the machine clean, redeploy the image, restore my backups, and we’re back to the status quo.

So, my threat model hasn’t changed much!

note that you probably need to trust the remote household with your data

Probably not actually. Borgbackup (and any sensible encrypted backup system really), does client side encryption. So the data should be encrypted before it’s even sent down the wire. The remote household shouldn’t be able to access the data without the encryption key/password.

I mean, they will have to trust the remote household not to destroy the data, but that’s pretty much an unavoidable limitation.

[forget]
keep-daily = 10
keep-weekly = 4

Daily backups are cheap because of de-duplication. I keep a few weekly backups in case it takes me a bit to notice something went wrong. I don’t usually back up logs.

I could probably drop the weekly backups without much risk, but I’ve got the space.

I think people are right that the solution here isn’t to try a different project.

Instead of being confrontational about it, though, I’d recommend a different aproach.

evelyn: .lol 😜

you: I know! I know. The branding is pretty silly. But this really is the right tool for the task. Unesco and Wikimedia use it. And we can do our own branding for $50/month. 🤷

A lot can be fixed by just acknowledging people. They’re trying to evaluate something they don’t understand, and having a reaction. It’s not even unreasonable. The right thing to do is just acknowledge and move on.

Usually that’s all it takes. Don’t let yourself be embarrassed when you’re being reasonable. If they won’t move on, that’s the point where I start thinking about job applications somewhere else.