OMN: Broken Institutions, and the Need to Rebuild the Commons

For progressive and radical people, one of the central political questions of our time is simple to ask but hard to answer – Why is it so difficult to rebuild the institutions that were destroyed in our #deathcult worship of the 1980s and 1990s? And more importantly why does the impossibility of rebuilding them make it so hard to change the needed balance of power in society? These question matters for working on the future of the society and most importantly the grassroots part of this: #openweb, grassroots media, and projects like #OMN.

The hollowing out of institutions, in the 20th century, politics used to be deeply institutional. People didn’t just express opinions, they joined organisations. If you marched in a protest, we usually marched as a member of something: a trade union, a political party, a civil rights organisation or community association. These organisations formed the infrastructure of democracy, connecting everyday anger and hope to real power.

But beginning in the 1980s and 1990s, much of this infrastructure was deliberately dismantled. Union power was broken, mass political parties were hollowed out, and community organisations lost resources and influence. The result is the political landscape we inherit, a society with political anger but without any working political structures.

Today we live in what #fashionistas and academics call #hyperpolitics or what I call #stupidindividualism in the hashtag story. Yes, some people are more politically engaged than they were in the 1990s or early 2000s: More fluffy protests, #dotcons online political discussion. But this engagement is almost all unstructured in the old sense.

Millions may join a protest or share a political message in the #dotcons, yet very little, if any lasting organisation emerges from this. This surface engagement creates a strange paradox of huge drifting mobilisations leading to very little structural change. We can have the largest protests in history – yet the underlying power structures remain completely untouched.

Closed #dotcons social media lowered the cost of expression, but algorithmically shaped it into smoke and mirrors. Let’s take a moment to lift the lid on this #tecsit mess. The role of media in this is complex, on the positive side, #closedweb platforms drastically reduced the cost of political expression.

Forty years ago, if you wanted to express a political opinion publicly you needed a newspaper, radio station, a public meeting or to stand in a square shouting. Now you can reach thousands of people instantly. But there is a downside that #dotcons smoke and mirror online engagement replaces the slow work of institution-building. Posting, sharing, and reacting can feel like participation, but it has very little role in building the durable structures needed for any long-term change.

So why do the current hard right succeed without institutions? There is an uncomfortable asymmetry between left and right. The right can carry out its agenda without building mass organisations, because it relys on: existing elitist power structures, wealthy donors, state institutions and traditional corporate media.

The left cannot rely on these, historically the left needed mass organisations because its power came from collective action – workers, communities, movements. Without those structures, left politics becomes, mess, fragmented and reactive. This is why protest waves can be enormous but still fail to shift any real policy.

The #undeadleft problem is where vertical left respond to this crisis with nostalgia, there imagination stops at rebuilding the mass political parties and institutions of the 20th century. But this is to often like trying to animate a corpse, even if you could recreate it, the environment has changed so much that it wouldn’t survive.

At the same time, the opposite response – abandoning institutions entirely to relying purely on digital networks – also fails. Purely online movements often dissolve as quickly as they form. We need a #DIY hybrid path based on federated #4opens institutions like the tools we are building and rebooting with the #OMN projects.

Not rigid old institutions, not purely online networks, But something that seeds the in between. The goal is not to create another platform, it is to expand #federated #p2p infrastructure for collective media and collective politics. The original #openweb worked because it supported networks of communities, independent publishers and grassroots movements. The corporate #dotcons replaced this with extractive platforms designed for profit and control.

KISS rebuilding the commons means rebuilding the social infrastructure of media, not just tools, but institutions and practices that persist to allow collective voices to organise and persist.

The simple truth, if we want real political change, we cannot rely on viral posts, temporary movements or algorithmic attention. We need structures that last, connect people, that can turn energy into horizontal power. That work is slow, messy, and unfashionable, but like digging compost for a garden, it’s the only way anything grows.

A path to start to compost this #techshit is growing horizontal tools from the Fediverse for real change (#OMN).

If the problem of our time is political energy without institutions, then the opportunity is clear:
build new institutions native to the #openweb. Not simply recreate the rigid organisations of the 20th century, and not fall into the hollow performative politics of the #dotcons. Instead, we grow native horizontal digital tools to help people organise, coordinate, and act collectively. This is where the Fediverse and projects like #OMN matter.

The #Fediverse already proves that distributed infrastructure works. But right now it is mostly used for conversation. If we want meaningful change and challenge, we need to extend it into practical coordination and collective action. by build tools for organising, not just talking

Current social media tools are built for attention and engagement, not organisation. What we need to add to the mix is simple #4opens tools that help people form groups, coordinate action, share resources, document activity and most importantly maintain continuity over time (#makinghistory). The Fediverse already has #fashionista and #geekproblem pieces of this:

Mastodon / Pleroma → conversation

Mobilizon → events and gatherings

PeerTube → video publishing

PixelFed → visual storytelling

Lemmy / Kbin → community forums

These existing pieces can become seeds to be woven together into workflows for collective action. On this path we need to remember the goal is not more platforms, it’s practical ecosystems. For this to work a first step is rebuilding commons-based media. A core idea behind #OMN is returning to something like the #Indymedia publishing model, but rebuilt using modern federated tools. Instead of a single website, imagine distributed publishing nodes where local groups post reports, media is shared across networks, discussions happen across servers and archives remain accessible and most importantly meaningful.

This builds collective memory, something the algorithmic feeds of the #dotcons constantly destroy. Movements need memory to learn.

#makinghistory is the same code-base as this grassroots media project

One reason mass organisations collapsed is that participation became too heavy, people don’t want to “join a church” politically any more. So tools should allow different levels of engagement: casual participation, occasional contribution, active organising with core stewardship. The Fediverse naturally supports this because it allows loose affiliation rather than rigid membership. You don’t need permission from a central authority to participate.

Focus on infrastructure, not branding. A common #NGO trap in activist tech is building new branded platforms that compete with existing networks. That approach usually fails. The better path is infrastructure building based on protocols instead of platforms for #4opens interoperability instead of silos, tools that connect existing communities. This was the original power of the #openweb, protocols scale. Platforms capture.

Keep the tech simple (#KISS), as the biggest barrier to grassroots technology is complexity. Many promising projects fail because they become too technical for real communities to use. So the rule should always be KISS – Keep It Simple, Stupid. Tools should be installable easily, understandable by non-geeks and maintainable by small communities to grow resilience without large funding. If only developers can run the system, it will never become a movement infrastructure.

Compost the failures (#techshit). Another key idea is recognising that the tech world constantly churns useful waste. Old tools, failed platforms, abandoned code, all of this is #techshit that can be composted instead of chasing fashionable new tech, we reuse working ideas, simplify existing tools to combine proven approaches. The #openweb already solved many of these problems decades ago. Sometimes progress means going back to what worked.

Build trust networks, as the most important layer isn’t technical – it’s social. Horizontal networks only function when there is trust and shared culture. The Fediverse works because communities can federate with trusted peers, block hostile actors, build local norms. This allows networks to remain open but resilient. The challenge is nurturing communities of practice around the tools.

Grow slowly and organically, movements that scale too quickly often collapse. The better model is ecological growth with small nodes → connected networks → resilient ecosystems. Just like compost turning into soil. The goal is not explosive growth, its sustainable infrastructure for collective action.

The real challenge is the biggest obstacle isn’t technology, it’s the #geekproblem – the gap between technical culture and social reality. Too many tech projects assume that better tools automatically produce social change, but tools only matter when they are embedded in real communities and struggles. The work of projects like #OMN is bridging that gap.

Shovels, not silver bullets, we don’t need magic platforms, we need shovels, tools that help people dig, build, connect, and organise together on the native #openweb. If we can do that, the Fediverse becomes more than an alternative social network, it becomes infrastructure for democratic power.

What projects like #OMN can learn from history

Europe, the Fediverse, and the story we failed to tell

A bunch of native #openweb people spent real time, energy, and focus pushing the #EU toward the #Fediverse. This wasn’t theoretical, it wasn’t speculative, it wasn’t a #NGO whitepaper or a #VC funding pitch. It was practical outreach, grounded in working technology and lived experience, aimed at reducing Europe’s dependency on centralized corporate platforms.

One concrete moment of this work was the webinar organised between the European Commission and the ActivityPub community: https://socialhub.activitypub.rocks/t/webinar-with-the-european-commission-and-ap-community/1507

The webinars mattered, they demonstrated that EU institutions were genuinely open to #ActivityPub as a viable public infrastructure standard, not as a niche hobby project, but as a way to regain institutional and civic agency without defaulting to US-based platforms.

This is the work we needed more of, but this kind of engagement is slow, unglamorous, and politically awkward. It doesn’t fit VC startup narratives or revolutionary aesthetics. But it is the work required if Europe wants digital sovereignty without surrendering to #BigTech or reinventing the same centralized failures under an #EU flag.

So the obvious question is: what went wrong? Drift, fragmentation, and the return of the #dotcons. Instead of consolidating that momentum, the grassroots fractured, attention drifted, energy leaked away, people burned out or moved on. In the end, outreach was blocked from both sides

And then slowly, predictably, attention returned to the familiar #dotcons, because they are easy, visible, and culturally dominant. They offer the illusion of reach without the substance of agency, in the long run, this is just more #techshit to compost later.

#SocialHub itself documents much of this history. The discussions are there, the threads exist, the intent is visible. But there is little aggregation, little synthesis, and almost no narrative continuity. For anyone not already embedded, it’s hard to see what mattered, what succeeded, and what was quietly blocked or abandoned.

The missing piece is our own history – this is the core failure – we are very bad at telling our own history, this thread says it plainly: https://socialhub.activitypub.rocks/t/eu-outreach-if-we-dont-tell-our-story-am-not-sure-who-will/2950

Because we didn’t document, curate, and repeat this story, the same myths keep resurfacing:

“The EU was never interested.”

“Federation can’t work at institutional scale.”

“There were no serious alternatives.”

“Centralized platforms are the only realistic option.”

None of these are true – but they feel true when history is missing. When people don’t know that EU–Fediverse outreach already happened, when they don’t know that viable alternatives already exist, when they don’t know that these paths were actively neglected rather than disproven.

Then people fall – again and again – for the #dotcons mess, believing it’s the only possible future. This matters now, as focus shifts back to tech change, and is exactly why #OMN, #indymediaback, #makinghistory, and #OGB exist, not as competing platforms, not as replacements for everything else, but as infrastructure for memory, communication, and accountability.

Before we argue about funding models, platforms, or scale, we need to get the ordering right:

  • History — to remember what already worked and what failed, and why
  • Media — to tell the story properly, in our own words
  • Governance — to keep power visible, contestable, and rooted in trust rather than myth

Without these, attempts at “European digital sovereignty” will reproduce the same capture dynamics under a different logo. Telling the story is political work, if we don’t tell our story, someone else will, and it won’t be told in our interests. It will be told as inevitability, as market logic, as “there was no alternative.” That story always ends the same way: more centralization, more dependency, more enclosure – followed by another round of cleanup and composting.

We already did part of the hard work, we opened doors, we proved viability. What’s missing is not only technology – it’s memory, narrative, and continuity. Until we fix that, Europe will keep mistaking amnesia for realism, and surrender for pragmatism.

Examples of the problem we need to compost

In #openweb tech, these people are the problem not the solution https://freeourfeeds.com/whoweare

This is spoiler incompetent #techshit and likely funding mess we need to ignore https://cybernews.com/tech/europe-social-media-w/ Then compost.

Diversity is good, but this is a prat move https://www.modalfoundation.org/ the are quite a few of these.

Progressive Mainstreaming

Most progressive #mainstreaming isn’t about ending the #deathcult – it’s about making its worship feel more fair, more inclusive, more polite. There is some real everyday value in this. Fewer people get crushed immediately, some suffering is reduced, that matters.

But let’s be honest about what it does not do, it does not get people off their knees to challenge the altar to stop the sacrifice. It rearranges the seating in the temple, feeding the deeper problem, obedience. Progressive mainstreaming accepts the frame, accepts the metrics, accepts the economy of extraction and then argues about distribution. It negotiates better terms with a machine that is killing us. That is not transformation, it’s managed decline.

The project of real change and challenge – the work the #OMN exists for – starts somewhere else entirely. It starts with people standing up and walking away. Walking out of the temple of the #deathcult we all live in, not in purity, utopia or comfort. But into mess, cooperation, unfinished tools, shared risk, and actual agency. This isn’t about better policies inside the system. It’s about building outside it, under it, alongside it – until the system hollowed itself out and no longer matters.

It’s about people picking up shovels, composting the wreckage, and growing something that can actually sustain life. This is simplicity #KISS #OMN

We have already seen the failures: lived through #Indymedia, the #NGO turn, the #dotcons capture, the #Fediverse repeating old mistakes. When we talk about #OMN, we’re trying to stop people from re-learning the same lessons by losing again. Silence would be complicity.

The #OMN is where critique becomes agency. It’s not about “promoting a project”, if we don’t talk about this without something like #OMN, critique collapses into doom, aesthetics, or personal exits. #OMN is a way to, act collectively, without lying about power, money, or governance.

Forgetting is how capture happens, the moment people stop naming alternatives, the space fills with managerial language, funding logic, and fear-based control. We talk about #OMN to keep the space open enough for something human to grow.

The #OMN is a path that resists #stupidindividualism, where most contemporary “solutions” reinforce isolation, personal brands, and individual safety strategies. #OMN starts from the assumption that survival and meaning are collective. We need to keep talking about this because almost nobody else does.

It’s unfinished – and that matters. It’s not about defending a polished system, instead, it’s about holding open a process. Talking about #OMN is how we invite others into the compost rather than presenting them with a finished product to consume.

We talk about #OMN because it’s a native way of saying: “We don’t have to repeat this. We can build differently, together, if we remember what already worked.”*

It’s not evangelism, it’s stewardship.

A few of us have been working on real, positive, horizontal social and technological solutions for over twenty years. Not hypotheticals, not vibes, things that actually work.

We know they work locally, we know they work socially. And after more than a decade building on the #fediverse, we know they can work in tech, at scale without going vertical, corporate, or authoritarian.

This isn’t speculative any more. Our creative task now – the #nothingnew work – is simply to combine what already works: Horizontal social practice, federated #openweb tech, trust-based governance. We already have a slate of projects waiting to be built: #OMN, #OGB, #indymediaback and #makinghistory. What’s missing is not ideas, it is people willing to show up and implement.

And here’s the hard truth: every time we try to talk about radical or progressive language, power, or structure, people retreat into #blocking and ignoring. The same unresolved tensions get replayed endlessly, nothing is mediated, nothing is grounded. Bad will accumulates, the social commons rots.

This rot isn’t accidental – it’s structural – To work our way out of this mess, we need both #fluff and #spiky. We need broad categories to think clearly, the #mainstreaming #fashernista rejection of this isn’t sophistication – it’s submission. It’s a soft, polite form of #deathcult worship.

You don’t dismantle a #deathcult by being nicer to it, you dismantle it by stopping your participation and building something better.

So this is the question, not rhetorical, not theoretical: Are you going to help make this happen? Are you going to pick up a shovel? Or are you going to stay on your knees, arguing about tone while the ground burns?

Conversations on Compost, Bridges, and the Future

A few recent conversations remind me: we’ve already done the work of building alternatives. Twenty years of grassroots tech, radical process, and messy social organizing. The trouble is, that soil has been hollowed out, scattered, exhausted, and feed into the #dotcons

Our current mission isn’t to “start from scratch,” but to rebuild bridges, spread compost, and replenish the soil. That’s why I keep coming back to this moment, the bridging of the #openweb back into #mainstream via #ActivityPub. This is a rare window, let’s not waste it.

The #SocialWebFoundation (#SWF) and others organizing around this space need to think hard about where the bridges land. If we build only toward control, influence, and safety, we miss the point. The #Fediverse wasn’t meant to become a “cleaned-up Twitter clone.” That path leads us back to enclosure.

We need to keep the messy stuff alive, the radical roots, the collective compost piles, the experiments. Because if our worlds keep shrinking, if we make everything tidy and branded, we lose the alternatives that might save us in an age of #climatechaos and hard-right acceleration.

And yes, some of them do understand, the #nastyfew they ran the numbers, and concluded they don’t have to care. In their calculus, the collapse is survivable (for them). The rest of us? We’re disposable. We need different maths, rooted in care, commons, and continuity.

Personally, I’m tired, I no longer have the energy to push these projects alone. So, the next step? Abstract the flows, share the compost, and hand the maps to the next generation. I’m still here to mentor. Still sailing, thinking of writing a book to document the 40+ years of practice that shaped this works

If you want to help build something that actually matters, not just another platform, but commons, the tools are here. The ideas are ripe. The soil can be restored. Let’s keep building, linking, and #makinghistory.

What should be closed? And what should never be?

We need a better conversation about ideology, sociology, and the #openweb. A good place to start is with a basic liberal framework: “Most social interactions should happen in the open. Some personal interactions should remain private.” Seems reasonable, right? That’s the position many of us think we agree on. Yet when we look at how our technology, and by extension, our society, is being built, that balance is totally out of whack. Today, more and more of life is CLOSED:

Closed apps.

Closed data.

Closed social groups.

Closed algorithms.

Closed hardware.

Closed governance.

And on the flip side, the things that should be protected, our intimate conversations, our location, our health data, are often wide open to surveillance capitalism and state control. What the current “common sense” dogma gets wrong? What is missing from the #mainstreaming tech culture, privacy absolutists, and many crypto/anarchist types:

Almost all good social power comes from OPEN.
Most social evils take root in CLOSED spaces.

When people organize together in the open, they create commons, accountability, and momentum. They make movements. When decisions are made behind closed doors, they breed conspiracy, hierarchy, abuse, and alienation.

It’s not just about what is open or closed, it’s about who controls the boundary, and what happens on each side. If we close everything… If we follow the logic of total lockdown, of defaulting to encryption, of mistrust-by-design… then what we’re left with is only the closed. This leads to a brutal truth, the powers that dominate in closed systems are rarely the good ones. Secrecy benefits the powerful far more than the powerless. Always has.

So when we let the #openweb collapse and treat it as naive, we’re not protecting ourselves. We’re giving up the last space where power might be accountable, where ideas might circulate freely, where we might build something together.

We can find examples of when openness was lost. Let’s talk about a real-world case of #Diaspora vs. #RSS. 15 years ago, Diaspora emerged with crypto-anarchist hype as the alternative to Facebook. It was secure, decentralized, and… mostly closed. It emphasized encryption and privacy, but lacked network effects, openness, and simple flows of information.

In the same era, we already had #RSS, a beautifully open, #KISS decentralized protocol. It powered blogs, podcasts, news aggregators, without permission or centralized control. But the “Young #fashionistas ” of the scene shouted down RSS as old, irrelevant, and too “open.” They wanted to start fresh, with new protocols, new silos, new power. They abandoned the working #openweb to build “secure” ghost towns.

Fast-forward a decade, and now we’re rebuilding in the Fediverse with RSS+ as #ActivityPub. The same functionality. The same ideals, just more code and more complexity. That 10-year gap is damage caused by the #geekproblem, the failure to build with the past, and for real people.

So what is the #geekproblem? At root, it’s a worldview issue. A failure to think about human beings in real social contexts. Geeks (broadly speaking) assume:

  • People are adversaries or threats (thus: encrypt everything),
  • Centralization is evil, but decentralization is always pure (thus: build silos of one),
  • Social complexity can be reduced to elegant protocols (thus: design first, use later).
  • But technology isn’t neutral. It reflects ideologies. And if we don’t name those ideologies, they drive the project blindly.

A place to start is to map your ideology, want to understand how you think about openness vs. closeness? Start by reflecting on where you sit ideologically, not in labels, but in instincts. A quick sketch:

Conservatism: Assumes order, tradition, and authority are necessary. Values stability, hierarchy, and often privacy.

Liberalism: Believes in open society, individual freedom, transparency, and market-based solutions.

Anarchism: Rejects imposed authority, promotes mutual aid, horizontal structures, and often radical openness.

None of these are “right,” but understanding where you lean helps clarify why you walk, build or support certain tools. And if you say you’re building tools for the #openweb, these questions matter:

Do you default to closed and secure, or open and messy?

Who do you trust with knowledge—individuals or communities?

Do you believe good things come from control, or emergence?

These are sociological questions, not just technical ones, maybe start here: https://en.wikipedia.org/wiki/Sociology and https://en.wikipedia.org/wiki/List_of_political_ideologies.

Where do we go from here? Let’s bring this back to the openweb and the projects we’re trying to build, like:

#OMN (Open Media Network)

#MakingHistory

#indymediaback

#Fediverse

#P2P tools (DAT, Nostr, SSB, etc.)

All of these projects struggle with the tension between openness and privacy, between usability and purity, between federation and anarchy. But if we start with clear values, and an honest reflection on the world we want to create, we can avoid the worst traps. Let’s say it plainly:

Not everything should be open. But if we close everything, we lose what’s worth protecting.

Let’s talk: What do you think should be closed? What must be kept open at all costs? What’s your ideological instinct, and how does it shape your view of the #openweb?


Interesting look at a #4opens project notice “”Strict scrutiny” means that any measures instituted for security must address a compelling community interest, and must be narrowly tailored to achieve that objective and no other. ” We have come a long way from this with our #encryptionsist agenders.

Capitalism is a hostage situation -Not an economy

There are meany sides to the current mess, it’s worth looking at them. An example the #mainstreaming path of paywalls stacked on paywalls isn’t any real life, it’s a trap, which we need a way out. In our everyday lives, we’ve come to accept the absurd:

  • You pay to eat food grown on land you don’t own,
  • Pay to sleep under a roof that someone profits from,
  • Pay to drink water privatized by corporations,
  • Pay to breathe, because the air is poisoned by industries that sell you both the problem and the solution.

And if you miss a payment? Game over (inspired by). That is not a functioning economy, it’s not in any way freedom, it’s a hostage situation, where every basic human need is held behind a transactional barrier, and the meter is always running.

This #deathcult is late capitalism: an endless stack of paywalls enclosing what used to be public, shared, and free. It isn’t just about money, it’s about control, dependency, and isolation. It’s a system that need to engineer artificial scarcity, so a #nastyfew can profit while the many just try to survive.

But it wasn’t always like this, for most of human history, people lived within commons-based paths, where land was collectively stewarded, food was grown and shared within communities, tools and knowledge were passed down, not patented and governance was sometimes local and participatory.

The last 200 years of “common sense” capitalism is an enclosure of these commons, first the physical ones (land, water, food), and now the digital and social ones (communication, culture, identity). The #openweb, like the open land before it, is being digitally fenced off. Platform by platform. App by app. Cookie banner by paywall.

This enclosure now defines much of our tech infrastructure, in this #mainstreaming every scroll, click, and share is now mediated by profit-driven platforms. Even activism – once vibrant and messy – is being swallowed by slick interfaces and the same throttled feeds. Resistance is filtered, shadowbanned, deboosted, and pushed to monetize. And “our” #NGOs fighting platform power… are doing so on those same platforms.

It’s an absurdity, and worse: it’s a trap. We need alternatives, real ones. We’re not going to “ethics workshop” our way out of this. We need to rebuild the tools of everyday life – economically, digitally, socially – from the grassroots up.

Commons-based systems, let’s turn some “common sense” on it head, instead of private ownership: stewardship. Instead of scarcity: abundance through sharing. This is where projects, like The Open Media Network (#OMN) come in as a practical framework for grassroots media infrastructure:

Built on the #4opens: open data, source, standards, and governance.

Designed to decentralize publishing, and return control to local communities.

Uses both client-server and P2P bridges for accessibility and resilience.

Encourages trust-based networks over extractive platforms.

OMN is not just theory, it’s active code, messy dev, and practical tools for people to tell their own stories, host their own content, and build alternative knowledge systems outside corporate media. These technologies make community hosting the default – not the exception. They reduce reliance on fragile or compromised #dotcons infrastructure. They’re imperfect, but they’re a step out of the enclosure.

The point isn’t just tech, It’s power, capitalism doesn’t only gate resources. It enforces relationships of power. That’s why rebuilding tech without addressing governance, ownership, and access won’t get us far. The #geekproblem is real: tech that nobody can use isn’t liberation, it’s just another dead-end.

The alternative? Keep it #KISS (Keep It Simple, Stupid), prioritize social usability over technical elegance, build bridges, not silos, return to shared ownership and open processes. Capitalism is a hostage situation, but we can walk out the door – if we build the exit together.

You’re not powerless, and this isn’t about purity or escape. It’s about building real infrastructure for real life, so when the capitalist system keeps crumbling (as it will), we’re not left scrambling. We’ll already be living differently.

#OMN #MakingHistory #4opens #openweb #p2p #indymediaback #geekproblem #commons #decentralize #cooperative #foss #degrowth #resilience

UPDATE the seed of this post was from a toot, but can’t find the original to link to due to the #UX of mastodon updating and no functioning search on my instance to find history, sorry, add in comments if you find the original. Updated

Real world tackling the #geekproblem

With rebooting the #openweb we run headfirst into the #geekproblem, a recurring pattern where: Technically brilliant people build powerful tools …but those tools remain socially unusable …or solve only geek problems, not the needs of actual communities. It’s not malice, often it’s idealism, but it creates a dead-end culture of endless prototypes, abandoned standards, and empty tech demos. Meanwhile, the real-world crisis deepens.

The work we need is bridges building, let’s try this ere “P2P news app” built on #dat Hypercore/Hyperswarm is exciting. Yes, it’s similar to Nostr in structure: distributed relays, client-side aggregation, unstoppable flow. But as with Nostr tech isn’t enough. We are social creatures. A usable system needs:

  • Clear use cases rooted in human relationships – not just tech possibilities.
  • User-facing front-ends that invite participation, not gate it.
  • Interoperability with existing protocols (ActivityPub, ATProto, etc.) to avoid siloing.
  • Bridges between architectures – e.g. client-server ↔ P2P – so that real-world adoption is gradual and survivable.

The good news, the wider #OMN project is already a sane path forward, with a #KISS hybrid path. The plan is in bridging #P2P and client-server as a way out of this. Something like:

A lightweight server bridge that serves data to client-server users (ActivityPub, fediverse, legacy web),

While simultaneously feeding a P2P mesh, with each peer storing and distributing redundant objects,

So that over time, client-server becomes the bootstrapping layer, and #P2P becomes the long-term archive + resistance layer.

“Data is just object flows – how the user gets the object is irrelevant technically.”

This is the kind of thinking that gets us out of the traps, by moving from protocols to people. This isn’t just about code, it’s about culture. The #geekproblem won’t be solved by more architecture diagrams, it needs movements that embrace imperfection and prioritizes social use, visible, working front-ends people can contribute to and understand, documentation and tooling that builds capacity in others, not silos around the brilliant few.

What next? For the devs:

  • Can the p2p-news-app codebase be modularized to plug into #OMN projects as a data backend, even in a basic way?
  • Can we bridge shared data objects across protocols (e.g. post metadata flows from P2P → ActivityPub), even if janky at first?
  • Can we prototype a simple but cross protocol usable frontend, the examples is the work on #makeinghistory and #indymediaback, that lets non-geeks see and touch the network they’re part of?

    Yes, for the movement, keep things messy but moving. Avoid dead ends by always asking:
"How does this empower non-technical users to organize, document, and publish together?"

Keep the tech grounded in the social fabric, the activists, journalists, organisers, and rebels this is all meant to serve. If you’re reading this and thinking, “I can help,” please step forward. There’s space in wider tech/social #OMN and #MakingHistory for everyone, coders, writers, designers, testers and storytellers.

Let’s build bridges, not silos, let’s build tools people can use, not just tools geeks can admire, let’s do this together.

Trying to Remember: A Personal Reflection on Activist Histories and Memory Holes

Looking back on the activist groups I’ve been part of over the past few decades, I find myself drawn into the messy business of memory. Not nostalgia, something more grounded than that. A desire to trace what actually happened: why things unfolded the way they did, what they meant politically and personally, and what we can still learn from them.

But this work isn’t easy. Many of the people I worked alongside carry completely different versions of events. They remember different turning points, attribute success or failure differently, or sometimes choose to forget altogether. Writing about this – even carefully – risks reopening wounds. It challenges settled myths. It can feel uncomfortable, even unkind.

So the question keeps coming back: is it worth trying? I think the answer is yes. Painful, imperfect, but necessary. As George Santayana famously wrote: “Those who forget their history are doomed to repeat it.”

And in our small corner of the world – radical media, grassroots tech, DIY networks – repetition is a real problem. The cycle of reinvention is one of the most frustrating aspects of media activism. We keep rebuilding the same tools, replaying the same conflicts, falling into familiar traps. Why? Because we don’t do history well.

More precisely, we don’t keep our history. Websites disappear, servers shut down, backups are lost, and mailing lists become unreadable. Entire communities vanish almost overnight, leaving little trace beyond broken links and half-remembered stories. The next wave arrives thinking they are starting from zero.

This amnesia isn’t accidental; it’s cultural. There’s an ingrained tendency within activism to assume: “We invented this. This is new. We’re the first.” I’ve heard this countless times from people who are thoughtful and brilliant. It’s not arrogance, it’s isolation. A lack of intergenerational knowledge transfer. The result is predictable. Each new cycle repeats the mistakes of the last, often with shinier tools and worse outcomes.

Another reason to document our own histories is simple: if we don’t, someone else will, and they may not understand what actually mattered. Academic and institutional accounts often rely on authoritative sources: funded projects, named leaders, official reports, and neat case studies. That’s understandable, but it means messy grassroots realities frequently disappear from the record.

Grassroots work rarely fits institutional narratives. It’s decentralised, anonymous, improvised, sometimes deliberately undocumented for safety or principle. Yet when official histories are written, these messy spaces are where the real change happened. In truth, many of the most effective projects I’ve been part of were born in squats, kitchens, backrooms, chaotic email threads, and improvised hacklabs. They weren’t polished; they were alive.

Take #Indymedia, I was there to helped build and maintain parts of it. It transformed online publishing and participatory journalism. For a time, it worked remarkably well, until it didn’t. Its decline wasn’t just about technical debt or burnout. We lacked strong practices for documenting process and preserving institutional memory. When fragmentation came, there was no shared record to return to, only fragments, myths, and personal recollections.

That experience is part of why I later focused on projects like #OMN (Open Media Network), alongside #indymediaback and #makinghistory. These are attempts to embed memory into infrastructure itself: to preserve process as well as outcomes, to balance individual and collective histories, and to resist co-option by institutional gatekeeping and #NGO driven narratives.

So should we document activist histories? Yes, because we keep losing what we build. Yes, because new generations deserve shoulders to stand on, not endless reinvention. And yes, because remembering is a political act.

But we need to do this carefully. With plural narratives rather than single heroes. With archives that hold disagreement instead of smoothing it away. We need to document failure alongside success, not as shame, but as compost for future growth.

And we need to stop assuming the truth will speak for itself, it won’t, we have to speak it, even when memories clash or perspectives diverge. This isn’t about gatekeeping, it’s about keeping gates open for those who come next.

If you were part of these histories, write your piece, even if it contradicts mine, especially if it does. If you’re building now, take time to look back. Find the old code, talk to the elders, search for the backups, document what you’re doing as you go.

History isn’t just the past, it’s infrastructure.

Let’s build some together.

Actors, Power, and Collective Publishing: Rethinking Fediverse Architecture for Grassroots Media

We recently had an extended and thoughtful discussion on signal between collaborators working on #IndymediaBack and #MakingHistory, a key issue emerged: how should we structure “actors” (ActivityPub identities) in a network where the focus is collective action, not individual performance? This question isn’t just technical. It’s political, and central to the success or failure of rebooting radical grassroots media within the #Fediverse.

The tension is about balancing the individual and the collective. In most current Fediverse platforms (like Mastodon or PeerTube), each user is an “actor” with their own inbox/outbox, mirroring the logic of the mainstream #socialweb where identity and expression are deeply individual. But for platforms rooted in collective publishing, such as a revived #Indymedia, this doesn’t map neatly.

“We are trying to balance individualism with collectivism. People already have all the individualism they can take, we need a structure to support the collective.”

That means maybe moving away from assuming every account needs to be a visible, subscribable actor. Working model: Per-instance actors first, a consensus is emerging around per-instance actors – e.g., the Newswire and Features flows of a local Indymedia site act as the primary publishable entities in the Fediverse. These represent the editorial collective’s curated output – not just anyone shouting into the void.

External trusted contributors (like info@hamishcampbell) would publish content from their own Fediverse accounts using hashtags like #oxfordindymedia, which the local Indymedia instance detects, vets, and republishes.

This brings three key benefits:

  • Curation over chaos – Stories don’t just flood in via hashtags; they’re filtered through trust relationships.
  • Permissioned federation – Only trusted flows (or untrusted but manually reviewed ones) are accepted. Hashtag spam is naturally blocked.
  • Maintaining editorial identity – Subscribing to an Indymedia instance means subscribing to its judgement, not just raw firehose feeds.

Do we need per-user actors? Here’s where things get messy, and interesting. Three models were debated:

  • Classic Fediverse model: Each user has their own actor. This supports full transparency and traceability of actions, but risks returning to individualist norms and opens the door to abuse or platform drift.
  • Invisible user accounts: Users exist internally for moderation or curation roles, but aren’t visible in the Fediverse as actors.
  • Controlled per-user actors: Users do have actors, but these are only used to publish activity logs, not posts. Think: “Editor X approved story Y”, useful for building transparency and trust within an open process.

Option 3 sits nicely with the principles of the #4opens, particularly open process and open governance. It provides a transparent audit trail without pushing users into the spotlight.

UX vs backend architecture, what becomes clear is that the user experience should foreground collective flows – Features, Newswire, Tags – while any per-user mechanics operate in the background, supporting moderation, traceability, or edge-case publishing. Whether those background accounts are AP actors or not might depend on implementation details.

“It’s not about the actors per se — it’s about what shows up in the front-end UX, and how we build trust in the process.”

Final considerations, networks like #IndymediaBack default to collective-first publishing, with user actor functionality off unless needed. #MakingHistory, by contrast, might enable user actor publishing to support mass collaborative storytelling. Both platforms rely on whitelist federation, meaning only trusted instances and users can feed directly into the editorial stream. Abuse prevention comes not just from code, but from the politics of moderation, curation, and shared norms.

  • We probably need per-user actors, but used sparingly and carefully.
  • We definitely need per-instance actors for trusted collective outputs.
  • Hashtags are a start, but the flow must be curated and accountable.
  • UX should put collectives front and centre, with user identity in the background.
  • This is a political choice, not just a technical one, and that’s a good thing.

For more on how this fits into the broader reboot of radical media infrastructure, see:
Rebooting Radical Media (YouTube)
Programming: Open Media Network

Building #OMN projects

Both #Indymediaback and #MakingHistory represent grassroots publishing models built around commons-based media rather than platform ownership. They differ in structure and interface, but share the same DNA: collective trust, open participation, and social moderation. The challenge – and opportunity – is to bridge these approaches, allowing interoperability while preserving their distinct paths.

#Indymediaback

Data model is the commons, most content exists as shared common’s data rather than owned posts. Authority comes from collective process rather than individual ownership.

The default core flows:

  1. Newswire (public, chronological flow). The newswire is the living river, anyone can contribute, but trusted contributors publish directly. Untrusted or unknown contributors enter moderation flow. Editorial collectives curate trusted streams feeding into the instance. Te news is chronological, raw and immediate to reflect street-level reporting. This flow priorities presence over polish – what is happening now.
  2. Features (curated layer) where features are the reservoir built from the river. Editorial collective crafts longer pieces that draw from newswire material to provide narrative framing and synthesis. This is to slow down the flow, too provide time for context and elevate significant stories. This layer introduces collective editorial voice without eliminating grassroots origin.
  3. Hidden (private moderation layer) Hidden is the dam, filtering toxic waste while preserving transparency internally by moderating untrusted content, not publicly visible unless released. This is used for spam control, conflict mediation and ethical decision-making. The goal is not censorship but collective filtering.

The default view structure is mostly fixed layout of:

  • Newswire (live stream)
  • Features (curated)
  • Hidden (private moderation)

Tags exist but are secondary. Think of a fixed landing page shaped by flows rather than algorithms.

Editorial Model is collective moderation by affinity-group consensus to build social trust through participation. Authority emerges from process, not ownership.

Core metaphor is a river feeding a reservoir, with a dam filtering toxicity.

#MakingHistory

MakingHistory evolves the model from chronological publishing toward narrative ecology.

Data Model: Fragment-first publishing. Media objects become composable fragments of text, images, video, audio with annotations. Stories emerge from assembling fragments rather than existing as single immutable posts.

Everything begins as a crafted piece, linking fragments together.

Context is explicit, when editing is iterative and collaborative.

Publishing is closer to historical archiving than newsroom reporting.

Tag-based flows are primary navigation. Rich tagging enables dynamic timelines, thematic streams and historical clustering. Instead of one homepage, many narrative paths emerge.

Moderation has a private curator layers to review, prioritise and archive. Moderation becomes gardening rather than gatekeeping.

Interface is dashboard-based with multiple parallel views and TweetDeck-style streams.

Users track themes rather than sites.

Core metaphor is a garden of stories with paths (tags) connect plots. Some bloom publicly, others compost behind the scenes.

All #OMN projects have shared DNA

Both systems treat data as commons, rely on collective moderation and maintain public/private split for trust-building. They resist corporate enclosure, support grassroots communication. Differences are primarily structural:

  • Indymedia = flow-first (timeline + editorial layer).
  • MakingHistory = narrative-first (linked stories + thematic streams).

The role of #OMN is to act as bridge infrastructure enabling interoperable flows, shared trust networks and cross-platform publishing. Through ActivityPub and #4opens principles we get transparency, participation, open standards and shared stewardship. #OMN enables federation not just technically but socially.

Open Questions (Design Challenges)

  1. Collective data ownership. Should commons data be managed through group structures? A possible model is groups hold stewardship rights, membership grants moderation/admin capabilities and legacy admin roles remain but fade into background. The goal is to shift from individual admin power → collective governance.
  2. Trust model is about trusted vs untrusted flows – what determines trust? Possible signals are group membership, instance reputation, individual history, tag-based reputation and source provenance. Trust must remain dynamic and reversible.
  3. Metadata layer becomes the backbone of federation.
  4. Every object as a wiki is a radical shift, each object has a history in this articles become evolving commons rather than static posts. A Wikipedia of news built from organic trust groups and street-level reporting. Narrative truth emerges from collective editing over time.

The deeper shift is not in just technical architecture, it is moving from publishing as broadcast → publishing as process, authority as ownership → authority as participation, fixed media → living commons. The aim is to rebuild #mainstreaming from below not more centralised media institutions. We need federated grassroots storytelling networks.

Funding Proposal: Open Media Network (#OMN) – Building Portable, Human-Centred Digital Commons

The #OMN isn’t just about media, it’s about building the social soil

We need to keep highlighting an old but still urgent tension: the intersection of technology and social change. In this too often unspoken divide, one side leans heavily on practical, technical problem-solving. They want working code, functioning systems, and tangible results, not abstract debates. To them, critiques about capitalism shaping code sound like distractions from the “real work.” The other side insists that technical problems are social problems. They argue that all code is written by people, shaped by culture, power, and history. Ignoring the social dynamics behind technology guarantees we repeat the same failures.

This divide plays out constantly in movements trying to bridge the worlds of #AltTech and social transformation. You see it in tensions between the tech-focused “geek” communities and broader #mainstreaming society. And both sides have blind spots.

The geek camp often falls into the #geekproblem: over-prioritizing tech innovation while ignoring the human and social context. Meanwhile, the #mainstreaming crowd tends to embrace vague social ideals while underestimating the soft power – and necessity – of building real technical infrastructure to support those ideals. Neither side alone can solve anything meaningful, especially not something as vast as rebooting the #openweb or to even start to touch on #climatechaos.

We need bridges, that’s what projects like the #OMN (Open Media Network), #OGB, #IndymediaBack, and #MakingHistory are about: building trust-based, grounded, people-powered platforms that can span the divide between tech and society.

But let’s be honest, there’s a lot of very bad behaviour on all sides of the #openweb reboot. Blocking progress, gatekeeping, aggression, virtue signalling… it’s all too common. Let’s try not to become prats, it’s easy to start, and hard to stop. Mess breeds more mess, prat-ish behaviour comes in waves. It aligns with waves of #mainstreaming and the reactive “alt” backlash, these tides bring a lot of flotsam, it’s up to us to shovel and compost what we can.

Our biggest block right now? The culture war postmodernist fog that has drifted through radical spaces over the past decades. It’s slippery, full of “common sense” that doesn’t hold up, but is hard to challenge because it feels “right”. Composting this will be difficult, but necessary.

The #Fediverse is built on people-to-people relationships. Trust, not just tech, is the foundation. That’s why there’s a healthy pushback against “tech fixes” that try to replace social trust, a path that is much more common in places like #Nostr and #Bluesky, where algorithms and cryptography are too often seen as the solution to everything.

Yes, in reality, we need a balance of both. The debate is fluffy in places, spiky in others. But if we build tech-bridges to span this messy social terrain, we might actually get somewhere. This brings us to the hard green question: how do you scale local, eco-conscious solutions to a disinterested – and sometimes hostile – global population? Green progressives often promote small-scale, ethical living. That’s great for the 1% who can afford to live that way. But what about the other 99%?

Let’s be blunt: some people will die from #climatechaos. Maybe 9%, maybe more. But 90% will still be here, and they will need different kinds of solutions. Right now, the options on the table look like this: A rebooted, green-infused social democracy (the old Corbyn project was an example). A slide into eco-fascism and top-down “solutions” (the Trump path). Or doing nothing, and let #climatechaos run wild (the current #mainstreaming).

One thing is likely, a wartime economy is coming within 20 years, where there’s will be little room for the last 40 years of #neoliberalism, and “soft” liberalism will likely play a secondary role at best, the political landscape is shifting fast. The new #mainstreaming question is which side will you be on?

Because we need more than clean branding and good vibes – we need bold, practical, radical action rooted in both tech and human trust. We don’t just need freedom from the state and the #dotcons – We need freedom from our own dogmas.

The #OMN isn’t just about media, it’s about building the social soil where openness can grow, thrive, and renew. We need compost, and not just as a metaphor.

Dev test work for Makinghistory application

The #makinghistory project is a decentralized, open-source archiving and storytelling network designed to preserve and amplify grassroots histories. It’s founded on the idea that history isn’t written by the winners – it’s made by those who resist, build, and care. Using digitized collections like the CampbellFamily archive as a seed, the project invites communities to reclaim their narratives through shared, federated networks. This isn’t just another data repository – it’s a living, breathing ecosystem where collective memory is gathered, enriched, and kept accessible for future generations and movements.

The application functions as a community-installable tool that allows anyone to host their own archive node. These nodes, whether local or remote, connect into a wider peer-to-peer network of storytellers, archivists, and activists. Core features include uploading and organizing digital files, enriching metadata flows, and linking material to broader narratives using human-created tags and annotations. The platform follows a participation-first path, encouraging affinity groups to contribute not just data, but context, weaving a rich web of interlinked histories.

But #makinghistory goes further than archiving. It’s a space for collaborative storytelling, publishing, and public exhibition. Its narrative layer draws from the archive to trace connections between people, places, and events, transforming scattered fragments into stories of solidarity, resistance, and change. These outputs feed both digital commons and real-world installations like the Resistance Exhibition, where history is brought to life in public, participatory spaces. This is the infrastructure for radical memory work, a composting system for movement knowledge. Developers are not just needed to build features, they’re invited to help shape the very flows and protocols that keep history in the hands of those who live it.


Developer Roadmap: #makeinghistory – Testing & Prototyping

  • Phase 1: Core Object Listing
    • Implement a single-column interface that lists objects (text, image, link).
    • Set up two test instances that can post and sync objects between them.
    • Default view lists objects by most recent. Super simple.
  • Phase 2: Hashtag Columns
    • Add support for hashtag-based columns (inspired by Mastodon’s Tweetdeck interface).
    • Reuse and adapt existing open-source implementations where possible.
  • Phase 3: Story Objects
    • Introduce a new “Story” object that composes and links existing media objects, with added narrative context.
    • These stories are published through collective/community accounts (discussion needed on access/trust models).
  • Phase 4: Federation & Flows
    • Begin mapping and testing how edits, hashtags, comments, and objects flow across federated instances.
    • Align this with the #OMN trust model and the work from the #indymediaback reboot (estimated 90% overlap).
  • User Interfaces
    • Desktop: Use a Tweetdeck-style interface, similar to Mastodon’s current layout.
    • Mobile: Build a simplified UI with a single-column scroll. Objects open fullscreen with sideways swiping (like Tusky for Mastodon).
  • Every Object
    • Has edit capabilities (if user has login/auth).
    • Editable hashtags.
    • Comment threads.
    • All changes sync across instances via federation/trust flows (option 4).

The current test interface and images will need refreshing, as they’re based on early-stage mockups. But the concept remains: keep the interface minimal, usable, and focused on narrative composting. This project is both infrastructure and imagination, grounded in the old but reaching toward the new.

These images need an update as they were based on the dev work from back in the day. This is the very basic interface for testing. The mobile user facing interface is a flick sideways basic interface.

The logic and workflow are all based on the OMN project and have likely a 90% overlap with the indymediaback project

DEV of the #OMN projects

At the core of the #makinghistory infrastructure lies the Open Media Network (#OMN) – a trust-based, human-moderated, #4opens project that offers a decentralized, federated database shared across peers. What makes the OMN unique isn’t just what it does – but what it refuses to do. Rather than chasing complexity or abstract “AI-powered” solutions, the OMN focuses on simplicity and social cohesion, using technology to support and grow human networks. Its structure is purposefully minimal, with only five essential functions:

These core functions are: Publish (to share a story as an object into a stream); Subscribe (to people, pages, groups, or subjects); Moderate (to express trust or disapproval by pushing or pulling content); Rollback (to remove content from your stream based on trust flows); and Edit (to collaboratively change metadata across federated nodes where you’re authenticated). This framework serves as the back-end engine for building a grassroots, DIY semantic web. The front-end can take many forms: city-based or subject-specific sites like a modern reboot of Indymedia, regional storytelling platforms, or thematic archives like #makinghistory. Protocols like ActivityPub form the connective tissue of this system, the plumbing.

In practice, this means people can build meaningful media spaces that reflect local struggles and solidarities without being dependent on corporate platforms or NGO gatekeeping. The data cauldron of the OMN stores the shared knowledge, and every community holds a golden ladle – a way to draw out, remix, and republish what matters to them. If you’re interested in supporting this effort financially, you can do so via Open Collective. And if you’re ready to dive deeper, we need to make this #KISS project work. Let’s build tools for memory, not marketing, infrastructure for resistance, not careerism. Let’s be #makeinghistory together, not sit bord looking at a screen.


This #OMN path is “native” built on a simple, powerful truth: “This is the Internet”:

GET
PUT
POST
DELETE
–MERGE–

These basic actions — close to the core HTTP verbs every website uses — are all you need to create, share, remix, and grow.
(From RFC 7231 and RFC 5789.)

Then you have the #4opens which are about reclaiming the grassroots social power of the web:

Open data

Open source

Open process

Open standards

No gatekeepers. No #dotcons middlemen. No closed silos. Just people, building together. This is what #openweb reboot looks like.