Hamish Campbell is a long-time #openweb activist and technologist working on grassroots media and digital commons. He was involved in the early development of #Indymedia and continues this work through projects like the Open Media Network (#OMN), which works on how federated tools and community publishing supports public-interest media infrastructure. His focus is balancing building native platforms and on growing the social culture that makes the #openweb work: transparency, decentralisation, and horizontal collaboration. Through writing, workshops, and practical projects, he argues that the future of the Fediverse depends as much on culture, governance, and shared infrastructure as it does on code.
Workshop 1
The #Mainstreaming Problem in the Fediverse
Purpose is to open conversation that many people feel but rarely articulate: the tension between grassroots culture and institutional capture. Start with your simple distinction:
- Good #mainstreaming → openweb values spreading outward
- Bad #mainstreaming → corporate/NGO structures reshaping the Fediverse
Then ask: “Which direction are we currently moving?”
Discussion topics – funding and governance, foundations and institutional capture, developer vs user power, infrastructure vs platforms. How to avoid repeating Web 2.0
Activity is to ask participants to map three layers: Grassroots – NGO / institutional – Corporate. To discuss where power currently sits and what healthy balance might look like.
Outcome is people leave with language to understand the tensions they are experiencing in the Fediverse.
Workshop 2
Maybe a second one on why #makeinghistory is needed? Translating #OMN from “activist infrastructure” into “missing public digital infrastructure.” That language is what this event is trying to figure out. The Open Media Network (#OMN) proposes a model where grassroots publishing, community moderation, and institutional participation are balanced. Participants can discuss how institutions support shared infrastructure rather than just deploying isolated platforms.
Many institutions are experimenting with the Fediverse as an alternative to #dotcons corporate social media. However, simply running institutional servers risks reproducing the same platform dynamics in a federated form. We need workshops that explore the broader ecosystem of public-interest media infrastructure.
“What happens after institutions join the Fediverse?” The #KISS answer is they need to support the commons infrastructure that makes it socially viable. Running Mastodon is not enough, institutions need to support the wider open media ecosystem.
Talking about #openweb culture in a constructive way is tricky because most #FOSS and Fediverse conversations default to technical framing: code quality, scalability, moderation tooling, and #UX. These things matter, but they are not the foundation that determines whether a network lives or dies.
Maybe a useful way to open the conversation is to shift the starting point. Instead of saying “culture is important too”, say something stronger but practical: The success or failure of open systems is primarily a cultural question, not a technical one. The code only expresses the culture behind it.
Start with a simple historical observation. Many technically strong systems failed because the social layer was weak, while some technically rough systems succeeded because the community culture worked.
Examples from the open web – early open source projects that thrived because communities shared norms of collaboration. Grassroots networks like Indymedia worked socially even when the software was messy. Corporate platforms that succeeded not because they were technically better, but because they built powerful social gravity.
The pattern is clear, that technology enables networks, but culture sustains them. This is the missing step in most Fediverse conversations. Right now to meany discussions focus on: scaling servers, moderation tools, interface design and onboarding. These are all necessary but insufficient.
What way to often goes missing is the deeper questions – What culture are we actually trying to grow? Without answering that, the system tends to drift toward the dominant internet culture, which today is shaped by the #dotcon platform model of engagement optimisation, algorithmic attention markets, influencer dynamics and centralised power. When that culture seeps into the Fediverse, the result is a federated copy of the same problems.
So why is culture harder than code? Code can be written by a few developers, culture requires shared understanding across thousands of people. To grow this we need native governance norms, trust networks, moderation values and expectations about ownership and participation to hold to native paths for how conflict is handled. These things cannot simply be implemented in software, they must be grown socially, fail to address this is why many technically strong projects fail, they assume the social layer will somehow emerge automatically. It rarely does.
To make this constructive, it helps to clearly describe what we mean by #openweb culture. Some core values historically included public-first communication rather than platform ownership, decentralised responsibility instead of central moderation authority, commons thinking rather than product thinking to nurture horizontal participation rather than audience/influencer hierarchies, this need clear #4opens processes rather than opaque decision-making.
These values were never perfect, but they created a different social environment from today’s corporate social media. If we do not actively cultivate these values, the surrounding internet culture will slowly overwrite them. If the Fediverse continues to grow without addressing culture as it currently is, the most likely outcome is large institutional instances dominate, smaller community spaces struggle leading to more moderation being centralised. This all shifts user expectations toward platform-style experiences.
At that point, the system may still be technically federated, but the culture will have drifted back toward Web 2.0. The code will be open, but the social dynamics will not be.
So the “extra step” is simply, we must talk about culture as deliberately as we talk about software architecture. That means asking questions like: What social norms should Fediverse communities encourage? What governance models support open participation? How do we keep the ecosystem diverse rather than dominated by large actors? What responsibilities come with running infrastructure in a commons network?
These conversations are sometimes uncomfortable, because they move beyond engineering into politics, sociology, and ethics. But avoiding them does not make them disappear, it simply means the culture will be shaped by default forces instead of conscious choices.
A simple way to frame this – A phrase that often works well in discussion is – “Code builds the network, but culture decides what the network becomes.” If we want the #openweb to remain something different from the #closedweb platform internet, we need to invest as much thought into the culture as we do into the code and #UX. Otherwise, the technology may succeed technically, but the social project behind it will quietly fail.






