Q, The #Fediverse seams to kinda be on autopilot at the moment – I miss the days when the community was more focused….
A. I’d say it’s growing and changing. From my window, there’s a LOT happening. Many people are excited by the new stuff that’s landing, while others are afraid of how those changes may rock the boat they’re on. My solution is to build a bigger boat, because everyone needs the opportunity to be here. But that’s understandably scary for those who want a very small, exclusive community. Hopefully we can make tools that give affordances for both.
My metaphorical thinking on this is, yes, there is a lot of technical activity. New software, new protocols, bridges, funding, organisations and experiments. From that perspective, the #Fediverse is very active. But socially, it often feels like it’s on autopilot.
In the early years there was a shared sense that we were rebuilding the #openweb together. There were arguments, of course, but there was also a common direction. People were asking social questions about ownership, governance, federation and community. Those conversations created momentum beyond individual projects.
Today much of that shared vision has fragmented. Each project has its own roadmap, each server its own concerns, each funding stream its own priorities. That’s healthy to a point, but without a wider narrative the movement risks becoming a collection of software projects rather than a #openweb social movement.
I agree that we need a bigger boat. The internet needs one. But the question is what kind of boat are we building? If becoming bigger simply means attracting more users while reproducing the culture of the #dotcons, we’ve missed the point. Federation alone doesn’t create commons. We can decentralise servers while recentralising culture, governance and influence.
This is where the #OMN perspective differs from the current #mainstreaming. The challenge isn’t only scaling infrastructure – it’s scaling communities. A bigger boat still needs lots of crew who know how to sail it, repair it and decide together where it’s going. Without that, people become passengers rather than participants.
The #Fediverse already has the technical foundations. What it lacks is enough shared social infrastructure: ways to build trust, preserve collective memory, govern openly and connect local communities into something larger without creating another centre of power. That’s why I keep talking about #DIY, #MakingHistory and the #4opens. They aren’t distractions from the technology, they’re the missing social layer. The code is necessary, but code alone won’t build the commons.
Perhaps the feeling of “autopilot” comes from this imbalance. We’re very good at building new features, but much less good at building shared purpose. The result is #techchurn: lots of movement, but not always much direction.
So yes, let’s build a bigger boat, but let’s also build more harbours, more local communities, shared stories and more reasons for people to become co-builders instead of just users. Because the strength of the #openweb has never come from one magnificent ship.
It has always come from a sea full of small boats, travelling together without needing a single captain.

Update It’s interesting that there’s still so much denial about this history. To be clear, I’m not blaming the people who arrived in the #Fediverse after the shift in the first five years of its development. They only know the culture they arrived in. It’s understandable that many assume this is how the project has always been.
What needs to be better understood is that, for roughly the first five years, the #Fediverse and #ActivityPub were driven primarily as a social and political project. The technology mattered, but it was there to serve the wider goal of rebuilding #FOSS commons-based infrastructure and supporting subculture communities. The people doing the work were mostly motivated by those social and political aims, with technical and #mainstreaming perspectives forming a minority.
After that period, the balance shifted. As the network grew, technical concerns, institutional interests and #mainstreaming priorities became dominant, while the social and political vision became a minority. The conversation increasingly focused on software, scaling and features, rather than governance, commons, trust and community.
Neither perspective is wrong on its own. We need both. The problem is that the shift happened without much reflection, and today many people are simply unaware that it happened at all. There are now very few people left who have lived through both periods and can bridge the divide. Their experience matters because they remember why many of these projects were started in the first place.
The real frustration is with those few people who do know this history, who experienced the transition firsthand, yet now deny or minimise that it happened. That denial makes it much harder to have an honest conversation about where we are and where we need to go.
For everyone who arrived later, the response shouldn’t be blame – it should be curiosity. Every movement has a history, and understanding that history helps explain why today’s arguments keep repeating themselves. This isn’t unique to the #Fediverse. It’s a common pattern in grassroots projects. As movements grow, they become more institutional, more technical and more professionalised. The original political purpose fades into the background, and new participants naturally assume the current culture is the whole story.
If we want to avoid repeating that cycle, the first step is simple – Acknowledge that the shift happened. Only then can we decide, together, what kind of #Fediverse we want to build next.








