Tag: KISS

A fresh look at the mess we need to compost

Anything that starts as a real idea – community, freedom, or independence – gets picked up, processed, and turned into something hollow. Not just by “the other side,” but by the entire modern media and tech machine. Good ideas go in, slogans come out, you’ve seen it: “freedom” becomes branding, “community” becomes marketing and resently “sovereignty” becomes a funding pitch.

This is the trap, when ideas get flattened into talking points, they stop doing anything real. They become easy to repeat, to weaponise and impossible to build with. And once that happens, it doesn’t matter who started the idea, it’s no longer yours. So the question isn’t only left vs right. It’s how do you keep ideas grounded so they can’t be hijacked and sold back to us?

One answer is structure, the #4opens approach is simple, a way to stop things being quietly twisted behind closed doors. If you can see how something works, it’s harder to fake. If you can take part, it’s harder to capture.

The other answer is mess (the good kind), the #OMN hashtag approach doesn’t try to clean everything up into a single message. It keeps things local, contextual, a bit rough around the edges. That “mess” is protection, because systems that are too neat, too polished, too uniform… are exactly the ones that get captured, repackaged, and pushed back at you.

In plain terms if an idea can be turned into a neat slogan, it can be taken over. If it stays tied to real people, real places, and real processes, it’s much harder to fake. This is the difference between something you can live with and something that gets sold to you. Call it compost if you like – You break things down, keep what’s real, and grow from that.

One example: Tactical Tech is a Berlin-based nonprofit that’s been around since the early 2000s, working on tech, activism, media, and education. Their core thing is:

  • building digital literacy + critical thinking tools
  • producing toolkits, exhibitions, and guides (like The Glass Room, Data Detox Kit)
  • working with civil society orgs, journalists, activists, educators
  • focusing on how tech shapes power, politics, and society

They’re not grassroots infrastructure builders, they’re capacity builders and narrative shapers, working through partnership networks, funding, and “field building” – classic NGO patterns.

In #OMN view they sit squarely in what we call the #NGO / #mainstreaming layer of the #openweb story. In that they don’t build the soil (infrastructure, protocols, messy grassroots tools). They build the interpretation layer (how people think about tech). They push this into narratives + toolkits that travel across institutions. That’s why they’ve lasted 20+ years – they’re adaptable mediators, not in anyway rooted projects.

So why dose it feels like “they create mess”? The friction comes from this pattern the balance of abstraction over grounding in that they translate messy realities into frameworks, exhibitions and “kits”. This flatten lived complexity into safer portable concepts, in to language production. They are part of the ecosystem that generates terms like digital literacy, resilience and sovereignty (adjacent space). These become floating signifiers – useful for funding and policy, messy in practice.

They collaborate with foundations, governments and large NGOs. So their outputs are shaped to be fundable, presentable and non-threatening enough to circulate. That’s where the “compost” instinct kicks in – because this layer detaches language from practice.

But it’s not just negative, if were honest (and it’s worth being), groups like this do some real things. They’ve help millions engage “critically” with tech issues to make complex problems accessible (privacy, AI, influence systems). They might create bridges between activists, educators, and institutions. So they’re not empty, they’re just not where the roots are.

The real tension, the problem isn’t that they exist, it’s where they sit in the ecology. They are compost producers, but they mistake themselves for gardeners. Or more sharply

  • They circulate meaning rather than anchor it
  • They mediate change rather than enact it
  • They stabilize narratives that should sometimes stay unstable

So yes – they create “mess” …but it’s a different kind of mess than grassroots paths. Grassroots mess = fertile, emergent – #NGO mess = abstracted, packaged, drifting.

Projects like Tactical Tech can be a part of the same ecosystem we need – but they sit one layer up from where change actually happens. Their outputs duse need composting because they generalize lived practice into frameworks, turn struggle into language and then feed that language back into systems which tends to blunt its edges.

The task isn’t only to reject them, it’s to ground what they produce back into lived, messy, trust-based practice – the bit they can’t really do. Once you see this pattern, a lot of the confusion in the #openweb space makes sense.

• Soil layer → messy, native, trust-based (#indymediaback, grassroots, actual users)
• Infrastructure layer → protocols, servers, code (#ActivityPub, Fediverse devs)
• Mediation layer → governance, coordination (#OGB-type thinking)
• Narrative/NGO layer → language, framing, funding-facing outputs
• Power layer → states, corporations, capital (#dotcons)

Most confusion comes from people mixing these layers up, Here are a few examples of these groups and organisation.

Tactical Tech – Layer: Narrative / NGO
Role: Translator of tech → society
What they do (in practice)
• Turn complex tech issues into stories, exhibitions, toolkits
• Shape how civil society talks about tech
• Build “awareness” rather than infrastructure

In #OMN terms they produce processable compost input, but often pre-packaged into neat bags. This problem pattern flattens messy reality into clean narratives to encourages passive understanding over active building. So what is there value? Good at onboarding people, opens doors into the conversation. But risk is people stop at understanding instead of doing.

Mozilla Foundation – Layer: Narrative + Funding + Soft Infrastructure
Role: Bridge between grassroots + institutions
What they do is fund projects to run advocacy campaigns (AI, privacy, etc.) that maintains a symbolic connection to the #openweb. In #OMN terms they gate keep legitimacy to define what is “acceptable open”. This is a problem pattern because of NGO gravity → safe, fundable ideas win, radical edges softened into “trustworthy AI” and “ethical tech”. So what is the value? Real money → keeps projects alive and visibility → amplifies issues. The risk is common sense #mainstreaming capture that shapes agenda toward what institutions tolerate. Makeing only more mess to compost.

Open Society Foundation – Layer: Power / Funding
Role: Macro-level agenda shaping
What they do is fund civil society globally to influence policy, rights frameworks, governance. In #OMN terms its a part of the liberal wing of the #deathcult. Problem being funding creates dependency, agenda alignment when movements adapt to grant logic. Value is it enables work that wouldn’t exist otherwise to support rights-based infrastructure. The risk is it turns movements into professionalised NGOs and risk-averse actors.

Sovereign Tech Agency – Layer: State / Infrastructure funding
Role: Stabiliser of critical open tech
What they do is fund maintenance of open-source infrastructure with a focus on “digital sovereignty” In #OMN terms they are trying to support the infrastructure layer by using state-language framing. Its a problem pattern as language like “sovereignty” pulls toward state/control logic and away from commons/trust logic. What is the value? It pays for the essential work to keeps #FOSS tools alive. But it risks reframes the #openweb as national infrastructure instead of shared commons.

NLnet Foundation – Layer: Infrastructure funding (closer to soil)
Role: Rare “good compost feeder”
What they do is fund small, weird, early-stage open projects with minimal interference. In #OMN terms one of the few funding bodies that, could in theory not over-shape outputs to respect messy innovation. But the are problem pattern of limited scaling and still within funding constraints, Value is they enables actual building and possibly supports non-mainstream ideas. The risk is the normal that they still are pulled into NGO gravity over time.

Electronic Frontier Foundation – Layer: Advocacy / Legal
Role: Defensive shield
What they do – Legal battles, policy advocacy and civil liberties protection. In #OMN terms they protects space for the #openweb to exist. But the are problem patterns, the focus on defence, not creation that only works inside existing legal frameworks. Value they are absolutely necessary to stops things getting worse. The risk is they doesn’t build alternatives = slowing decline, not transformation.


The pattern, is all these orgs sit above the soil. They translate, fund, shape, defend. But they rarely grow rooted communities of sustaining messy trust networks or live with the consequences. So why dose this create “mess” it is because language drifts away from practice. Ideas come and go: “digital sovereignty”, “trustworthy AI” or “resilience”. These sound solid, but float free of lived reality, then incentives bend behaviour. Funding → reporting → metrics → simplification is when mess gets cleaned up too early or packaged instead of composted

The #geekproblem + NGO problem merge, you get geeks wanting to tidy systems and #NGOs wanting to tidy narratives. The result is over-simplified systems + over-simplified stories. The #OMN position is clear and grounded, we don’t reject these orgs, we place them correctly: Useful → yes, Central → no and ground truth → never.

The simple way to say this (#KISS) These organisations sometimes help explain, fund, and defend the world, but they do not remake it. If we mistake them for the source of change, we end up with only better words and worse reality. The next stage is a practical progression from “mapping the mess” → “building something that can survive it”.

To make anything work we need to stop confusing layers (cognitive clarity) – Before anything technical the path needs to never treat NGO / funding / advocacy layer as if it is THE system. This is the correction, in #OMN terms:

  • NGOs ≠ infrastructure
  • funding ≠ governance
  • narratives ≠ reality
  • protocols ≠ politics

The outcome is people stop trying to “fix the web” by only better policy decks, better ethical frameworks, better terminology (like “digital sovereignty”). And start asking “What is actually being built, and by whom?”

How to do this? we need to build the soil layer first (not apps, not orgs) as this is where most projects fail. The soil layer is trust groups, working collectives, repeated interaction spaces and small-scale publishing + coordination. In #OMN framing #indymediaback style groups, #OGB governance spaces and local + affinity networks. If it doesn’t survive social breakdown, it isn’t infrastructure.

Define “failure as feature” systems, is one of the strongest #OMN ideas. Instead of perfect systems that must not break – We grow systems that fail into human repair. What that means in practice is moderation doesn’t escalate → it returns to people, governance doesn’t lock → it re-opens, conflicts don’t freeze → they surface into trust spaces. The principle is breakage must increase human contact, not reduce it, this directly counters the platform logic (#dotcons), #NGO sanitisation logic and geek “perfect system” logic.

Build mediation layers (not control layers). This is where #OGB thinking fits. Mediation layer ≠ governance authority, is translation between groups, conflict visibility, trust routing and decision recording (not decision ownership). We don’t centralise power – we route attention. This is the difference between bureaucracy (control) and federation (flow).

Define “trust as infrastructure” this is the “missing” technical core. Most systems assume identity, verification and thus control. #OMN flips this to assume partial trust, local trust, evolving trust and broken trust. So native systems must record trust signals (lightweight) to allow contradiction, allow decay and allow repair. Trust is not a certificate, it is a living flow.

Explicitly resist “narrative capture”. This is where orgs like Tactical Tech / Mozilla / OSF become relevant. The patterns to avoid – messy reality emerges, #NGO translates it, funding aligns around translation and original practice disappears. #OMN counter-path is if it can be fully explained in a funding report, it is likely already dying. So we maintain ambiguity, partial documentation and lived process > polished narrative.

Build dual-stack reality (critical stage). This is essential, you always run:

Native stack (real community power)

  • trust networks
  • local groups
  • Fediverse-native tooling
  • #4opens processes

Interface stack ( individual survival layer)

  • NGO language when needed
  • funding language when needed
  • policy translation when needed

The path is never confuse the interface with the infrastructure.

So what are composting failures? Instead of discarding failed projects, rewriting history and blaming actors. We need to explicitly turn failure into reusable material. Compost includes:

  • broken governance attempts
  • failed funding models
  • collapsed communities
  • conflict histories

Output:

  • patterns
  • lessons
  • reused structures
  • new trust layers

This is where the “mess is valuable” idea becomes operational.

Anti-capture safeguards – Every healthy #OMN system needs resistance to #NGO capture, funding capture, geek capture and ideological capture. Mechanisms:

  • lose roles
  • refuse most permanent authority
  • keep systems reversible
  • enforce transparency (#4opens)
  • limit scale before complexity dominates

The long game is federated commons, at scale, the goal is not a platforms, it is many overlapping, messy, partially connected commons. Not one Fediverse or one governance model, not one truth layer. But overlapping trust regions, with shared protocols and local autonomy to weak global coupling.

The summary (#KISS version). If you compress all of this:

  1. Stop confusing explanation with infrastructure
  2. Build trust-first “soil systems”
  3. Design failure that returns to people
  4. Keep governance as mediation, not control
  5. Treat trust as a living system
  6. Resist narrative capture
  7. Run dual-stack (native + interface)
  8. Compost failure, don’t hide it
  9. Prevent capture structurally, not morally
  10. Scale as messy federated commons, not platforms

The shift is from “understanding the system” → to “acting in a small part of it without being captured” This means choosing a river, a locality, a topic, or a community and committing to working inside its mess without trying to abstract it into a universal model too early. #OMN path is if it doesn’t exist in a place, it doesn’t exist at all. This is where a lot of NGO / narrative layer work fails – it stays placeless.

Build “thin infrastructure”, the #OMN correction to both NGO thinking and geek thinking is that wrong instinct is to build full systems, design complete governance models, define everything upfront. #OMN instinct is to build the minimum structure that lets humans keep adjusting it together. Thin infrastructure = simple publishing tools, basic coordination spaces, visible decision trails and lightweight identity/trust signals. Nothing heavy, nothing “final”, because heavy systems attract control, thin systems attract use.

Make conflict visible, not resolved. This is where #NGO culture diverges hardest from native systems. NGO pattern is to resolve conflict, smooth disagreement and force consensus narrative. #OMN pattern is surface conflict so it can be worked with socially. Why, because in real networks conflict is information, disagreement is structure and tension is direction. The compost is if conflict disappears, it hasn’t been solved – it has been buried. Buried conflict always returns, festers, later as system failure.

Build “trust scaffolding”, not trust systems. This is subtle but crucial, you cannot design trust, you can only create conditions where trust can form and where it can fail safely. Trust scaffolding includes repeated interaction spaces, low-stakes collaboration, visible contribution histories and reversible decisions with clear exit paths. The path to trust is an emergent behaviour of stable mess, not a product of design. This directly opposes #mainstreaming ideas of identity systems, certification systems and techbro reputation scoring systems.

Explicitly reject “clean governance” as this is where most of well-meaning systems collapse. The trap is people try to build clean voting systems, formal representation and universal rule sets. But in messy reality governance is not clean – it is negotiated, situated, and constantly patched. #OMN path is instead of clean governance, we grow layered responsibility, overlapping legitimacy with temporary authority and visible disagreement. Think of governance as weather, not architecture.

Anti-scale principles (very important). Most systems fail because they assume more scale = more success The #OMN flips this with a path of scale should be resisted until coordination proves it is needed. Because scale introduces abstraction, funding dependency, narrative capture, bureaucratic drift. So instead we grow horizontally first, federate slowly and allow divergence to tolerate inconsistency.

Build “failure memory” as infrastructure, its one of the most underused ideas in the whole space. Most ecosystems forget failures, hide conflict history and rewrite past attempts. #OMN path is about failure is the most valuable dataset. So you build public failure logs, conflict histories and abandoned project archives with “why this didn’t work” notes. Not as shame, but as compost. Because systems that cannot remember failure are forced to repeat it.

Soil layer (real life)

trust groups
lived coordination
actual practice

Infrastructure layer

tools
protocols
servers

Mediation layer

conflict handling
coordination
routing

Narrative layer

NGOs
funding language
public explanation

Power layer

states
capital
platforms

On this working group path no layer is allowed to pretend it is another layer, the core anti-confusion mechanism.

So what is the actual #OMN outcomes, when this all works, you don’t get a platform, a movement or a unified system. You get a living field of partially connected commons that can adapt without central control, yes it looks messy from outside – and that’s correct. Because coherence is not the goal, survivability and humain flourishing is. lets reduce the whole thing to operational clarity: Build small, stay local. Keep systems thin, let conflict stay visible, treat trust as emergent. Avoid clean narratives, resist scale, remember failure. Separate layers to never centralise experimentation into control.

That’s where theory finally has to become dirt-under-the-fingernails practice, where the abstraction has to survive contact with reality. Lets look at some example work flows, different angles of the same living loop.

What a real example #OMN #oxfordboaters river project looks like day-to-day. The river communerty is not an organisation. It’s a persistent coordination affinity around a real place/problem/ecology (a river in this case). Daily reality looks like this:

Morning layer (signal gathering) when people notice things:

  • water quality change
  • planning notices
  • blocked access points
  • local council updates
  • photos from walks
  • stories from anglers / walkers / residents

This is not formal reporting, It’s messy input that lands in:

  • Fediverse posts
  • local group chats
  • simple shared logs

Mid layer (sensemaking) is when a few people (DIY, not fixed) do:

  • cluster reports (“this looks like sewage spike again”)
  • link patterns (“this happened upstream last month”)
  • tag relevance (#pollution #access #planning)

No authority – just attention shaping (or focalising).

Action layer (light coordination) is made up of small, reversible actions:

  • someone emails council
  • someone visits site
  • someone talks to landowner
  • someone checks data source
  • someone posts explainer thread

Crucially no one needs permission to act, only visibility into what others are doing

Weekly rhythm (social compression) is a loose gathering (online or physical):

  • “what changed?”
  • “what patterns are forming?”
  • “what are we missing?”
  • “what broke this week?”

No authority, rather shared memory and process. The river project is not a formal group. It is a shared affinity flow. That’s why it works (when it works) – it stays situated, porous, and continuously re-formed.

Lets look at a second example, how #OGB decision flows actually operate, it is not voting or governance in the institutional sense. It is a routing system for trust, conflict, and attention.

Step 1 – Issue appears, something surfaces

  • conflict
  • proposal
  • blockage
  • uncertainty

It is posted publicly (default open).

Step 2 – Context attaches, people attach:

  • experience (“this happened before”)
  • local knowledge
  • technical input
  • historical memory
  • disagreement

Important – contradiction is allowed and expected

Step 3 – Clustering happens (not authority). Instead of leaders deciding clusters of alignment form naturally, disagreement clusters remain visible and minority views persist. Think weather systems, not committees

Step 4 – Decision emerges as a path, not a vote – a “decision” is a visible “common” path of action with acknowledged alternatives still open. So nothing is deleted, nothing is finalised, nothing is owned

Step 5 – Follow-through is voluntary, but visible. People act based on trust in community, reasoning based on proximity and capacity. And they report back into the same system. The native path is the #OGB doesn’t only decide things – it makes decision pressure visible.

What a Fediverse-native governance loop feels like is where it becomes felt reality rather than structure. It feels like slow public thinking, less meetings, less agendas. More like threads that evolve over days, posts that accumulate context and replies that become infrastructure

Persistent memory in the stream, nothing disappears old decisions are still linkable, conflict history is visible and prior attempts remain accessible. So governance is navigation through lived memory. Weak coordination, strong transparency as no one is forced to agree. But disagreement is visible, reasoning is public and action is observable. This produces accountability without authority to grow temporary gravity centres.

Certain threads or instances become coordination hubs, discussion anchors and action nodes. But they fade naturally – nothing, but memmery is permanent. It feels like thinking in public with other people who sometimes act on what emerges. Not bureaucracy, not formal consensus culture. More like shared situational awareness that occasionally crystallises into action.

OMN / #OGB model is: surface → act → observe → remember → re-surface. It is governance more as continuous ecological process, less a fixed control structure.

Think that is anufe for today, please ask in comments to help finsh this.

The hashtag story is messy, that’s the Point

One of the constant pressures we face in #OMN and wider #openweb spaces is the urge to “tidy things up.” People arrive, see a messy landscape of hashtags – #geekproblem, #deathcult, #dotcons – and their first instinct is to fix it, define it, standardise it, make it neat and legible. That instinct feels sensible, but is also the #geekproblem.

The hashtag ecology we’ve been growing over the last decade is designed to be messy. Not as a failure, but as a feature. These tags are not rigid definitions; they’re handles – entry points into ongoing conversations. They hold space rather than close it down. Different people can use the same tag slightly differently, argue over it, stretch it, even misuse it. That friction is not a bug. It’s the composting process.

This is where the #geekproblem shows up hard. The default technical mindset is to treat language like code: define variables, eliminate ambiguity, enforce consistency. In living social systems, that approach kills more than it fixes. You don’t get clarity – you get dead structure. A taxonomy that excludes instead of invites.

But – and this matters – pure chaos doesn’t work either. If everything is noise, only insiders can hear anything. New people can’t find a way in, and the whole thing collapses into a closed loop. The compost stops producing anything useful. So the question isn’t “mess or order?” It’s how to grow balanced living structures.

Dead structure says: this is the correct meaning, this is the right way to use it, anything else is wrong. Were living structure says: here’s how this is being used, here are examples, come play and meaning emerges through use. That’s the difference between a locked-down platforms and the #openweb. One enforces clarity from above, the other grows understanding from below.

Think of it like ecology. Compost isn’t just random waste – it’s a process. Layers, breakdown, transformation over time. Healthy systems have patterns and flows, but they’re never fixed. Forests change. Rivers shift. Nothing is static, but nothing is completely formless either.

The same applies here we don’t need to “clean up” the hashtag mess. We need to use it better by repeating patterns, so people can follow threads, tell stories that embody the tags, let contradictions surface and be worked through and resist the urge to prematurely close meaning. This is basic #KISS, but it’s a hard lesson. Keep it simple doesn’t mean make it simplistic. it means don’t over-engineer what needs to stay alive.

So yes, the mess has value. It creates space for people to build differently, to step outside the rigid frames of the #dotcons and their algorithmic control. It’s how we hold open a commons instead of collapsing back into platforms.

But remember, if everything is compost, nothing grows. If everything is fixed, nothing lives. #OMN sits in that tension, not cleaning up the mess, not drowning in it – but composting it into something people can actually use to make change.

“Digital sovereignty” is more mess we need to compost

“Digital sovereignty” is more mess we need to compost

The servent of the #nastyfew wispering in the ear of the #deathcult ists liberals

From a #OMN perspective, the mess isn’t just the wording – it’s the ideology embedded in the wording, and how that shapes behaviour over time. “Digital sovereignty” sounds harmless, progressive in a liberal policy context. But if you run this through a #KISS ideological lens, its more mess rooted in control, borders, and authority – concepts historically tied to state power. That’s why it’s so easy for the #mainstreaming crew to reuse the language without friction. When they launch something like a “Sovereign Tech fund,” they’re not inventing a new narrative, they’re tapping into one that was already compatible with their narrow worldview.

That’s the problem we need to keep composting – #mainstreaming language carries “common sense” ideological defaults. So what how can we shovel this mess – Liberals adopt a term to make ideas legible to institutions and funding. But obviously the term carries right-leaning assumptions (control, territory, hierarchy) – assumptions that quietly reshape the thinking and direction of projects. Then right-wing actors step in and feel completely at home using the same language.

At that point, it’s already too much mess, you’re not just “using” the language, you’ve internalised the worldview – “Sovereignty” is about defensive, fear-based framing (“protecting against others”) that clashes directly with #openweb values of networks over borders, trust over control and interoperability over enclosure. Our native world view is commons over ownership, so even if the intent is good, the term pulls thinking in the wrong direction. Its #KISS we need to shift focus from states → to people and communities, from control → to capability, from fear → to empowerment.

But here, #OMN pushes much harder – if you need mainstream policy language to explain what you’re doing, you’re already halfway into the #closedweb logic. The #openweb path doesn’t start from sovereignty, autonomy, or even agency. It starts from something simpler – shared standards, visible processes and trust networks (#4opens). That’s why the #OMN path matters, the more abstract the language gets, the easier it is to smuggle in ideology without noticing.

So what do we do with this mess? Yes, “digital sovereignty” is a dead-end term for open, trust-based politics. Yes, alternatives like “autonomy” are an improvement, but the real work is stepping outside that whole framing, instead of arguing over better words, focus on building systems that demonstrate openness, using language grounded in practice, not policy fashion.

Bluntly, this is mess we need to compost, it’s the normal mess of “blinded” liberals laying the groundwork – unintentionally – by adopting language that was never native to the #openweb. That’s the messy pattern – #OMN keeps pointing at, if you build with messy concepts, you will get messy outcomes. So yes – compost it. And next time, start from cleaner soil please.

The recurring theme is digital & social decay – A “trust collapse” resulting from bad faith and disempowerment online. The Goal is #KISS moving beyond individualistic #stupidindividualism, ” common sense to create a balanced collective, community-controlled alternatives.

The #OMN hashtag story is a shovel to “compost mess” to turn toxic digital decay into valuable, new growth rather than pretending the stinking mess doesn’t exist, the second step is acknowledging that disagreements are not to be avoided but used constructively to build stronger, more empathetic, and more transparent communities.

Do you notice a recurring theme and issue here? Read and use the hashtag story to help compost this.

The hashtag story is messy, that’s the Point

People, Process, and the Myth of Difficulty

What we are doing at #Oxfordboaters is simple, that’s the uncomfortable truth for people who see this as to complex. The core idea – people coming together around shared concerns, communicating openly, and acting collectively – is about as old as human society. There’s nothing technically complex about it, nothing conceptually obscure. Yet in practice, it feels almost impossible.

So where does this friction come from? It’s not the goal, it’s not even the surface the process, most of the time, it’s the people – and, more importantly, the tools and cultures we bring with us. The path we need is simplicity underneath – #Oxfordboaters is doing three things:

  • Sharing information about what’s happening
  • Building a shared understanding of that information
  • Acting together based on that understanding

That’s it, strip away the noise, and that’s the whole system. It’s classic #actavisam: publish, discuss, act. You don’t need layers of management theory or complex governance frameworks to make that work. You need #KISS trust, visibility, and participation.

But we rarely get to operate at this level of clarity, the difficulty creeps in as people bring baggage – Everyone arrives with habits shaped by the #mainstreaming worshipping of the #deathcult that leads to the imposing of unthinking expectation of hierarchy (“who’s in charge?”) and fear of speaking openly (“will this be used against me?”) leading to the desire for control (“we need to manage the message”) this “common sense” mess leads to focus on avoidance of conflict (“let’s keep it positive and not rock the boat”).

    These aren’t individual personal failings, they’re social learned behaviours, that distort simple processes into complicated ones. This mess is amplified by a second “common sense” problem, that the tools we use shape behaviour, the #dotcons platforms we “use” default push us in particular mess making directions:

      • Chat tools fragment conversations into noise
      • Social media rewards reaction over reflection

      Instead of supporting collective clarity, these default tools amplify confusion, they make it harder to see what’s actually going on, and thus easier for misunderstandings to spiral. One tool we have is process but is it a tool or weapon? Process can either help people work together, or it can be used to block this work. Some processes are designed to:

      • Encourage participation
      • Make decisions visible
      • Build shared ownership

      Others – often unintentionally – end up:

      • Slowing everything down
      • Creating gatekeepers
      • Hiding power behind “procedure”

      You can see this easily when something urgent comes up – healthy process helps people respond quickly and collectively, were a broken one turns into endless discussion, deferral, and inaction. Same situation, same people – different outcome depending on the process.

      At #Oxfordboaters, the work itself is straightforward: There’s an issue affecting the river community – People gather information about it – That information is shared – A response is organised. But what makes it hard? People are different – Disagreements about tone (fluffy vs spiky), uncertainty about who should act and fragmented communication across platforms leading to #blocking of action.

      None of these are about the actual goal, they’re all about how people relate to each other and the structures they’re working within. The illusion of complexity is one of the biggest traps – mistaking this friction for complexity. When something feels hard, we assume the solution is to add more structure, more meetings, more rules, more #dotcons tools. But this “common sense” push to often adds another layer of blockage, it treats the symptoms, not the cause.

      The reality is harsher the system is simple, but we as a community are messy. So how can we work better in this mess? The answer isn’t to eliminate the mess – that’s impossible. It’s to design processes that work with it instead of work against it. That means accepting disagreement as normal, making conflict visible rather than suppressing it. Keeping structures lightweight and adaptable, in the end it’s about prioritising clarity over control. In #OMN terms, this is where the #4opens come in:

      Open data → everyone can see what’s happening

      Open process → decisions aren’t hidden

      Open source → tools can be adapted

      Open standards → systems interconnect

      These don’t remove human complexity, but they can mediate it from becoming opaque and blocking. So what do we mean by blocking vs enabling. You can tell the health of a project by a simple test – Does the process help people act, or stop them from acting? If people feel empowered to contribute → the process is working. Hesitant, confused, or sidelined → the process is blocking.

      At #Oxfordboaters, like many grassroots efforts, both dynamics exist at the same time. That’s normal. The work is to shift the balance toward enabling. So the hard truth is this the challenge isn’t building the perfect system, it’s growing the relationships that allow the #4opens path to function. That’s slower, messier, and far less comfortable than designing a neat process diagram, but it’s the only thing that actually works.

      Keep it simple (#KISS) – when things get messy, the instinct is to add complexity. The better move is usually the opposite by striping things back to focus on what actually needs to happen. Make it easier for people to take part, because underneath all the noise, the work is still simple. People, talking to each other, deciding to act. Everything else is either helping that – or getting in the way.

      What we’re growing at Oxford Boaters is simple

      From the towpath at dawn to moonlit moorings at dusk, Oxford’s boating community is not a curiosity, it’s part of the city’s living fabric. Generations of people have chosen to make their homes on the water, creating a culture rooted in community, care, and independence. This is a quieter Oxford, rarely captured in guidebooks but felt by anyone who walks the river or canal: a human-scale world of shared tea, passing conversations, and everyday presence. In a city shaped by wealth and exclusion, the river remains one of the few places where real social diversity still exists, where people live side by side not because of status, but because they’ve chosen a different way of life.

      This matters because the boating community doesn’t just live on the river, it sustains it. Their daily presence keeps the towpath safer, more welcoming, and alive. They act as informal stewards, noticing changes in the water, caring for the banks, and maintaining a relationship with the environment that no institution can replicate. Remove this community, and you don’t just lose homes, you lose Oxford’s character, its openness, its lived connection to the river. The waterway becomes quieter, more managed, less human. What looks, from a distance, like a marginal issue is in central, a question of whether #Oxford remains a living city, or becomes more controlled, polished and diminished.

      Exchange CRT for EA its the same story.

      How can we protect that space?

      We want to protect a shared space, keep the river livable, and organize ourselves to have a voice. None of that is technically complicated, the difficulty isn’t the goal, it’s the people, and the tools we use to try and work together. No matter what process we choose, it always comes back to the people who make it work, or the people make it stall. Some processes recognise this and work with human reality – trust, conflict, misunderstanding, ego, care. Other processes ignore it, and end up being used (consciously or not) as blocking. Let’s look at a few grounded examples of this.

      We’ve already seen this clearly, in a face-to-face meeting (the “whispering fire”), trust rises fast. People read each other, soften, find common ground. You can go from 50% to 70–90% trust in a couple of hours. Move the same conversation to online chat, and trust collapses. Tone gets lost, small disagreements escalate, and people start pulling things apart. You drop to 20–30% trust, sometimes lower. Completely different outcomes, it’s not a failure of individuals, it’s a mismatch between tools and human communication.

      The website vs the chat is another clear split. The website (or any structured space) holds higher trust, but lower participation. The chat holds high participation, but low trust – knowledge isn’t captured properly, decisions aren’t visible and new people can’t easily get up to speed. Result: constant rehashing, frustration, and burnout leading to momentum loss.

      There’s a temptation to design the perfect structure with formal agendas, strict procedures and detailed governance. On paper, this looks like progress, in practice, it becomes a brake. As people use “hard” process to delay decisions (“we need another meeting”), avoid responsibility (“that’s not my role”) and assert control (“this isn’t the proper channel”). Instead of enabling action, the process becomes a gatekeeper, leading to the same basic issues resurface again and again. Not because people are stupid, because the basic social fabric isn’t being maintained.

      Processes that work can see this cycle and design around it so as not to keep restarting from zero. So what actually works? The path isn’t finding a “perfect” process, it’s choosing #4opens processes that fit people as they are. That usually means prioritising face-to-face (or close equivalents) for trust building. Keeping structures simple (#KISS) so they don’t become tools of control. Capturing shared knowledge clearly (FAQ, summaries, decisions). Accepting mess as normal, but making sure it composts rather than festers. Balancing fluffy and spiky – you need both to move forward

      And most importantly recognizing that process is never neutral, every structure we put in place will either help people collaborate or give them ways to block each other. Often both at the same time. So yes, what #Oxfordboaters is trying to do is on the surface easy, but what makes it hard is human complexity, mismatched tools and blinded pushing processes that don’t align with either. When we get those bits even slightly more right, everything else becomes possible.

      If we don’t, even the simplest goals turn into a grind, that’s the real work.

      Closed systems protect individuals, but they rarely build movements
      Trust and fear – the spiky/fluff debate – OxfordBoaters

      Closed systems protect individuals, but they rarely build movements

      People fight against or/and ignore the #KISS (Keep It Simple Stupid) approach in tech because simplicity exposes power. Complexity, jargon, and process give cover – they make control look like competence. When paths are simple and transparent, everyone can see who’s blocking, who’s hoarding, who’s acting in bad faith. Many “experts” and institutions are emotionally and professionally invested in keeping things complicated; simplicity threatens their authority, their funding, and their identity.

      All the #OMN projects are not directly about social change – they’re about making social change possible. That distinction matters as people don’t step into change unless they first believe change can happen. If the world feels fixed, locked, inevitable, then nothing moves. Our role is simpler, and maybe more important, to open that door a crack, to show that different paths exist.

      Think of #OMN as a helping hand, not dragging people forward, not telling them what to do – just making it easier for them to take that first step when they’re ready. But to do this, we need to think more clearly – and more fundamentally – about technology itself. As most of the current “open paths” are cosplay at best, we need a network that links them as flows for there use to be unlocked from the current limits of #stupidindividualism shaping them – to become a native part of the expanding #openweb reboot.

      I’ve been working on this for over 20 years, and one thing keeps proving true: we need roughly 90% open and 10% closed, the balance matters. As the current push from the #encryptionists flips this – aiming for 90% closed and 10% open. That isn’t a solution, it’s a retreat. It breaks the social fabric that makes collective tools usable and meaningful. It fragments, isolates, and ultimately shrinks the space where shared culture can exist.

      Yes, privacy matters, yes, some things should be closed, that’s the 10%. But the commons – the space where we meet, talk, organise, and build trust – has to be open. Without that, there is no network, just silos. Take a simple example: you’re reading this via #activitypub. That’s a system built on being mostly open, with just enough closure to function safely. And it works, people are here, conversations happen, networks grow.

      Compare that to more closed, encryption-heavy systems like old school Diaspora. Technically interesting, sure, but socially? Empty, few people, little flow, no impact. That’s the core point: this isn’t just about functions or features, it’s about culture.

      Open federated, networked systems create the possibility of shared culture, and from that, the possibility of social change. Closed systems protect individuals, but they rarely build movements. We need both – but we need to get the balance right. Right now, too many people are getting it the wrong way round.

      This Isn’t New: Decentralisation Was the Point All Along

      Decentralised servers – what we now call the #Fediverse – are often talked about as if they’re some new, radical innovation. They’re not, they’re a return to the original design of the network. The early internet wasn’t built to be controlled, it was built to survive. The core idea was simple: if parts of the network were destroyed – even something as extreme as a nuclear strike – the rest would keep functioning. No centre, single point of failure or “off switch.”

      That’s what decentralisation actually means. And this thinking didn’t even start with the #openweb. Systems like Usenet already embodied this approach: distributed, federated, run by many, owned by none. Messy? Yes. But resilient, open, and hard to capture.

      What we’ve been living through for the last 20+ years – the rise of the #dotcons – is the opposite of this. Centralised platforms with single points of control. Easy to use for control and monetise, easy to manipulate, easy to shut down. We didn’t lose the #openweb by accident, we blindly traded it away for this convenience.

      What we’re seeing now with the #Fediverse, #ActivityPub, and related projects isn’t innovation in the common sense. It’s a reboot, a return to the path we were on before we derailed it. The difference is that now we’re trying to rebuild this in a world that has spent decades normalising centralisation and control. 40 years of death cult worship has changed people, institutions, social groups and our very internal selves. That’s where the friction comes from, people arrive expecting #dotcons platforms, what they find is networks. People expect control, what they get is responsibility. People expect “free” what they face is shared cost and care.

      So, it was never about the tech, the mistake we keep making is ONLY thinking this is a technical shift, it’s not, it’s cultural. You can spin up a decentralised server in minutes, that’s not the hard part, the hard part is everything around it:

      • Who runs it
      • Who pays for it
      • How decisions are made
      • How conflict is handled
      • How trust is built and maintained

      This is the work the #dotcons hide from us, they wrap control as “free services” paid for with surveillance, extraction, and control. Now that we’re back on the #openweb path, that work becomes visible again, and yes – it’s harder.

      Why this matters (Again). Resilience isn’t an abstract idea anymore as we’re living through cascading crises: political instability, #climatechaos, infrastructure fragility. A centralised network fails catastrophically were a decentralised network degrades – but keeps going. That’s the difference between a system you depend on and a system you can trust.

      We don’t need to overcomplicate this – Keep It Simple (#KISS)

      One builds commons, the other extracts value, everything else is detail. And yes nobody thinks the Fediverse is not messy, uneven, (yet) match the polish of corporate platforms. That’s fine, mess is where growth happens – if we compost it properly.

      The #OMN view, we’re not trying to invent something new. We’re trying to make what already works usable at scale for media, trust, and collective action. The infrastructure is there, the protocols exist, the history is long. What’s missing is the shared layer – the commons – where information flows in ways people can actually rely on, that’s what we’re building.

      If decentralisation feels radical, it’s only because we’ve spent so long inside systems that forgot #OMN #openweb #KISS

      Trust and fear – the spiky/fluff debate – OxfordBoaters

      People fight against or/and ignore the #KISS (Keep It Simple Stupid) approach to social movements because simplicity can expose power. Complexity gives cover, making control look like competence. When paths are simple and transparent, everyone can see who’s blocking, who’s hoarding, who’s acting in bad faith. Many “experts” and institutions are emotionally and professionally invested in keeping things complicated as simplicity threatens their authority and their identity.

      As second step in change and challenge we need to face some uncomfortable roots: fear of death, fear of the “other.” Fear, as the man said, is the mind killer. Too few people trying to change the world bother to look at the psychological ground they’re standing on. Our social mess isn’t random, it grows from somewhere. If we don’t deal with the roots, we just keep trimming the leaves and wondering why the weeds grow back.

      At the centre of this is trust, it is what makes social change possible. It’s the messy, ongoing tussle between horizontal and vertical forces, between collective process and imposed control. Take Oxford boaters as a lived example, this is observational, based on 40 years of doing this kind of work.

      Face-to-face meetings? They start at maybe 50% trust and can rise to 70% without too much trouble. That’s because the people who show up are self-selecting – a mix of fluffy and spiky, but open enough to engage. You get debate, but also movement.

      Then we go back online were trust drops fast – down to 20–30%, sometimes even into negative territory. That becomes the dominant tone as things splinter. Work that was built collaboratively offline gets pulled apart, the focus doesn’t hold.

      On the open collective website, trust is actually high – but usage is low, again, self-selecting. So rollout stalls, no shared space, no shared understanding, no momentum.

      So we call another face-to-face, the “whisper fire.” Trust shoots up – 90%, easy. People align, decisions get made, it feels like progress. But then everyone goes home, the next day? Momentum evaporates, as few people feel responsible for carrying things forward. And very quickly, we slide back into the low-trust dynamics of online chat.

      Meanwhile, the group has grown, more people from offline outreach and leafleting. But the website is still stalled, so there’s nowhere to hold shared knowledge. We keep re-arguing basics, we don’t even have a solid FAQ. Trust drops again.

      Next meeting: bigger pool, smaller turnout. Trust starts at near zero, the first half is rough – people filtering out, clashing, posturing. Slowly, some shared ground emerges and trust crawls up to maybe 50% but still, nothing concrete gets resolved. A few working groups are seeded. Environment sort of functions. Media splinters from the start, but manages a press release, but without any clear #4opens process. Beyond that, the next steps remain unanswered.

      Back online? Trust gets ripped apart again. The whisper fire is supposed to be every week, but we have lost focus, but we try agen – half-heartedly at first. Poor turnout, then people drift in after a couple of hours. Trust rebuilds to around 70%. Real decisions get made, consensus emerges, it starts to feel like an actual working affinity group.

      But the chat? Still toxic, low trust, constant tearing-down, fixation on side issues, and a push toward rushed bureaucratic structures that crumble under their own weight. The only thing that actually works is the consensus built in the whisper fire – because that’s what people really agree on, underneath the passive-aggressive noise. But after each cycle, trust in the online chat drops again, down below 30% on the surface. Maybe 40% underneath, if you’re generous.

      And now we hit the next stage: formal process, bureaucracy, decisions that actually matter, where it gets real. And because online trust is still so low, everything becomes harder than it needs to be, friction everywhere, misunderstanding as default.

      But – and this is the hopeful bit – offline trust is slowly growing. So maybe, just maybe, we can carry that through, if we don’t let the chat tear it apart first.

      Individual fears
      So how do we mediate this fear?
      Process is what gives legitimacy

      #OxfordBoaters

      We keep making mess, then wondering why everything smells

      A big part of this is the language we use, when we unthinkingly spread #mainstreaming terms, we push the worldview that comes with them, and that worldview is usually rooted in fear, control, and market logic.

      Take “digital sovereignty.” it sounds solid, sensible, progressive. But, it’s a made-up term trying to frame the internet in nation-state and market terms – ownership, borders, competition. It’s a liberal answer to a fear-based economy: “how do we control this thing so it doesn’t threaten us?” That framing is the problem, because the #openweb was never built on control. It was built on trust, shared standards, and open process – the #4opens:

      • open data
      • open source
      • open standards
      • open process

      That’s the native soil, when we blindly shift to language like “sovereignty,” we drag in assumptions that don’t belong. We start thinking in terms of ownership instead of participation, control instead of collaboration. And that creates mess – conceptual, political, and technical Then we spend years trying to “fix” that mess, composting it.

      But it’s much better if we don’t make that mess in the first place #KISS, by staying grounded in #openweb values. We don’t need to retrofit control structures onto something that was designed to work without them. We don’t need layers of governance theatre to simulate trust, we can build trust directly through open processes.

      This is why clarity, clear language matters, if we keep pushing borrowed language from the #deathcult, we’ll keep rebuilding its logic, no matter how good our intentions are. So yes, we need to talk more clearly about stopping importing broken concepts, stop framing open systems in closed terms and stop making more mess we then have to compost.

      Start from the roots, grow from there, please.

      The #dotcons, #mainstreaming, and Build to Walk Away

      Three years ago I was trying to explain something simple in language liberals might actually hear. They talk about “platform capitalism.” Fine. But I’ve been calling it the #dotcons for 20 years – because that’s what it is – a con.

      The last 30 years of tech hasn’t just drifted into this mess. It’s been shaped, step by step, enclosure by enclosure, into systems designed to extract value from us. What we now call the internet is, in large part, a machine built to manipulate, capture, and profit.

      The old #openweb got fenced in, and most people, especially polite liberal society, went along with it. So we need to talk about the return and the problem. Now we have a shift of the #mainstreaming is flowing back toward the #openweb, that should be a good thing. But there is a problem: people don’t leave the #dotcons behind when they move, they bring the culture with them.

      What we’re seeing is a flood of the same patterns – extractive behaviour, ego performance, status games. Not from one “side,” but from everywhere. The habits built inside the #dotcons don’t magically disappear just because the platform changes.

      So the real issue isn’t technical, it’s cultural. If we don’t actively mediate this influx, we won’t rebuild the #openweb – we’ll just recreate the same broken systems in slightly different code.

      So why do I talk so much about compost, and mess not being the problem. Mess is necessary, but only if it composts – if it breaks down into something fertile. Right now, we’re mostly just piling it higher.

      This is where projects like #indymediaback and #OGB matter. They’re not perfect, but they are native to the #openweb path: grounded in trust, process, and the #4opens rather than control, branding, and capture.

      The question isn’t whether #mainstreaming is good or bad. The question is: how do we hold the cultural line so that what grows is something genuinely different? Because if we don’t, the #dotcons don’t need to defeat us. We’ll blindly rebuild them ourselves.

      So why do I argue we can’t just leave the #dotcons? This is where people get it wrong, every time the #dotcons tighten control – censoring, tweaking algorithms, shifting rules – the reaction is the same: leave, build the #openweb.

      Yes, build the #openweb, but the idea that we should stop organizing inside the #dotcons right now? That’s a trap, because billions of people are still there. The conversations, the communities, the movements, they haven’t magically migrated. Walking away doesn’t free those people, it abandons them, leaving the space to be shaped entirely by the #deathcult and the forces already in control.

      This is #nothingnew. The #dotcons are #closedweb infrastructure. They serve power because they were built to serve power. Expecting anything else is misunderstanding the system. The real question has never been: are these platforms good? It’s: what do we do, given that this is where people are?

      The #geekproblem and the exodus fantasy, is a persistent fantasy – a classic #geekproblem – that if we just build better tools, people will come. They won’t, not on their own. A clean exodus to the #fediverse or any #openweb space doesn’t happen because we post about it. Movement-building has never worked like that, people move through relationships, trust, and shared struggle – not technical superiority.

      So if you abandon the spaces where people already are, you cut those pathways. The #OMN approach has always been simple to use the #dotcons as a bridge, not a home, seed organizing where people already are while focusing energy on building the #openweb in parallel to clearly keep your foundations in the #4opens.

      This isn’t about purity, it’s about effectiveness, don’t fall into #stupidindividualism, the idea that personal withdrawal is more important than collective reach. This is about infrastructure and grounding, if the #dotcons can switch you off at any moment, they cannot be your foundation.

      That’s why we need:

      • indymediaback as publishing roots
      • activitypub and the #fediverse as distributed infrastructure
      • OMN as a bridge between cultures and spaces

      This is the practical expression of the #4opens: not just open code, but open process and open trust. Don’t build your house on someone else’s land, but don’t stop talking to the people still living there either. Stay in the fight, when the #dotcons clamp down, it’s not a surprise, it’s a signal of what they are, and what they’ve always been.

      The answer isn’t to run away, it’s to root ourselves somewhere that can’t be shut down, while continuing to show up where the people are.

      Build the #openweb, stay in the fight, keep it simple #KISS

      Toward Healthier Digital Public Spaces: A Cultural and Structural Challenge

      From a practical perspective, the challenges in digital and social technology are not technical, they are cultural. This may seem obvious, but it is often overlooked in policy and implementation. At a basic level, there are two broad approaches to handling disagreement and complexity in online spaces:

      • Exclusion-focused approaches (e.g. blocking, filtering, silencing), which reduce immediate friction but reinforce fragmentation and polarisation.
      • Engagement approaches (e.g. dialogue, questioning, listening, and iterative response), which are more demanding but can, over time, reduce conflict and build shared understanding.

      In the current mess – shaped by strong norms of individualism and personal optimisation – the first dysfunctional approach dominates. This grows increasingly fragmented discourse, where communities become isolated and less resilient.

      Understanding this we can start to show the limits of “Common Sense” in today’s mess, were governance relies on this “common sense.” Over the past four decades, economic and cultural frameworks – market-driven individualism – has controlled how we design and use digital systems contributing to:

      • Increased social fragmentation
      • Growing economic inequality
      • Incentive structures prioritising engagement over well-being
      • Environmental and social externalities (including visible #climatechaos impacts)

      These outcomes tell us that existing models are not sufficient for building sustainable digital public spaces, so we need to #KISS revisit platform dynamics and structural Incentives.

      The dominant digital platforms (the #dotcons) operate on business models that prioritise data extraction, engagement metrics, and advertising revenue. These incentives shape what information is amplified, how users interact and which behaviours are rewarded. While these systems are effective at scaling control, they are not in any way aligned with public interest outcomes such as trust, accountability, or democratic participation.

      Current trends – ranging from disinformation to polarisation and environmental stress – highlight the limits of systems based purely on competitive, self-interested models. At the same time, alternative approaches – such as the #openweb and federated systems – offer more aligned values but face basic challenges of coordination, usability, and governance. So we need to move from fragmentation to constructive engagement, to reframe the problem, from crisis to stewardship.

      This more sustainable approach emphasises stewardship over extraction, collaboration over isolation to help build resilience over short-term optimisation. This does not mean abandoning innovation or individual freedom, but rather #KISS balancing these with responsibility for shared outcomes. As the current challenges in digital spaces are not only the result of “bad actors” or isolated failures. In simple terms we need to move from systems that amplify division toward systems that support understanding and the common good.

      To compost this mess we need a willingness to engage with complexity and a commitment to building systems (technical and social) that prioritise long-term public value over short-term individual gains. This is not easy work – but it is necessary if digital infrastructure is to support healthy, democratic societies.

      KISS – Keep it simple, sustainable, and focused on the common good.

      Why you should help

      The internet’s public square is privatised, algorithmically controlled for “engagement” over any idea of truth, and placed under the control of a handful of American corporations with no accountability to European citizens or values. The #Fediverse is the most credible existing alternative – but it lacks the shared infrastructure to function as a native commons for news and media. #OMN builds that infrastructure: trust-based, community-controlled, transparent, reversible, and owned by nobody. At €45,000 for a proof of concept, it is one of the cheapest possible investments in the long-term health of European digital public life. If it works – and the technical and social groundwork suggests it will – it becomes the plumbing for a Fediverse that can actually be used to serve democratic societies rather than more #techshit alongside the current #dotcons platforms that undermine them.

      Why this matters – because the #WWW was stolen – Designed as commons at CERN, decentralised, open, nobody in charge. What we have today is instead is five American corporations controlling the information diet of billions of people. Facebook decides what news you see. YouTube’s algorithm decides which voices get amplified. Twitter/X decides who gets banned. None of these decisions are transparent, accountable, or reversible. They are made by private entities in pursuit of control, advertising revenue and engagement metrics – not truth, not public interest, not democracy.

      The #Fediverse exists as a rejection of this, it’s the largest real functioning alternative to corporate social media, with millions of people on thousands of servers, federated together, nobody owning the whole thing. It works. It’s growing. But it has a weakness: it’s kinda fragmented at the commons layer. There’s no shared infrastructure for how news and media actually flows across the network in any trustworthy and coherent way.

      That’s the gap #OMN fills, but why? Most people don’t think about internet infrastructure. They think about whether they can trust what they read. Whether the news they see is real. Whether the platform they’re on is working for them or selling them. Whether they can do anything when something goes wrong.

      Right now the answer to all of those is: it depends entirely on decisions made by people you’ll never meet, for reasons you’ll never know. OMN proposes something different. If your community trusts a source, a trust flow, you see it. If they don’t, you don’t. And that decision is yours, reversible, transparent, locally controlled.

      For a journalist in a small country trying to get independent news out, this is the difference between having infrastructure that works for them and being at the mercy of a platform that can deplatform them overnight. For a community archive trying to keep historical memory alive and accessible, this is the difference between dependence on Google’s goodwill and owning your own distribution. For an ordinary person trying to figure out what’s true, this is the difference between an algorithm designed to maximise your outrage and a network shaped by people you actually trust.

      Bureaucracies fund things slowly, in ways that often serve existing power structures rather than challenging them. But digital sovereignty is an existential European concern. The EU has spent years trying to regulate American platforms – GDPR, the Digital Services Act, the Digital Markets Act – and the platforms have responded with compliance theatre, token gestures, and armies of lawyers. Regulation of concentrated private power is a losing path. The only actual answer is to build the alternative infrastructure so that people have somewhere else to go. That’s what the NGI Commons Fund is for and what #OMN does.

      The EU should not only be funding products, it needs to fund commons infrastructure – the plumbing that nobody owns and everyone can use. Like funding roads rather than funding a logistics company. The outputs are open source, meaning any European media organisation, any local community, any public institution can pick this up and use it. No lock-in. No dependency on a vendor who will be acquired or shut down.

      It’s cheap, with the second stage scaling across Europe with institutional partners, building on European strengths. The Fediverse is disproportionately European. Mastodon was built by a German developer. The culture of digital commons, open standards, and public interest technology is stronger in Europe than anywhere else. This project is native to that tradition. It’s not asking Europe to compete with Silicon Valley on Silicon Valley’s terms – it’s asking Europe to build the alternative on its own terms.

      The problem #OMN solves is getting worse, not better. Disinformation, algorithmic radicalisation, platform capture of public discourse – these are not abstract threats. They are actively destabilising European democracies. Funding the technical infrastructure for trustworthy, community-controlled information flows is not a nice-to-have. It is digital public health infrastructure.

      #KISS

      Thematic call: NGI Zero Commons Fund

      Organisation: Open Media Network (unincorporated community project, fiscal hosting in Belgium via OpenCollective) Country: United Kingdom General Project Information Proposal name: Trust-Based Media Flows for the Fediverse (#OMN) Website / wiki: https://unite.openworlds.info/Open-Media-Network/Open-Media-Network

      Abstract

      Can you explain the whole project and its expected outcome(s)?

      The Open Media Network (#OMN) is a protocol-driven, federated media infrastructure built on top of ActivityPub and the Emissary codebase (emissary.dev). It addresses a real gap in the current Fediverse: while platforms like Mastodon, PeerTube, and Lemmy are federated at the instance level, there is little coherent cross-platform layer for trust-based content flows, moderation, or news aggregation. Each instance operates largely as its own silo, moderation is hierarchical and per-server, and there is no shared commons model for media distribution across the ecosystem. #OMN proposes a minimal, compostable interaction model – the Five Functions (#5F): Publish, Subscribe, Moderate, Rollback, and Edit Metadata – implemented as a flow layer on top of existing Fediverse infrastructure. Content moves through the network as objects flowing through pipes and holding tanks, filtered and shaped by trust relationships between nodes rather than by opaque algorithms or centralised authority.

      The central R&D question is: can trust-based moderation and distribution flows replace algorithmic amplification in a federated news ecosystem? Expected outcomes of this first-stage grant: By Month 3: A technical specification of the flow architecture; a prototype flow service routing ActivityPub objects between two instances; documentation of existing Fediverse flow patterns; early integration with one platform (likely PeerTube). By Month 6: A cross-platform prototype connecting at least two Fediverse systems; a working demonstration of trust-based moderation flows; a public code repository and documentation; and a user-facing prototype via the #makinghistory test environment (https://unite.openworlds.info/Open-Media-Network/MakingHistory). All outputs will be released under recognised open source licences. The project follows the #4opens framework: open data, open source, open standards, and open process.

      Have you been involved with projects or organisations relevant to this project before?

      Yes. The project lead, Hamish Campbell, has over 40 years of experience in grassroots media and technology, including early involvement with Indymedia – the pioneering open publishing news network – and more than 8 years working directly with the Fediverse and ActivityPub community. The #OMN conceptual framework has been developed over this time and is documented extensively in the project wiki, SocialHub, and at https://hamishcampbell.com. Developer Michael has contributed to #OMN concepts and logic for 10 years and is currently building the #makinghistory reference implementation. Ben, the core developer of Emissary, brings specific expertise in the codebase that will form the technical foundation of the project. Alex brings potential DAT/distributed storage support, and IKA will work on testing and rollout.

      Requested Support Requested Amount: €45,000

      Explain what the requested budget will be used for. Does the project have other funding sources, both past and present? A breakdown in the main tasks with associated effort is appreciated. Make rates explicit. The budget covers a lean, seed-stage proof of concept with no prior external funding. There are currently no other funding sources. The budget breakdown can be found in the attached PDF (funding). Roles: Hamish Campbell (project lead, coordination, documentation, community engagement) and Michael Saunders (primary development, UX, system logic). Additional contributors (Ben, Alex, IKA) are contributing on a voluntary/community basis during this seed phase. Work packages and approximate effort: WP1 Research & Specification (Months 1–2, ~25% of effort): Architecture design, gap analysis of existing Fediverse tools and flows (PeerTube, Lemmy, Mastodon), and documentation of trust-flow patterns. Output: Technical design document. WP2 Core Development (Months 2–5, ~45% of effort): Flow service implementation on top of Emissary; ActivityPub integration for the #5F model; and a trust-based moderation layer extending Emissary’s existing block/flag capabilities. Output: Working prototype codebase. WP3 UX & Prototype (Months 3–5, ~20% of effort): #makinghistory user interface; dual-layer UX (simple and advanced modes); and WCAG 2.1 accessibility compliance. Output: Testable user prototype. WP4 Testing & Documentation (Months 5–6, ~10% of effort): Community testing and iteration; public documentation and reports; and an open knowledge base of what works and what fails. Output: Public documentation, reports, and reusable design patterns. LINK PDF and wiki

      Compare your own project with existing or historical efforts.

      The closest existing efforts are: Mastodon’s built-in moderation tools: per-instance block lists and the Fediblock community blocklist. These are instance-level tools – they do not create cross-platform trust flows or shared content aggregation. #OMN operates at the network layer, not the instance layer. Fediseer: a trust registry allowing instances to vouch for each other. Fediseer addresses instance-level reputation but does not implement content flow logic, rollback, or metadata editing as network functions. #OMN builds a compostable flow model on top of the kind of trust signals that Fediseer represents. GNU Social / Friendica: older federated social platforms with some aggregation capability. These predate ActivityPub’s consolidation as the dominant standard and do not address the cross-platform news/media commons use case. Indymedia (1999–2010s): the historical precedent for open publishing federated media. Within the wider project, #OMN explicitly revives and modernises the Indymedia model for the ActivityPub era via the #indymediaback reference implementation, addressing the unfinished work of that tradition. The #makinghistory project grows from, and shares, this same established workflow. Bonfire networks: likely related, but unclear in scope and function. Attempts to install and use it have not clarified its approach. It may be trying to address similar problems, but this remains uncertain. The key difference of #OMN: it is not building a new platform. It is building a protocol-level flow layer that works across existing Fediverse platforms, implementing trust-based content propagation as commons infrastructure rather than as a product. See included PDFs.

      What are significant technical challenges you expect to solve during the project?

      1. Trust flow implementation: Designing and implementing a data model for trust relationships between federated nodes that is lightweight, compostable, and expressible via or alongside ActivityPub. Trust is local and subjective – the system must allow different communities to apply different trust filters to the same content flow without requiring global consensus.
      2. Rollback across federated state: Implementing the rollback function (re-evaluating and reshaping historical content visibility) in a distributed system where content has already propagated to multiple nodes. This requires a time-aware, local re-indexing approach rather than a global delete mechanism.
      3. Cross-platform content normalisation: Aggregating content objects from Mastodon (short-form social), PeerTube (video), and Lemmy (forum) into a common JSON-LD content model with a consistent trust trail, despite these platforms having different ActivityPub implementations and object schemas.
      4. Search actors as push feeds: Implementing the “content finds you” model – where a defined search query becomes a persistent ActivityPub actor that pushes matching new content to subscribers – requires extending Emissary’s existing subscribable search engine capability.

      Describe the ecosystem of the project, and how you will engage with relevant actors and promote the outcomes.

      The primary ecosystem is the Fediverse: the network of federated, open-source social platforms running ActivityPub, including Mastodon, PeerTube, Lemmy, Friendica, and many others. This ecosystem has grown substantially (estimated 10+ million active users across thousands of instances) but remains technically fragmented at the commons/media layer. The project builds directly on the Emissary codebase (https://emissary.dev), an existing ActivityPub-native Go application. Engagement with the Emissary community is embedded in the team through Ben’s mentoring role.

      Wider ecosystem engagement:

      The project will contribute design patterns and documentation back to the broader Fediverse developer community via public code repositories, the project wiki, and events. The #makinghistory test phase connects us to existing archives such as Bishupsgate, Maydyroom, the Peace Museum, and the Campbell Family Archive, providing access to extensive datasets as well as outreach to their administrators and users. The five community events included in the budget are specifically designed to recruit contributors, gather real-world feedback, and expand the network of participating nodes.

      Promotion of outcomes:

      Outcomes will be shared through the Fediverse itself (maintaining an active presence on ActivityPub-native platforms and legacy social media), via open-licensed documentation, and through NGI/NLnet networks and events. This first-stage grant is explicitly designed as a seed and proof-of-concept phase, with a larger second-stage proposal planned to deliver a fully production-ready system once the core architecture is validated.

      See attached PDFs.
      Powered by Forgejo

      Technical SpecificationDownload


      Answering the small print for fundingDownload
      FundingDownload

      Would like to thank all the meany people who helped with this.

      How things can change

      Hope this helps compost some of the mess building up. It’s something we all need to do and have responsibility for.

      Groups don’t usually fail because of external pressure, they fail because they turn inward and burn energy on themselves. If you want a calm, #KISS path that actually holds diversity without collapsing, we need a few simple lived – traditions and mythos – not heavy governance, not ideology battles, just grounded #KISS practice:

      • Keep the core action very small and clear – a shared purpose. If people can’t easily answer “what are we doing?”, drift and conflict creep in.
      • In twine “doing” with “talking” Most infighting comes from too much abstract discussion. Doing space – Talking space – Don’t let one swamp the other.
      • Protect focus like it’s fragile (because it is), the biggest risk isn’t disagreement – it’s distraction. When things start spiralling bring it back to “what are we building this week?” if it doesn’t help, park it
      • Default to trust, but design for friction, diversity is strength. But unbalanced diversity = chaos. So let people approach things differently, but require shared outputs – If it doesn’t produce something, it doesn’t dominate attention.
      • No purity tests, this is where diversity dies. People will come with different politics, paths (fluffy vs spiky) and have different priorities, that’s fine – as long as they don’t block others doing the work.
      • Make conflict low-energy, not zero-conflict – we won’t avoid disagreements. Trying repression = explosion later. Instead, keep arguments short, move unresolved tension into parallel paths (“try both”) and let results decide, not personalities. This is the “compost” approach we need to talk about – don’t fight the mess, process it.
      • Grow by doing, not convincing, you don’t need everyone to agree. You need visible, working examples. Let people see it working – that’s what grows a community of action.

      What we are sketching and building is the hard middle path of not rigid control (kills growth) and not total openness (creates chaos). But a light structure that keeps things moving.

      #Oxford example:
      Oxford boaters are sovereign, keeping the free-flowing life of the river, not bound by the old rules of the landlords.

      #Fediverse example:
      The Fediverse is native to the #openweb path. We judge by the #4opens, and walk with power.