Last weekend, Scott Jenson, a product strategy advisor to the Mastodon core team, posted a thread asking whether Mastodon was becoming an echo chamber. He cited declining engagement numbers compared to Threads and Bluesky, pointed to a journalist whose Mastodon following was shrinking while their other audiences grew, and suggested the community's hostility toward AI was symptomatic of a broader tendency to drive people away. The comparison he drew to the loss of Black Twitter in 2022 was badly misjudged, and the furious response was largely justified. Hannah Aubry, Mastodon's community director, publicly distanced the organisation from his views. The thread blew up, accumulating hundreds of comments in a single weekend, most of them hostile, and the pattern of the community's response is worth looking at closely.

Dozens of replies made the same argument in different words: no central authority decides who joins, and the protocol is open to anyone, and if AI enthusiasts want a community they are free to build one. "No one is guaranteed an audience, just the ability to speak." If your posts don't find an audience on a platform with no algorithm, that is the system working as designed. "The fairness that matters is in access and safety for people to engage. It is not then about whether the current Mastodon user base is morally obligated or socially owes anyone any attention at all."

These are arguments about what Mastodon is as a system: the protocol is open, and no technical barrier prevents an AI-friendly instance from existing.

But the same thread, often from the same people, also produced this: "THE AI BROS ARE THE ENEMY. There can literally be no room for pop culture tolerance of AI anything." "AI is a neoliberal and right pursuit, period." "AI is shit and so too are people that worship these plagiarism machines. I'm glad this platform doesn't feel welcoming to people that are pro or even neutral to this garbage tech." "The ai community needs to have a reckoning with the fact that the politics and the technology are deeply entwined to the point of being inseparable."

These are arguments about what Mastodon is as a community. This is a space with values. It was built by and for marginalised people, queer people, artists, people who came here to escape the platforms that corporate tech built. AI represents everything this community defines itself against.

The community produces both responses simultaneously, and does not experience them as contradictory. The system argument appears when the topic is access: the protocol is open, nobody is gatekept. The community argument appears when the topic is values: we don't want that here, this space has standards. Each response feels correct, and the tension between them only becomes visible when you look at both statements about Mastodon side by side and ask what kind of thing Mastodon is.

Eugen Rochko, Mastodon's founder and lead developer, replied early: "We don't need equal amounts of people who love puppies and want to kill puppies. Not everything needs to be equally represented." Mastodon is software that runs an open-access protocol, designed so that anyone can participate and no central authority decides who joins. Its creator is now defining the space that software produces in explicitly exclusionary terms, equating a technology position with something self-evidently abhorrent.

Jaz-Michael King, who runs IFTAS (Independent Federated Trust and Safety), has written that "the fediverse is not a place, it is the means to build a place." His vision is a million small places, each with its own governance and its own front door, connected where it makes sense and disconnected where it doesn't.

At the instance level, admins can act on this. They can set rules and moderate the local timeline, or defederate from instances whose values conflict with theirs. Instance rules can say "no AI content" and mean it. Some instances do. The place-making toolkit at the instance level is rudimentary but functional: if you want to run an anti-AI community or a bilingual Welsh-language community, you can build that at the instance level and the software will support you.

The difficulty is that almost nobody experiences Mastodon at the instance level. People experience it through their home timeline, which composites content from across the entire federation. They experience it through replies arriving from users on other instances, through boosts that carry posts across instance boundaries, through trending topics and hashtags that aggregate across the network. The lived experience of Mastodon is the federated social graph: thousands of overlapping follow relationships and federation decisions producing a shared space no instance controls.

At that layer, there are no place-making tools. The federated social graph is a space nobody designed and nobody governs, without rules or onboarding or any mechanism for communicating what the space is for. When someone on instance A sees a pro-AI post from instance B because someone they follow boosted it, the interaction that follows happens in a space that belongs to neither instance and is governed by nobody. Replies to the Jenson thread arrived from dozens of instances. People who had never interacted before, who were accountable to different admins under different rules, converged on the same post and produced a collective response that no single instance governed. Each individual reply may have been within its own instance's norms. The aggregate experience was a property of the federation layer, and no governance mechanism exists there. The Jenson thread is itself an example. The anti-AI consensus that expressed itself across those hundreds of replies is not written into any instance's rules. It is not the product of any admin's moderation decisions. It is the culture of the federation layer, formed through years of shared follows, shared boosts, shared blocks and shared arguments about what is acceptable, and it governs even though no institution maintains it.

This is why "spin up your own instance" is such a persistent but unsatisfying response. It is true at the instance level, where the place-making tools live. The person receiving replies from across the federation is experiencing the federation, not their instance, and moving to a different instance does not change the federation layer. An AI-friendly instance's users will still encounter the community's hostility the moment their posts cross instance boundaries through boosts, replies, and hashtags.

King has been building software that takes the instance-level vision seriously. The Twt app for toot.wales is hard-locked to a single instance, with curated local feeds, bilingual onboarding, and a deliberate design that makes the community the unit of experience rather than the protocol. It works precisely because it keeps the experience at the instance level, giving the community tools to define and communicate its identity through software design rather than through social enforcement. In the default Mastodon experience, the federation layer is front and centre and the instance is barely visible.

The gap between instance-level governance and federation-level experience explains more than the AI debate. A former journalist in the Jenson thread explained that they could not justify maintaining a Mastodon account to their editor, because the platform's design made it impossible to demonstrate click-through traffic. Several respondents treated this as validation: Mastodon is a social network, not social media. Another user pointed out that what looks like low engagement may be high readership without visible metrics. These responses accurately describe what the community values, and in doing so they describe why professional journalism is structurally incompatible with the platform, even though the community wants journalists here and wants the public discourse that journalism sustains.

The AI question and the journalism question are symptoms of the same condition. The community has a clear sense of what kind of place it wants to be, formed and maintained at the federation level through shared follows, boosts, and social signals. But the tools for expressing and maintaining community identity exist only at the instance level. At the federation level, where the sense of place actually lives, the only mechanism for maintaining community boundaries is individual social behaviour: who you boost, who you reply to, and how you respond to people whom the community actively rejects. When those signals need to do the work of governance, they default to hostility, because nothing else operates at that layer.

The community wants the fediverse to be a place. King is right that architecturally it is not one, that it is the means to build a place. But the lived experience of most Mastodon users is not King's million small places with curated front doors. It is a single shared social space, experienced through the home timeline, in which community norms are enforced through individual responses but cannot be formally expressed, in which boundaries are real but can only be maintained person by person, reply by reply. The result is a community that defaults to social aggression for boundary maintenance, because the software provides no other mechanism at the layer where the boundaries actually matter.

This is not a cultural failing that can be fixed by asking people to be nicer, which was roughly Scott Jenson's prescription. Nor is it resolved by pointing to the protocol's openness, which was roughly the community's response. Neither prescription reaches the actual problem, because Mastodon's governance tools sit at the instance level and the community's experience happens at the federation level. Mastodon was built as open infrastructure at the federation level and community at the instance level. The Jenson thread demonstrates that the community has long since reversed this: they experience the federation as their community, and the instance as an administrative detail. The software has not caught up, and until it does, the community will keep enforcing its boundaries the only way the federation layer allows: person by person, reply by reply.