Tag: KISS

Why you should help

DRAFT

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, so why should normal people care? 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.

Why the EU specifically should fund this. 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 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.

Rebuilding Journalism as Commons (not a product)

News culture on the Fediverse

It should be obvious that we need a path back to good journalism – journalism that sheds light on facts, connects the dots, and lets people trace those dots back to sources. This is what allows us to share, question, and discuss within our own trusted communities, and then spread that knowledge outward through federation, always linking back to the source.

Right now, the #mainstreaming path is broken. It’s sometimes hard for people to see this because the decline has been slow, a gradual death of journalism. Since the early days of the internet, we’ve been told the same story: “People expect news for free, so quality journalism is no longer economically viable.” There’s truth in that. Good journalism is expensive. It takes time, skill, trust, and institutional memory.

But that’s only half the story. What actually happened is this: people kept consuming familiar “news brands,” and those brands were bought, consolidated, and financialised until shareholder value replaced any sense of public value. Slowly, investigative journalists were cut and sidelined, editorial independence eroded, and content shifted toward ads, PR, and narrative management. What we now call “news” is marketing, agenda-setting, and reputation management – a distraction. Journalism, as a public good, has been hollowed out, in part through our own passive acceptance of this shift.

Today, we can see more clearly that if you do real journalism – the kind that challenges power – you have no real career path and face risks: #dotcons blocking, right-wing co-option, and at worst, isolation, exile, prison, or worse. The result is a broken landscape: corporate media that won’t tell the truth, and under-resourced independent media that carries high risk for little or no reward. In that situation, who chooses journalism as a life path?

The deeper problem is articulation and power. The world is complex, most people don’t have the time, energy, or tools to fully articulate what they see, feel, and experience. Into that gap step politicians, corporations, and #fashernista influencers. They have the resources – especially through the #dotcons – to articulate reality, but in ways that divide people, flatten complexity into conflict, and steer perception to serve power and profit. This isn’t just misinformation. It’s structured narrative control.

Why the old models won’t come back, we can’t simply “fix” legacy media. It is structurally tied to advertising, concentrated ownership, and political influence. And we can’t rely on heroic individuals either, that path is too fragile, too dangerous, and too easy to suppress. If journalism is going to survive, it won’t look like the past.

A different path: journalism as networked commons. At #OMN, we’re outlining a different approach decentralised, collective path. Think of it as a second coming of #Indymedia, but more resilient, more sustainable, and better integrated with current networks.

This is where the #openweb and the #Fediverse matter. With protocols like ActivityPub, we already have the foundations for distributed publishing, shared visibility, and cross-community discussion. But tech alone isn’t enough, the missing layer is trust and flow. To rebuild journalism, we need to focus on how information flows socially, not just how it’s published.

This is where #OMN comes in:

  • Content flows between communities
  • Trust is applied locally, not imposed globally
  • Metadata (tags, context, sources, warnings) travels with stories
  • People can trace information back through the flow

Instead of one “authoritative source,” we get many sources, with visible relationships between them, shaped through community trust and discussion. This is journalism people can actually use to follow a story back to its sources, add context and local knowledge and share and challenge it within trusted spaces.

That’s how we rebuild public understanding – not just publish articles – but from product to process. Journalism should not be a product to consume, it needs to be a process we participate in. When it’s treated as a product it’s optimised for clicks, shaped by incentives and in the end controlled by owners. When it becomes a process it becomes collective, accountable and thus resilient.

So composting the mess, we’re not starting from nothing, we have the ruins of legacy media, the lessons of projects like #Indymedia and the living infrastructure of the #Fediverse. This is compost, from it, we can grow something new – grounded in the #4opens, simple enough to understand (#KISS), and social at its core, not just technical.

The real question isn’t “How do we save journalism?” It’s: How do we rebuild the social systems that make truth-telling possible? Because without those paths, journalism doesn’t just struggle –
it disappears.

Oxford – Boaters & Landowners: A Simple Path Forward (#KISS)

In Oxford we are currently at a recurring stress in how river space is shared between boaters, landowners, and other users (such as rowers and towpath communities). The direction we take will shape not just access, but the character and sustainability of the boating community itself.

Best vs Worst Outcomes

Best outcome is a consensus synergy between boaters and landowners.

* Builds trust and cooperation

* Encourages better self-management within the boating community

* Strengthens a shared sense of stewardship over the river

Worst outcome is the spread of static, paid moorings.

* Prices out existing boaters

* Replaces a living community with “posh houseboats”

* Leads to the destruction of the current, diverse boating culture

A Practical Middle Path

Rather than conflict or heavy regulation, we propose a simple, collective approach based on shared good practice. What would this look like in practice? A lightweight, voluntary “covenant” of good boater behaviour:

* Leave at least 2 metres between moored boats to allow safe exit from the water

* Keep boats and the towpath tidy and welcoming for all users

* Respect visitor moorings – do not overstay

* Avoid leaving empty boats unattended over winter

* Share the river space, including moving boats when needed for rowing events

This Approach:

* #KISS (Keep It Simple, Stupid): simple guidelines over complex enforcement

* Collective responsibility: community-led, not imposed from above

* Open process: visible, understandable, and adaptable

This does not legally bind boaters, but it:

* Encourages better collective behaviour

* Demonstrates responsibility to landowners and authorities (e.g. EA)

* Reduces pressure for restrictive regulation

Role of Landowners & Trusts

For balance, landowners also have a role to play:

* Provide at least two visitor moorings on their stretch of river

* Set a recommended capacity (not rigid limits) for boat numbers

* Engage in ongoing dialogue with the boating community

Open Questions for Discussion

* How do we encourage adoption of this covenant without enforcement?

* What is a fair balance between flexibility and responsibility?

* How can boaters and landowners maintain ongoing communication?

* What practical steps can we take now to move toward this “best outcome”?

This is a light-touch, community-first aimed at avoiding the worst outcome while building toward the best. If we act collectively and simply, we can preserve both access and community – without defaulting to exclusion, pricing out, or over-regulation.

Why do this – Boaters & Landowners

Framing the problem matters, we’re in a familiar pattern pressure builds → calls for regulation → community gets squeezed. This draft is about interrupting that cycle, the aim is simple:

* Give “them” something (landowners, authorities, rowers)

* Strengthen “us” as a visible, responsible community

* Untick the boxes that they use to justify intervention

* And in doing so, slow or deflect heavy-handed regulation

Not by confrontation (yet), but by being seen to act. The strategy is instead of waiting to be regulated, we act collectively to show responsibility to create a visible “good enough” standard. This gives everyone something to point to and say “Something is being done.” That alone often reduces the push for stricter control. Yes, there are multiple directions we could take:

1. Do Nothing (Status Quo)

* No shared standards

* Continued friction with landowners and other users

* High likelihood of imposed regulation

Low effort, high long-term risk

2. Top-Down Regulation

* Paid moorings

* Strict enforcement

* External control of boat numbers and behaviour

High control, loss of community, exclusion of existing boaters

3. Soft self-governance (Proposed path)

* Voluntary guidelines

* Visible collective responsibility

* Ongoing dialogue with stakeholders

Low bureaucracy, preserves culture, reduces pressure

4. Formalised self- organisation

* Boater associations or councils

* Agreed codes with some internal enforcement

* Recognised representation in negotiations

Stronger voice, but risk of internal gatekeeping and drift into bureaucracy, in the end the current community would be priced out anyway.

5. Hybrid Model

* Light self-governance + minimal agreed regulation

* Shared responsibility between boaters and landowners

* Periodic review rather than fixed rules

Balanced, but requires trust and ongoing effort and is unlikely to have a good outcome due to shifting priorates we have no power over.

So filling the gaps (What’s missing). To make the “soft self-governance” path credible, we need better visibility – A simple public-facing statement of principles, something landowners and authorities can point to. I suggest we create a open collective (I can look into this https://opencollective.com/search?q=UK&isHost=true&country=GB )

Encouraging good behaviour through norms, quietly discouraging behaviour that causes conflict. Framing boaters as stewards, not problems by emphasising contribution to river life and culture

Some questions for feedback:

* Does this feel like enough to shift perception?

* What would make landowners actually trust this approach?

* Where does this fall down in practice?

* What’s missing that would make this work on the ground?

* Which path do people actually think is realistic?

Gates vs Bridges: the obscure politics of the #geekproblem

In the #geekproblem mindset, crossing a protocol flow is a gateway were in #openweb terms, it’s a bridge. That difference is not technical – it’s social – the difference between CONTROL and TRUST. A gate is something you lock, permission, authentication, enforcement were a bridge is something you cross, connection, flow, relationship. In the physical world, we don’t put gates on bridges as a default, but in software, we keep rebuilding them, and then wondering why things fragment.

  • RSS is a bridge.
  • Closed APIs are gates.

This should be obvious, but it keeps getting lost inside coding culture.

This isn’t just a #mainstreaming problem, if this critique only applied to Big Tech (#dotcons), it would be easy, but it doesn’t. From 30 years of building in alt-tech spaces – hundreds of projects, no bosses, no corporate control – the same pattern keeps reappearing. Control creeps in, what’s striking is that this cuts across both mainstreaming “professional” engineering culture and radical, horizontal, “alternative” tech spaces. That’s why it’s an overarching #geekproblem, the shared cultural bias toward CONTROL in both code and community design.

The deeper issue is social blindness, at the root of this is something uncomfortable – A lack of joined-up social thinking – when a relatively small technical minority designs systems based on limited social experience, abstract models of human behaviour and little grounding in historical or grassroots movements.

When these systems scale globally, the result is tools fail to support humane, collective use, and undermine trust instead of building it, they reproduce the same power dynamics they claim to escape. This feeds the wider #dotcons worldview – even when the intent is “alternative”. It’s not just “the spirit of the age” it’s a worldview of a narrow culture that has become infrastructural. We’re all, to some extent, still operating inside this #deathcult logic, even when we think we’re critiquing it.

So a good first step is looking at who is funding the problem, this is where foundations and FOSS funding bodies need to look closely. A lot of funding unintentionally reinforces gate-based architectures, complexity that centralises control and abstract innovation over lived social practice. We keep funding new gates, then asking why the #openweb doesn’t grow. It #KISS that if people cannot mentally model a system, they cannot govern it, if they cannot govern it, power centralises every time.

A different path is bridges and flows. Projects like #OMN and #indymediaback take this different approach of start with flows, not platforms, building bridges, not gateways. The focus is on keeping systems simple enough to understand (#KISS) to grow trust as social and visible, not hidden in code. Using the #4opens as grounding, not branding, we understand none of this is new, that’s the value of #nothingnew. As I keep pointing out it’s how RSS worked, early Indymedia worked and large parts of the existing Fediverse still work (when not over-engineered).

On #blocking and conflict – Yes, it’s sometimes necessary, but often it’s a symptom of deeper failure of rigid, internalised worldviews, lack of shared mediation tools and systems designed for exclusion rather than negotiation. It’s easy to block, it’s much harder to build bridges, so the real question is how do we design systems that reduce pointless conflict without exhausting the people inside them? Food for thought (and compost).

We’re all carrying some of this mess, it’s fine – it’s compost. But if we don’t consciously shift from gates to bridges, we’ll keep rebuilding the same broken systems, just with nicer branding. As bridges scale trust – Gates scale control, to mediate this mess, the hard question we need to ask the #mainstreaming is which one are they funding?

#openweb #4opens #OMN

Let’s try and simplify the #OMN

The #OMN Framework: The Five Functions (#5F)

The #OMN is simple flows, not platforms, it’s a way of thinking about media as flows of objects moving through a network. People shape the flow, you can find a more technical view to read after here. A human-scale, federated media infrastructure built on #FOSS practices and the #4opens:

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

It doesn’t start with features, apps, or ideology, it starts with flows. Imagine the network as:

pipes and holding tanks

Content (objects) flows through them, communities decide how that flow is shaped. Nothing magical, nothing hidden. This matters because:

If people can’t picture how a system works, they can’t govern it.
And when systems become opaque, power centralises.

So #OMN reduces everything to five simple functions:

1. Publish

(Add a drop to the flow)

Publishing is simply adding an object:

  • a story
  • a post
  • media
  • data

to a stream.

  • No automatic amplification
  • No built-in authority
  • No algorithmic boost

Publication is contribution, not domination.

2. Subscribe

(Connect the pipes)

Subscription is how flows connect:

  • people
  • groups
  • topics
  • instances

This replaces:

  • platform logic → “you are inside us”
    with
  • network logic → “this connects to that”

No opaque ranking, you decide which pipes you connect.

3. Moderate

(Filter and route the flow)

Moderation is not censorship. It’s sieving.

Flows can:

  • pass through
  • be filtered
  • be slowed or prioritised
  • be contextualised

Trust is:

  • local
  • visible
  • reversible

Different communities can apply different filters to the same flow.

This is a feature, not a bug.

4. Rollback

(Drain and reset the flow)

Rollback is how systems recover:

  • remove past content from your stream
  • undo aggregation decisions
  • correct mistakes
  • respond to abuse

Without rollback:

  • errors become power struggles

With rollback:

Accountability becomes procedural, not punitive.

5. Edit Metadata

(Shape meaning downstream)

Content is not rewritten – it is contextualised.

Metadata can include:

  • tags
  • summaries
  • trust signals
  • warnings
  • translations
  • relationships

This is where meaning is created.

Not by algorithms, but by people.

The Holding Tank

Underneath it all is:

a simple storage layer

  • a database
  • stored objects
  • moving through flows

No “AI brain” or hidden feed logic, just data shaped by social processes.

Why This Matters

Most current systems bundle everything together:

  • identity
  • publishing
  • distribution
  • moderation
  • monetisation

This creates centralised control, even when systems claim to be “open”.

OMN does the opposite:

It separates the core functions.

This makes the system:

  • understandable
  • auditable
  • forkable
  • governable

#NothingNew by Design

This model isn’t new, it mirrors systems we already understand:

  • plumbing
  • electrical grids
  • packet-switched networks
  • version control

That’s intentional.

Systems people understand are systems people can govern.

From Platforms to Commons

The #5F is the smallest possible set of actions needed to run a media network:

  • Publish
  • Subscribe
  • Moderate
  • Rollback
  • Edit

Everything else:

  • feeds
  • timelines
  • notifications
  • UI/UX

…is just interface, nice to have but not essential.

The Point Is – The OMN is not about building a better platform.

It’s about building:

infrastructure for a democratic digital commons

Simple flows.
Social mediation.
Human control.

Not control systems, but trust systems.

In One Line

#OMN is plumbing for the #openweb. #KISS

To simplify the Open Media Network (#OMN), we focus on its core goal: creating a human-scale, community-governed media infrastructure that isn’t controlled by big corporate platforms. As we outline to understand and “simplify” the #OMN is a simple workflow:

  • Write: Creating the content.
  • Tag: Categorizing it, so others can find it.
  • Publish: Making it available on the web.
  • Federate: Sharing it across different trusted networks.
  • Archive: Ensuring it remains accessible over time.

The “#4opens” Framework is built on four principles designed to keep power in the hands of communities and users rather than central authorities:

  • Open Data: Information belongs to the community.
  • Open Source: The code is free to see and change.
  • Open Process: Decisions are made transparently.
  • Open Standards: Systems can “talk” to each other without gatekeepers.

Key Concepts for Simplification

  • Keep It Simple (KISS): The system should be so simple that anyone can mentally model how it works. If it’s too complex to understand, it’s too complex to govern.
  • Social over Technical: Prioritise how people use the tools over how “elegant” the code is, to mediate the #geekproblem (tech that’s too hard for normal people to use).
  • Composting the Past: Instead of starting from scratch or repeating old mistakes, the #OMN is about taking the “wreckage” of previous projects and turning them into “fertile soil” for new, federated networks.
  • Trust-Based Networking: It moves away from global algorithms and toward small, connected “nodes” of people who trust each other (or not).

You can build any application from this foundation – that’s the point of keeping the core this simple. On top of the basic #OMN #5F, we’re developing a set of seed projects:

  • #makinghistory – tools to keep grassroots and mainstream history alive, linked, and evolving across the #openweb
  • #indymediaback – a reboot of grassroots news, open publishing with modern federated infrastructure
  • #OGB (Open Governance Body) – lightweight, federated governance for coordinating people, decisions, and trust
  • #digitaldetox – a horizontal tool to step away from addictive, manipulative platform dynamics

Interoperability is default, not an afterthought, nothing is locked in, instead of building another isolated platform, we plug into the existing ecosystem, extend it to compost what doesn’t work. This is how we grow the #openweb by building better flows inside what already exists, not by replacing everything.

These aren’t separate silos, they’re expressions of the same underlying flows. The system is native to the Fediverse, built on ActivityPub. That means content flows in from existing platforms and codebases and flows out to existing networks and apps.

Compost metaphor – is memorable, not just technical. The focus on process over platform is clear and important. The move to simple steps works as onboarding and the insistence on #KISS + #nothingnew is the right first step.

#OMN is not an app, it’s a process + tools to move from isolation to commons.

The Digital Commons: The Ground We Already Stand On

At #NOAW event I talked a lot about the digital commons so thought it might be useful to write a post grounding this. The digital commons are not a future vision, it’s something we already have. At its simplest, the digital commons are the widely used #4opens digital resources of software, knowledge, data, and culture created collectively, governed by communities, and made available for public (re)use. This is the native path of the #openweb it’s been around for a long time, it might be hard to see but just about all of our current #dotcons mess is built on top of this layer.

There is a long history of commons in wider society. But mostly today we focus on the licences that protect reuse and sharing. None of this is abstract theory, it’s making the practical, working infrastructure that underpins much of what people still find useful online. One of the roots of the current digital commons go back to the 1980s and the emergence of the free software movement, led by Richard Stallman and the Free Software Foundation. This was not just about code, it was a social and political project:

  • Software should be shared
  • Users should have control
  • Improvements should remain in the commons

The creation of the GNU General Public Licence was the first step, enforcing a simple rule that if you benefit from the commons, you give back to the commons. The commons isn’t one thing, it’s an ecosystem – Some #KISS examples include:

  • Wikis – collectively written and maintained knowledge (#Wikipedia)
  • Open source software – built in public, shared freely (#FOSS)
  • Public code repositories like GitHub used to be (name one)
  • Open licensing systems like Creative Commons
  • Federated social tools built on ActivityPub (#Mastodon)

The Path is governance by the people who use it. What makes the digital commons different from “just free stuff” is this the people building it can shape how it works, a key distinction it’s not just access – it’s agency. The commons are non-exclusive (available to others), oriented toward use and reuse and governed by its participants, this is why it matters politically.

Today, much of the internet still runs on the digital commons, but the visible layer is dominated by #dotcons platforms. This creates a split of Commons layers → open, slow, sustainable and Platform layers → closed, extractive, growth-driven. People still rely on the commons, but interact through closed systems, this contradiction is unstable.

Policy is our current-missed opportunity, as our institutions see only the surface value. The European Union’s European Commission has pushed open source strategies as part of digital sovereignty, particularly through programmes like Horizon Europe. The idea is native – Share code – Collaborate openly – Build public infrastructure. But in practice, most of this gets lost in #NGO process, bureaucracy, and capture. The money flows, but the commons don’t grow.

The “Tragedy” of the Digital Commons. Like any commons, in the mess we live in today commons can be degraded from overuse (infrastructure strain), pollution (spam, low-quality content, noise) and information overload. The result is a corrupted signal-to-noise ratio, it is a real issue – but it’s to often used as an excuse to centralise control. This is largely solved by horizontal vs virtical scaling, if people can take this real native path.

There are social gaps. The commons reflects the culture that builds it, yes gender imbalance persists, access is uneven, and geek culture is too often exclusionary (#geekproblem). But the bigger problem we face is capture and drift. We’ve already seen it happen once: Free software → “open source” (politics stripped out). Commons → #dotcons platform capture.

Now we see this happening in the #Fediverse and #openweb reboot spaces with the last few years of vertical agendas dominating to meany outreach spaces, #NGO mediation and thus diluten is pushing native grassroots agency out, this is an old cycle repeating – the cycle that we need to compost.

OK, despite all the #mainstreaming mess, the digital commons are still the most viable path we have, we need to see this path not as hypothetical – more as it just works, but is underresourced. From a #OMN perspective, the digital commons are not only infrastructure, it’s the soil. You don’t build movements on platforms, you grow them in commons, but this growth needs care:

  • Protection from capture
  • Active governance
  • Social grounding, not just technical process

And most importantly the commons only survives if people act as commoners. The challenge now isn’t only to explain the digital commons, it’s to defend, rebuild, and extend it. That means funding native projects, keeping governance in the hands of participants to bridge activism, development, and real-world use as a path to push back against the continuing #mainstreaming capture.

This is not about nostalgia, it’s about #KISS recognising that we already have the tools we need, then caring enough not to only exploit them. Please try and be better than the current #mainstreaming on this, thanks.

Proposal – from #NOAW

A Note on “Security” for the #FOSS Crew

We need to have a clearer, more grounded conversation about “security” and what it actually means in the context of the #openweb. There is a long history of thinking in #FOSS spaces that security is something we can solve purely technically: better encryption, better protocols, better architectures. But in everyday life and practice, people need to work from a much simpler starting point – We do not trust client–server security. We only meaningfully trust what can be verified through the #4opens. And even with #p2p, we keep our trust closed limited.

Why? Because the underlying systems people actually use are insecure by design: old phones, opaque operating systems, proprietary blobs built and controlled by #dotcons. You can build the most secure system in the world, but if the people you are communicating with are using compromised devices, then your security collapses to their level.

That’s the bit people who fixate on closed don’t like to face. So a #KISS approach helps cut through the illusion – At normal use, there is very little real security. At paranoid levels, security breaks down socially, because you still need to interact with people operating at the normal level. That doesn’t mean security doesn’t matter. It means we need to stop pretending it technically works in isolation from social reality.

Why closed paths, spaces and projects fail socially, is a harder point. Closed systems are often justified in the name of security, privacy, or control, but socially, they create a very different dynamic in that they remove visibility. And without visibility, you cannot form shared judgment, without shared judgment, you cannot have social truth. In closed environments, bad actors – call them “monsters” if you like – can manipulate, divide, coordinate in the dark to avoid accountability, because there is no wider context to test what is happening.

In open systems, the same actors exist, but they are much easier to see, challenge, and trip up, because conversations are visible, processes are transparent and history is accessible. Closed breeds monsters, open pushes them out of the light and into the shadows. This is why, for the #openweb, “closed” should be deliberately limited and clearly bounded, not expanded as a default.

There is a very real social problem on this with #Encryptionism, as a social project as it is where meany parts of the #FOSS world go wrong. There is a strong tendency – what we call the #encryptionists – to treat encryption as a kind of universal solution, were in reality, this to often becomes: a focus on abstract technical purity, a dismissal of messy social reality to retreat into systems that don’t scale socially. And too often, aligns – ironically – with the same #deathcult logic it claims to resist: control, fear, and abstraction over lived practice. Encryption is a tool, not a culture.

This brings up the #Geekproblem – put simply – The people building the tools often cannot see the social problems those tools create. Even when those problems are pointed out repeatedly, over years, with real-world examples, the response is often negative and #blocking – to retreat into technical framing, to rephrase the issue in jargon, to build another “better” tool that misses the point.

A useful way to explain this to the #FOSS crew is yes, jargon can be messy, but this is not just about language. The deeper issue is cultural blindness, lets look at a concrete example that might help in bridging: #Indymedia was a ten-year working global experiment in open publishing and #4opens practice. And, yes, it ran into exactly these tensions, in the UK, the project fractured along three lines:

  • #Encryptionists – blocking aggregation due to abstract security concerns
  • #Fashernistas – pushing shiny but incompatible “better” solutions
  • #Openweb practitioners – arguing for simple, interoperable approaches (like #RSS)

Instead of adopting existing standards like RSS, parts of the project built new, incompatible formats, “better” on paper, but useless in practice. The result? Fragmentation, internal conflict, loss of interoperability, eventual collapse. All three sides lost. This pattern should feel familiar, you can still see it today in parts of the Fediverse.

The practical path forward, starts with taking this history seriously, then a few things become clear, that closed should be minimal and purposeful, not the default. Open processes (#4opens) are the only scalable form of trust, interoperability beats cleverness, social reality matters more than technical purity. And most importantly we need to design for the world as it is, not the world we only wish existed.

One Foot In, One Foot Out. Right now, most people are still inside the #dotcons. So the path forward isn’t purity, it’s transition. The approach we are taking with #OMN, it is simple, install and configure usable #openweb tools, make them accessible, let people use them alongside existing platforms to support a gradual #walkaway culture. One foot in. One foot out. If enough people take that step, the balance shifts.

But to take this step we need to compost the closed, we don’t need to destroy everything that exists, we need to compost it. Take what works, turn over what doesn’t, to grow something better from the remains. That means being honest about the limits of security, about the dangers of closed systems and about the cultural blind spots in #FOSS. If we can do that, we have a chance to build an #openweb that actually works.

If we can’t, we will keep repeating the same failures – just with better code.

The Tech “Empiricism” Problem

A recent essay on deadSimpleTech makes a point the #openweb community should hear: the biggest problem in technology is not only the tools, it’s also the culture behind them. For years the tech world has operated under a form of narrow “tech empiricism”: the belief that if something produces results quickly, then it must be working well. In this mindset, success is measured by novelty, speed of production, and the ability to create something new. The heroes of this culture are disruptors and iconoclasts who ship fast and build shiny things that capture #fashionista attention.

But this basic #geekproblem ignores a simple #KISS truth: technology only has meaning inside the culture that builds and maintains it. And this is where the real problem begins. In the dominant tech worldview, the culture rewards novelty, disruption, rapid production, and personal prestige. Inside this environment of #deathcult worship, producing new code becomes a way to gain status among peers. Shipping quickly matters more than maintaining systems or improving what already exists.

But there is another culture that exists alongside this, the culture of engineering and maintenance. In fields like civil engineering or infrastructure design, the heroes are not disruptors. They are the people who quietly maintain systems, improve reliability, and prevent failures. The emphasis is on responsibility, long-term stability, and care for systems people depend on. This difference in culture matters enormously. Because what counts as something working “well” depends entirely on what the culture values.

From the perspective of blinded tech culture, a tool that generates lots of new code and features appears incredibly successful. But from the perspective of infrastructure and engineering culture, that same tool may look deeply flawed – even dangerous. Real systems require debugging, maintenance, testing, and institutional memory. Most importantly, they require people who accept responsibility when things fail.

In mature systems, the first prototype is only the beginning. The real work comes later: years of maintenance, improvement, and adaptation. Yet this long-term work is largely invisible in tech culture and funding systems, which celebrate the person who creates something new but rarely honour the people who keep it running. This cultural blindness leads to fragile systems and recurring cycles of hype and #techshit to compost.

The same problem is in the #OpenWeb. Unfortunately, this problem is not limited to Silicon Valley, it also appears inside the #openweb, #NGO, and #FOSS ecosystems. Many conversations focus almost entirely on: code, protocols, scaling, features and UX. All of these are important, but without balance they are not enough to sustain a functioning ecosystem.

Without the native social culture that originally shaped the open web, open technology slowly drifts toward the dominant norms of the wider #dotcons tech industry of status competition, short-term innovation cycles, neglect of maintenance and eventual capture by institutions or corporations. This is one reason so many promising #openweb projects stagnate or collapse.

The technology works, but the social infrastructure fails. It’s in part why the #OMN exists as a project. This is the gap we need to address, not primarily as technical project. Most of the protocols and software already exist. What is missing is the social infrastructure that allows them to function as a public commons. Instead of focusing only on building new non-native platforms, the #OMN focuses on growing the wider ecosystem around what all ready works.

This means recognising that the real value of a network comes from the people who maintain it, moderate it and build communities around it – not just from the code itself.

From tech “empiricism” to social infrastructure, if we want the #openweb reboot to succeed, we need to move beyond the narrow mindset that treats technology as purely technical. The lesson from history is simple, code builds systems, culture makes them work. Without a healthy culture, even the best open technologies will eventually fail or be captured by more powerful institutions.

A deeper mess is “The End of Theory”, tech empiricism problem is really the #geekproblem amplified by ideas like this, the claim that massive data sets make traditional scientific thinking unnecessary. This idea, popularised by Chris Anderson, suggests that with enough data we no longer need theories, models, or human understanding. But this is a dangerously narrow view as large data models are epistemologically weaker than scientific theories. They can recognise patterns, but they do not understand them.

This becomes even more problematic in the age of opaque and unexplainable #AI systems. Deep learning models can be efficient at pattern recognition, but they lack human comprehension and produce opaque but believable outputs. At the same time, the increasing “datafication” of society means that communication and public life on the #dotcons platforms are moderated by these same algorithms. These systems prioritise engagement and behavioural prediction over needed values like: accuracy, truth, democratic deliberation. The result is a social environment driven by metrics rather than meaning.

It is past time to compost the mess as it is becoming easier and easier to see. But seeing the problem is only the first step. The next step is to compost it – to take the failures of the current system and use them as nutrients for something better. The future of the #openweb will not be decided by better code alone. It will be decided by whether we build the social infrastructure to support it. That is the work the #OMN is trying to grow.

If this work matters to you, help support it.

Thinking of workshops to run at “Nodes On A Web” #NOAW unconference

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 01

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:

  • 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 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 02

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.

Workshop 03

https://hamishcampbell.com/the-wall-of-funding-silence/ I am going to “Nodes On A Web” #NOAW to try and have this conversation in a polite way.

Public Money, Public Communication, Public Infrastructure

Public institutions are funded by taxpayers. Their role is to serve the public. So it should be obvious that their communication systems are open, accessible, and accountable to everyone -without requiring people to sign up to proprietary, for-profit platforms.

Yet this is not the world we live in. Today, much of public communication is effectively outsourced to the #dotcons. If you want to follow government updates, participate in consultations, or even access timely public information, you are often expected to create an account on a closed platform – designed for profit, data extraction, and behavioural manipulation. That alone should raise serious questions.

This contradiction is especially stark in Europe as they regularly speak about digital sovereignty, data protection and public accountability. And yet, at the same time, they rely on U.S.-based corporate platforms to communicate with their own citizens. It’s a strange situation:

  • Public institutions, funded by European taxpayers, using foreign, proprietary infrastructure to mediate public communication.
  • Not only does this create dependency, it also places public discourse inside systems that are not governed by public interest.
  • It’s not just ironic. It’s structurally broken, we should think about prosicuting the people who have made this happen.

The access problem, useing closed platforms to access public communication creates real barriers: Not everyone wants to create or maintain dotcons social media accounts. Some people are excluded for ethical, political, or practical reasons. Algorithms decide what is seen and what is not. Public information becomes entangled with advertising and engagement metrics. This undermines a basic democratic principle that public communication should be universally accessible, without conditions.

We already have an alternative to this curupt mess, the #DIY #OpenWeb comes from europe, it offers a different path. Instead of #closedweb platform dependency, it builds on open standards, interoperable systems with multiple access points, no user lock-in. This is not a new path, it is how the web was originally created to work in the EU.

An example project that contines this native mission and supports this is the #OMN whitch creates spaces where public institutions and public communities can meet on equal terms, without one dominating the other, and without relying on closed corporate systems. If institutions instead invest in and support the wider #OMN ecosystem, they help build something fundamentally different, a public communication infrastructure that is open by default, accessible to all, resilient and distributed and aligned with democratic values.

A simple principle, if it is funded by the public, it should be accessible to the public – without restriction. No accounts required, no platform dependency and no hidden gatekeepers.

We need to organise a call to act. Public institutions need to move beyond simply using the #Fediverse. They need to help build and sustain the commons that makes open communication possible. That means, supporting open infrastructure projects, funding shared ecosystems like the #OMN and building real, not facke PR commitment to public-first communication practices.

This is not just a technical shift, it is a political and cultural choice.

A simple #KISS way forward is to shift public social communication onto the #Fediverse. This is already a significant improvement on current platform dependency. However, I want to raise a point that may sound controversial at first, but is actually quite practical: public institutions should not rely exclusively on the existing codebases.

Most current Fediverse platforms have done vital groundwork – particularly in establishing shared protocols, interoperability, and a working culture of federation. That contribution is important and should be recognised. However, many of these tools evolved shaped by the same assumptions as #dotcons and constrained by #NGO project models. As a result, they can be complex, difficult to maintain, and not always well aligned with the long-term needs of public institutions or commons-based infrastructure.

A constructive path forward would be to fund the development of a small number of new, purpose-built codebases focused on commons publishing. Not one, but three parallel implementations.

Why three? Because diversity reduces risk. In practice, not every project will succeed – this is normal and expected. Funding multiple approaches ensures resilience, encourages innovation, and avoids over-reliance on a single solution. The cost of doing this would be minimal relative to existing public digital budgets, yet the potential long-term value is significant.

Importantly, this is not about replacing the existing ecosystem. Because the Fediverse is built on shared protocols, any new tools would remain fully interoperable with current platforms. This means users of existing services can still interact seamlessly, while the overall ecosystem becomes stronger, more diverse, and better aligned with public service values.

In short: build on what exists, but don’t be constrained by it. By investing modestly in new, commons-oriented infrastructure alongside the current tools, public institutions can shape a more robust, sustainable, and genuinely public digital communication space.

#KISS

Outreach to @newsmast interesting to see the #NGO view of the real alt path we need to take https://hamishcampbell.com/thinking-of-workshops-to-run-at-nodes-on-a-web-noaw-unconference/ you guys might be interested in working on the 3ed workshop outline. The 3 codebase need to be 1) mainstreaming, 2) radical #NGO and 3) native messy grassroots. You guys could be the second codebase. We do need diversity, best not to keep blindly messing up this path in the current globe mess.

Why It’s Difficult to Build the #OMN – and What We Can Do About It
Growing the #openweb – Notes for Composting the #dotcons (and growing an #OMN)

Stopped going to in-person general tech conferences around 15 years ago – they’d become beyond pointless. Since then, I’ve stuck to more focused online events.

Now heading back to an in-person one. Curious what I’ll actually find.

I have a feeling it’ll be about 75% pointless, 20% narrow geek, academic and #NGO-focused (slightly useful), and maybe 5% – probably less – actually useful.

Let’s see how that shifts after the event.

UPDATE: The event was posative, people were looking for change.

Individual fears

Individual fear scales into collective outcomes, when people act mainly from fear, they tend to choose control, isolation, and short-term protection, and those choices accumulate into worse social paths. It’s useful to frame this as the dynamic between fear/control and trust/open in #openweb thinking.

So the practical question becomes – how do we reduce fear enough that people act more cooperatively? We can try some grounded ways to make this to work.

  1. Build Real Social Support

Fear grows when people feel alone and powerless, it shrinks when people feel supported and connected. Historically, societies with strong collective structures – unions, cooperatives, community groups, local media, commons infrastructure – tend to show lower social anxiety and higher trust. What helps is strong local communities with shared institutions people actually control through mutual aid and cooperative structures. When people know others have their back, they are less likely to act defensively.

  1. Reduce Information Panic

Traditional and #dotcons media systems amplify fear, because fear drives attention and engagement. Constant exposure to crisis narratives makes people feel the world is collapsing even when their local reality may be more stable. To counter this we need slower, contextual media, local reporting and shared storytelling in flows in media systems not driven by advertising attention metrics. This is the place where the #OMN fits: if communities control their own media infrastructure, the incentives shift away from panic amplification.

  1. Increase Agency

Fear grows when people feel they cannot influence outcomes, when people have real participation in decisions, fear tends to drop and responsibility rises. So when people help shape the systems, they no longer see it purely as something happening to them.

  1. Create Stable Material Conditions

A lot of fear is simply economic insecurity, worrying about housing, food, healthcare, or work, their nervous systems remain in threat mode. In that state, cooperation becomes much harder.

  1. Encourage Contact Between Groups

Fear comes from distance and misunderstanding, interacting across social, political and cultural differences in real life, fear tends to decrease. Shared projects and cooperation help more than debate. This is why collective building projects (community media, shared infrastructure, local initiatives) can be powerful: people work together rather than just argue.

  1. Normalize Courage Instead of Panic

Fear spreads socially, but confidence spreads socially too, when people see others acting constructively – organizing, building alternatives, cooperating – it changes what feels possible. Visible examples of working alternatives matter because they shift the emotional landscape from “Everything is collapsing.” to “We can actually build something better.”

The idea we need to balance is fear itself is not the enemy, in moderation it is a normal protective response. The problem comes when systems, like much of today’s personal and social mess exploit fear to maintain control. When that happens, fear multiplies and becomes self-reinforcing. Reducing fear at scale usually requires: stronger communities, trustworthy “native” institutions using #4opens communication to drive real participation in building visible alternatives.

In short: build systems that reward trust instead of systems that profit from fear. That is one reason projects like #openweb infrastructure of the #OMN matter. They are not just technical tools, they are about building communication spaces that encourage cooperation instead of panic.

#KISS

So how do we mediate this fear?

Why It’s Difficult to Build the #OMN – and What We Can Do About It

One of the biggest barriers to building projects like the #OMN (Open Media Network) is not technical – it is structural – how resources are distributed in our society. Under capitalism, the driving force behind what gets built and what counts as “innovation” is profit. Investment flows toward projects that promise financial returns. Venture capital, grants, and corporate funding all operate under this logic: if a project can generate profit, scale, or market dominance, it is considered worthy of investment. If it cannot do those things, it does not get funded.

This creates a deep distortion in what kinds of technology and social infrastructure actually get built. Projects that could save lives, strengthen communities, or benefit wider society struggle to find any resources simply because they do not generate profit. We can see this clearly in the digital world. Billions flow into speculative technologies, advertising systems, surveillance platforms, and financial schemes. Meanwhile, the basic tools people need for public communication, community coordination, and independent media remain fragile and under-resourced.

The result is the landscape we now call the #dotcons: platforms that monetize our attention, harvest our data, and shape public conversation for the benefit of a handful of corporations and shareholders.

A different motivation? The native Fediverse and projects like the #OMN are built from a completely different starting point. Not designed to extract profit or built encloser. And not driven by the logic of venture capital. Instead, at best they grow from a humanist motivation: the desire to build social meaning and meet simple human needs. The goal is to improve the quality of life in general by supporting open publishing, shared media infrastructure, and grassroots communication. These are the kinds of tools we need to help communities tell their own stories, organise collectively, and respond to crises.

In this sense, the #OMN sits firmly in the tradition of the #openweb and projects like #indymedia. The technology exists, the cultural knowledge exists, what is missing is not possibility, but resources. Because the #OMN does not promise financial returns, it sits outside the normal funding pipelines. Venture capital has no interest, corporate sponsors want control, institutional funding comes with strings attached that reshape projects into something “safer” and less disruptive.

Over the past decades we have also seen how #NGO funding models neutralize grassroots initiatives, the original goals become softened, the governance shifts upward, and projects become professionalized to the point where they lose the communities they were meant to serve. So the challenge becomes very simple, but very real how do we resource projects that are built for social value rather than profit? This is the core difficulty in building the #OMN.

It is not that people disagree with the idea, in fact, many people recognise the need for open, public-first media infrastructure. The difficulty lies in finding ways to support that work outside the normal profit-driven economy.

Growing from seeds – the good news is that the #OMN does not need to start big. Many of the most important pieces of the #openweb have always grown from small seeds: communities, volunteer effort, shared infrastructure, and trust networks. The #Fediverse itself is proof that distributed systems can grow organically when people care enough to build and maintain them.

The aim is not to replace the existing system overnight. It is to grow an alternative ecosystem alongside it, rooted in openness, collaboration, and public benefit. This means building slowly, sharing knowledge, and keeping the processes transparent and simple. The #4opens principles remain a useful guide: open data, open source, open standards, and open process.

What you can do – if the #OMN is going to exist – it will exist because people decide it should. There are a few practical ways to help make that happen:

  1. Support the project financially. Even small recurring contributions make a difference when building shared infrastructure https://opencollective.com/open-media-network
  2. Contribute skills and development. Developers, designers, writers, organisers, and testers are all needed to grow the network.
  3. Use and experiment with the tools. Real projects and real communities are what give infrastructure meaning.
  4. Share the ideas. Talk about the need for public-first media systems and the problems with the current #dotcons landscape.
  5. Help build the culture. Technology alone is not enough. The #OMN depends on the social culture of the #openweb: cooperation, trust, and collective responsibility.

This is a #KISS path to building the world we need. The current system directs enormous resources toward technologies that extract value rather than create it. That is not inevitable, it is simply how our economic structures currently allocate attention and funding.

The #OMN represents a small but practical step to build something different, not a platform empire, or another startup. Just a shared piece of public media infrastructure, grown from the grassroots, and built to serve the people who use it. If that sounds like a world worth building, you can help make it real: https://opencollective.com/open-media-network

It’s not easy, and it’s not as simple as clicking “sign up” and walking into a ready-made community