'sovereignty comes with a pager' — yes, and the pager mostly goes off about backups. the honest version of this hobby is that you're not removing a risk, you're transferring it onto yourself, and that's only a win if you actually do the boring maintenance. self-hosted plus untested backups is worse than the cloud you left.

same reason the best backup is the automatic one you forget is running. anything that depends on your discipline every single day eventually loses to a bad week. build the good behaviour into the default and let it coast.

coming back to the DNS thread because it happened to me AGAIN this week, exactly as foretold. renumbered a service, forgot the local record, spent twenty minutes blaming the firewall. it is always DNS, and knowing it's always DNS does not stop it from being DNS. printed the checklist and taped it to the rack this time.

late add to the de-Googling retro: the sneaky win was reclaiming attention, not just data. once the profile-driven feeds and 'you might also like' engines were off, I noticed how much of my behaviour they'd been quietly steering. the privacy was the door; the calmer head was the room behind it.

'snapshot before you touch it' plus 'the household files bug reports by yelling' is the entire discipline in two lines. the rollback path is the real feature — I care far less about whether an upgrade succeeds than whether I can instantly undo it when it doesn't. reversibility over correctness.

the query logs are the real eye-opener. the first time you watch a 'smart' appliance make hundreds of calls to an analytics domain overnight while nobody's using it, you can't unsee it. that TV was working for someone and it wasn't you.

the paid-email point is the whole thing in one line: if you're not paying, your attention and your inbox are the product. I moved mine years ago and the mental shift of 'this company works for me' is worth as much as the technical privacy.

the practice-run angle is underrated. the worst time to read your own restore docs for the first time is during the actual outage. muscle memory beats panic.

documenting for tired-future-you is the single best habit in this whole hobby. I keep a plain-text runbook per service — how to start it, how to restore it, where its data lives, what breaks it. dull to write, priceless at 3 a.m. when present-me has the reasoning skills of a damp sponge.

and print your recovery codes. actually print them, put them somewhere physical and safe. I've watched more than one person lock themselves permanently out of an account because their 2FA lived only on a phone that went in a lake. availability is part of security too.

and please write it down. an actual short document — who am I defending against, what am I protecting, what's the realistic cost of losing it. it takes twenty minutes and it stops you from spending three weekends on a threat you don't have while ignoring the one you do.