Is running your own server actually safe?
Is self-hosting less secure than using a big provider? A straight answer on where you are genuinely safer, where you are worse off, and why.
4 min read
blog / self-hosting
Taking your data back — where it really lives, what happens when a service closes, and whether running things yourself is genuinely safer.
$ ls blog/
// 14 posts · counted from the collection at build
Is self-hosting less secure than using a big provider? A straight answer on where you are genuinely safer, where you are worse off, and why.
4 min read
Services close, hardware is switched off remotely and terms change without warning. What the record shows, and why software you run has no end date.
5 min read
Your photos, files and messages are somewhere. Three questions decide how much say you have — and most people get the same answer to all three.
5 min read
keep in the loop
There’s no public signup, and this isn’t one. Leave your name and email and you’ll get the occasional note when something on the network changes — an application going live, a security write-up, or word that access has opened. Nothing else, ever.
An occasional email when something on the network actually changes — an application going live, a security write-up, a change worth knowing about. No schedule, no newsletter, no noise.
Your name and email, nothing more. This is a mailing list, not an account: it grants no access to anything, and the applications stay invite-only and granted per person.
Access is provisioned per person and stays invitational today. If that ever changes, the people on this list hear first — nobody is added to anything automatically.
sent rarely · never shared · unsubscribe any time