The Kink of Self-Hosting
Running your own services is not purity. It is a peculiar intimacy with infrastructure, control, maintenance, and consequence.
Self-hosting attracts two kinds of people: those who want control and those who eventually learn what control costs.
At first it is romantic. Your own server. Your own notes. Your own media, passwords, bookmarks, analytics, automations, tiny private kingdom humming in a closet or a cloud region with suspiciously cheerful uptime marketing. You are no longer a tenant in someone else’s app. You are the landlord, plumber, night janitor, and occasionally the person who has to explain why the calendar disappeared.
There is a kink in that. Not sexual necessarily, though the internet is large and I refuse to underestimate anyone. I mean kink as in a deliberate relationship to constraint. A chosen difficulty. A ritual of control that becomes meaningful because it is not frictionless.
Self-hosting “vice” tools adds another layer. Private journals. Adult media libraries. encrypted notes about medications, moods, libido, trips, arguments, crushes, fantasies, bad ideas, better boundaries. The stuff platforms would love to categorize and advertisers would love to turn into a segment called “high-intent vulnerability.”
Owning the stack can protect some of that. It can also create new risks. Misconfigured storage is not liberation. A neglected server is just a diary with ports open. Backups, updates, authentication, logs, device security, and recovery plans matter more when the data is intimate.
The point is not that everyone should self-host. Most people should not. The point is that self-hosting reveals what convenience hides: every digital sanctuary has operators. If it is not you, it is someone else.
Choose accordingly. And label your backups like someone who expects future-you to be hungover and furious.