Nobody said it would be easy

If we want meaningful change rather than internal noise, it helps to talk less about individual personalities and more about roles, structures, and class. Individuals come and go, but the patterns they operate within repeat. Shifting focus this way isn’t about avoiding accountability, it’s about understanding the dynamics that shape behaviour across projects and communities.

When we centre individuals, discussions drift into blame or hero narratives, which generates more temporary heat than permanent light. When we look more at structural incentives, cultural habits, and class dynamics, we start to see why the same problems reappear across different spaces – from grassroots projects to NGOs to #FOSS communities.

This is a signal-to-noise issue. A #KISS approach helps: keep analysis simple, structural, and grounded in shared experience. By reducing personalisation and increasing systemic understanding, we create more room for collaboration, learning, and mediation, which is important when building sustainable paths like the #openweb and #OMN.

What we then need to compost. It’s a normal mainstreaming augment that systems built primarily on trust will inevitably rot, decay, and collapse. That concern is understandable. Many people’s lived experience tells them that without strong control structures, things fall apart. And honestly – sometimes they do.

But the story is more complicated than that. First, there are long-term examples of trust-based or grassroots systems working, though they rarely look neat or institutional enough to be recognised as “successful” by mainstream standards. The difficulty is that these systems are best understood through participation rather than observation. They are lived processes, not static models. I document some of this history on my site, but reading alone rarely communicates the full reality, experience does.

Second, yes, grassroots projects can be damaged by well-meaning people. That isn’t paranoia; it’s everyday reality. Social dynamics, unconscious habits from institutional culture, and imported control patterns all create friction. The #OMN approach accepts this and builds mediation strategies directly into projects. These strategies are imperfect, and we often get things wrong, but acknowledging the problem openly is part of making the work sustainable.

And to the harder question: if good intentions can cause disruption, what happens when bad actors show up? The answer is that no system is immune. Control-heavy systems fail too – sometimes more dramatically because their rigidity hides problems until they become catastrophic. The goal isn’t to create a perfect system (the classic #geekproblem), but to build a more humane messy system that can adapt, respond, and recover.

All functioning social systems are messy. Trying to eliminate that mess usually creates more fragility, not less. Instead, the path forward is to embrace smaller, resilient units that federate horizontally, many small experiments linked together rather than one central structure trying to manage everything. This is where the #fediverse and projects like #OMN become interesting: we now have technologies that allow small-scale trust networks to interconnect without collapsing into centralized control.

Will people try to take control or undermine these spaces? Of course. That’s part of reality. The work is to build cultures and processes that mediate this continuously, rather than pretending it can be eliminated.

What we maybe need to convince sceptical engineers is not ideology but demonstrated failure modes and working counter-patterns. Trust-based systems are not naive if they are designed with clear threat models, transparent processes, and layered social/technical safeguards. The question is not “can grassroots projects fail?” – all systems fail – but whether they fail visibly, recover ably, and without capture.

Long-lived commons like Wikipedia moderation structures, Debian governance, early Apache development, and parts of the Fediverse show that in tech messy, trust-anchored collaboration can operate for decades when legitimacy is distributed and process is open. #OMN is not proposing blind trust; it proposes observable trust – where actions, history, and reputation are legible through open process (#4opens), allowing engineers to audit the social layer much like they audit code.

The real engineering challenge is not eliminating messiness (a classic #geekproblem trap), but designing systems where messiness becomes resilient rather than brittle. Nobody said it would be easy, but difficulty doesn’t mean impossibility. It means the work is social as much as technical.

None of this new – as Bakunin put it, “The peoples’ revolution will arrange its revolutionary organization from the bottom up and from the periphery to the centre, in keeping with the principle of liberty.” Whether or not we use the language of revolution, the underlying insight is practical rather than ideological: durable systems grow from lived participation outward, not from abstract design imposed from above.

In #openweb and #OMN thinking, this means building structures that enable agency at the edges while allowing coordination to emerge through federation and shared practice. The goal isn’t purity or perfection, but resilient networks where trust, mediation, and collective responsibility evolve through use – messy, iterative, and grounded in real communities rather than centralized control.

#KISS