The problem isn’t simply that open source has feudal governance, it’s that by only decentralizing technology we reproduce the same old hierarchy under different names. The#openweb reboot based on the #Fediverse gives us a chance to build something better, but first we need to have the argument that decentralization alone isn’t democracy. Feudalism in code is still feudalism.
Four years ago I was arguing that feudalism was a poor model of governance for #opensource and #freesoftware, that argument hasn’t aged out. Too often, decision-making still rests with project founders, core developers, instance admins, founders and the people who control the infrastructure. Everyone else gets a voice only when those above them choose to listen.
This is the weakness of much of the current path – we have built copy’s of corporate platforms – but carried over their top-down assumptions: gatekeepers, personality politics, informal hierarchies and governance by whoever happens to hold the hard coded roles..
In 2022, we were arguing that decentralizing the technology wasn’t enough, that we also needed to decentralize power, ownership and decision-making. The uncomfortable question in 2026 is have we actually changed the governance, or have we simply reproduced the old power structures on decentralized infrastructure? My reading, that we’ve made some progress in recognizing the problem, but much less progress in building practical alternatives.
Mastodon has recognized the ownership problem. In January 2025 they announced plans to transfer its intellectual property and key assets into a European non-profit structure, explicitly stating that the project should not be owned or controlled by one individual. By November 2025, the transition was still in progress. The proposed Belgian AISBL had not yet taken over, and the existing organizational arrangements are continuing. By February 2026, Mastodon was talking more explicitly about community ownership, governance pathways and involving the wider social-web community in shaping its future.
This is a meaningful change – but there’s an important distinction – moving ownership from an individual to a non-profit organization is not the same as moving power to the community. A board can still be a small group exercising authority over everyone else. The question is who appoints it, who can challenge it, who controls the budget and who has a meaningful say in technical direction.
We have moved the discussion forward, but the democratic question remains. The research has caught up with the problem – there has also been fluffy research into how #Fediverse instances work. The 2024 Governance on Fediverse Microblogging Servers research by Erin Kissane and Darius Kazemi looked at the practical structures used by server teams, they identified problems that grassroots administrators have been experiencing for years:
- Too much responsibility concentrated in small teams.
- Weak participation by ordinary users.
- Inadequate moderation and governance tools.
- Poor support for cooperative and collective administration.
- A lack of any shared infrastructure between instances.
There is also newer academic work questioning whether Mastodon’s decentralized architecture actually distributes power as evenly as its public image suggests. That brings grassroots projects closer to the original #OGB argument. That decentralization hasn’t removed the hidden hierarchies, while the Fediverse has continued to grow and diversify, decentralization doesn’t automatically mean democratic control. There are several layers of power:
- Instance administrators: They control access, moderation, hosting and often the rules of participation.
- Software maintainers: They decide which features get developed, which contributions are accepted and what technical direction is taken.
- Funding organisations: They influence which projects receive resources and which approaches become sustainable.
- Protocol and standards bodies: They influence the underlying rules that determine how the network works.
Even when the code is open, these relationships remain quite closed. Research published in 2025 on defederation also highlighted the difficult balance between local autonomy, collective safety and accountability across independent servers.
We have the move to #NGO and mainstreaming infrastructure that brings the Fediverse more visibility to institutions, governments, NGOs and commercial platforms. That brings opportunities: funding, infrastructure, public attention and wider participation, but it also brings all the dangers of mainstreaming.
We get professionalised organizations, appointed boards, funding priorities and centralized decision-making, all wrapped in the language of community ownership. This co-option of language and power isn’t necessarily intentional, but the structural risk is real.
So looking back what has happened to the #OGB idea? This is where the comparison becomes more personal – the original path is about moving beyond benevolent dictators to creating practical horizontal governance. The idea was to experiment with:
- Affinity groups rather than permanent hierarchies.
- Sortition to bring fresh participants into decision-making.
- Recall so representatives remain accountable.
- Dilution of concentrated power.
- Voices and representation for smaller groups.
- Governance embedded in the software rather than bolted on afterwards.
The important point was never about simply creating another committee or NGO, it was to build governance into the infrastructure itself.
There has been progress in the wider discussion, but the practical development of #OGB, #OMN and #indymediaback, #makeinghistory has remained difficult. The projects have spent much of the past year stuck at the development stage, despite continuing funding applications and some technical work. We have a clearer understanding of the problem, but we haven’t yet built the working alternatives at anywhere near the scale we need. Four years ago, the framing was about moving from feudal open-source structures towards democratic grassroots stakeholder governance.
The realty is nothing has changed, we still need the technology to make these things possible. As if the software only allows administrators to make decisions, then writing a democratic constitution won’t fix the underlying problem. Governance needs to be reflected in the code, data structures, moderation tools and funding arrangements.
So 4 years on we are still at the first step – from feudalism to a working commons. I think the original work was pointing in the right direction, and the last few years have helped clarify the challenge. We don’t just need to replace benevolent dictators with elected committees. What we need is to move away from the assumption that power has to be concentrated somewhere in the first place. This is where the different OMN projects fit together:
- #4opens: The foundation of open data, open process, open standards and open source.
- #OGB: Practical experiments in horizontal governance, accountability and distributed decision-making.
- #indymediaback: Grassroots publishing and community media.
- #OMN: The shared data infrastructure connecting people, communities and trusted information flows.
The path of these projects is to build a network of communities that can cooperate without surrendering their autonomy. To make this work we do need to stop treating decentralization as a technical property and start treating it as a social practice. Today, the opportunity is still there, but the problem is clearer. The gap between talking about community governance and actually building it remains the central challenge.
We need to get beyond this – the #openweb needs practical grassroots governance, not another layer of professionalised management. It needs communities with real autonomy, shared infrastructure and the ability to challenge power when it becomes concentrated. That’s the unfinished work of the #OGB and the wider #OMN project.. The #Fediverse is a be a place to try this, but it won’t happen by magic.
