Fediverse is Distribution, Not Home

There's a version of the fediverse pitch that goes like this: leave the corporate platforms, come here, this is where the good people are. The algorithm is gone. Nobody's selling your attention. It's chronological, it's human-scale, it's real.

Most of that is true, and none of it is the point.

The fediverse is infrastructure. ActivityPub is a protocol. These things solve a real problem, which is how content moves between independently operated servers without requiring a central clearinghouse. That's genuinely useful, and it's worth understanding on those terms. What it isn't is a home. Treating it like one is how you end up in the same attention loop you left, just with better politics and a more interesting timeline.

The discovery problem is real and federation actually solves it. If you publish on your own site, the default situation is that nobody knows it exists unless you tell them or they already know to look. You have to solve distribution separately. ActivityPub gives you a working answer to that problem. Post from your own site, federate the content out, and people following you on Mastodon or any other compatible server see it without you having to paste a link somewhere and hope. That's not nothing. That's a meaningful piece of infrastructure that took years to get right and is worth using.

But here's what federation doesn't change: the timeline is still a timeline.

A chronological feed of everything people you follow have posted is less manipulative than an algorithmic one, but it's still a feed. It still rewards posting frequently. It still creates the pull to check, to respond, to stay current. The compulsion isn't generated by the algorithm alone. It's generated by the social nature of the thing, and that social nature is present on the fediverse in full. If anything, the absence of an algorithm makes it more honest about what it is, which is a stream of human activity that will keep flowing whether or not you're watching, and that makes it very hard to close the tab.

The distinction worth drawing is between your publishing surface and your distribution layer. Your publishing surface is where your work lives. It's your site, your domain, your archive. It's the place where someone can find everything you've written without depending on any particular platform's continued existence. Your distribution layer is how people find out that you've published something. These are different problems and they should be handled by different things.

The mistake is collapsing them. If the fediverse is where you write, then the fediverse is your publishing surface, and you have all the same dependency problems you had on Twitter or anywhere else. The server could close. The instance admin could burn out. The community could drift. Your history lives somewhere you don't control, and your audience is tied to a platform rather than to you directly.

Use ActivityPub as transport. Write on your own site, syndicate out, let the federation carry the content to wherever people are reading. This is not a complicated technical setup. Several publishing tools support it directly, and for those that don't, the implementation is well-documented. What it requires is the conceptual shift of treating the social layer as downstream of the publishing layer rather than treating them as the same thing.

The timeline is useful for conversation. It's not useful as a home base. Conversations are ephemeral by nature, which is fine. You don't need a permanent record of every reply thread. What you do need a permanent record of is your actual work, the pieces you put effort into, the things you'd want someone to find if they went looking. That record should live somewhere you own.

The people who've figured this out have a noticeably different relationship to the fediverse than the people who haven't. They're less anxious about it. They post when they have something to say and they don't check as compulsively because the stakes of any individual interaction are lower. Their work exists independently of whether anyone boosted it. If the instance goes down, they lost a distribution channel, not their archive. That's a much more stable position to be in.

The fediverse being good doesn't mean you have to live there. You can use a road without building your house on it.

ActivityPub solves the problem it was designed to solve. Let it do that job. Own everything else.