The EU opportunity and danger, what grassroots projects can offer

What can grassroots #openweb people actually do when the EU is building alternatives to #dotcons, but with very real risks of recreating European versions of the same problems? This is a historic moment, for the first time in decades public funding is flowing toward digital commons and infrastructure sovereignty is being taken seriously. Federated technologies like #ActivityPub are gaining traction, largely due to years of grassroots work which is leading to initiatives such as @NGICommons attempting to support open infrastructure.

But alongside this opportunity comes an obvious risk, that they replace Californian platform capitalism with European platform capitalism. The danger: is European #dotcons. Institutional “common sense” – especially when combined with bureaucracy and the #NGO class – tends to reproduce familiar patterns of projects prioritise compliance and institutions over communities. Tech governance becomes professionalised and detached from users and seed communities. Yes, open standards exist, but power centralises anyway as funding rewards scale, stability, and safety rather than needed native grassroots paths.

The result is predictable, European #dotcons. The structural problem is institutions optimise for safety when #EU funding systems are designed around risk avoidance, measurable outcomes to build controlled delivery structures. This leads to only professional actors and institutional partnerships. Grassroots projects – messy, political, horizontal – rarely fit comfortably into this narrow thinking.

So even when the intention is to “build commons,” the outcome becomes safe-looking infrastructure that lacks living social ecosystems. The commons turn into infrastructure without community, and frequently fail, leaving funding poured down the drain and more #techshit to compost.

Why grassroots counter-currents matter is that healthy technology ecosystems need tension between institutional builders for stability, grassroots radicals for innovation and activists for accountability. This balancing leads to communities and real-world grounding.

Without this tension, governance ossifies and technology becomes abstracted from users. Political imagination shrinks and becomes #blocked. Grassroots projects like #OMN represent the compost layer, the messy soil where new forms grow. Institutions rarely generate this energy themselves.

Where initiatives like #NGICommons sit is that some people inside these initiatives genuinely want openness. Much like early Google’s “don’t be evil” phase, there is still a window of possibility. This means influence is still possible and direction is not fully locked in. Individuals inside may be allies, even if institutional structures trend toward mainstreaming. The danger is not simply bad intentions, it is the structural gravity toward institutionalisation.

We need practical strategies (not just critique) to move grassroots actors to shift direction, critique alone is not enough. Practical engagement matters to frame grassroots work as ecosystem infrastructure. Don’t argue only from ideology, speak in terms institutions understand: that tech ecosystems need experimental edges as monocultures fail. We need to argue that diversity increases resilience.

Policy language travels further, when we push for small “wild funding” streams. Instead of demanding institutional transformation, push for small structural openings:

  • microgrants
  • low-bureaucracy funding
  • experimental tracks
  • funding for governance experiments, not just technical deliverables.

Small budgets can create disproportionate impact.

Promote ActivityPub + social governance together as many EU projects adopt federation technically while retaining centralised governance culturally. We need to communicate that federation without social decentralisation is fake decentralisation. This is where #OMN has strong positioning.

Build parallel legitimacy, not only opposition, as institutions might respond to working prototypes with visible communities that demonstrated outcomes. Critique alone rarely shifts funding flows. Working alternatives do.

We need to find sympathetic insiders, every institutional structure contains pragmatists, a few idealists and sometimes meany reformers. So bridge-building matters. Not everyone inside #NGICommons or EU initiatives is an opponent, some are actively trying to resist corporate capture from within.

The EU currently has three possible futures:

  • European #dotcons — platform capitalism with EU branding
  • Technocratic infrastructure without social life (#techshit to compost)
  • Living digital commons grounded in grassroots communities.

The third path requires messy activism with strong social processes (#4opens) and historical memory rooted in #openweb culture. Without pressure from the grassroots edge, institutions drift toward the first outcome by default.

The deeper insight is that grassroots movements do not need to “win” against mainstreaming. They need to remain the compost layer that keeps the ecosystem alive. That means critique combined with collaboration where possible, strong and grounded independent experimentation and most importantly refusal of capture.

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.

Why the #OMN works with #ActivityPub – And why we need a bridge to #p2p

Let’s look at this. #ActivityPub is not a product. It’s not even really a “protocol” in the narrow, rigid sense that vertical tech likes to imagine. ActivityPub is a shared vocabulary, a public language for moving meaning and connection across the #openweb. It gives you nouns and verbs, and the community defines the grammar through lived use.

This is why the #OMN works with ActivityPub, a metadata and meaning layer, not a platform, flows, not silos. ActivityPub is the widely deployed #4opens protocol that treats publishing as a flow, a conversation.

Unlike the more vertical stacks (#ATProto is a good example), ActivityPub doesn’t force a worldview. It doesn’t tell you, “this is how your network must be structured.” It doesn’t enforce hierarchy or lock you into one interpretation of identity, authority, or workflow. It’s a #KISS path – here’s a shared language, verbs for publishing and receiving, express objects, updates, relationships. The rest is up to the commons

This flexibility is exactly why the #OMN can become a part of this flow. ActivityPub, with #FAP process, is already evolving this way – not through top-down committees, but by developers and users defining new grammar for shared needs. Quote posts, permissions, object types, and many other extensions are emerging organically. This is horizontal protocol evolution, which aligns well with the #OMN path.

To mediate the #geekproblem trying to break this path. We need to say clearly why we don’t want an “ActivityPub 2.0”. A clean break is a vertical move, it reproduces the #techcurn cycle: throw away the compost, start another shiny stack, burn everything down every five years because fashion demands it. It’s the #fashernista mindset applied to protocols.

For the #OMN, we need continuity, evolving the commons, not abandoning it. ActivityPub works because it’s an accretion protocol, not a replacement protocol. We extend it, we add grammar, we build bridges, we compost the broken bits. This is the #nothingnew ethos: repair, adapt, extend, don’t rewrite reality every cycle.

This is fine up to a point, but still too much – Central points of failure – Which is fine for much of the #fediverse. But the #OMN isn’t only for well-resourced servers, it’s for change and challenge. Activists on the ground, communities without reliable hosting, people under surveillance, low-resource groups, offline-first publishing, pop-up networks, autonomous movements that cannot rely on central infrastructure.

For this layer, we need true #p2p protocols. This is where #DAT, #Hypercore, and similar tools matter – not as replacements, but as bridges. These are needed for resilient metadata flows, where stories, tags, and meaning travel across networks even when the networks are broken.

We need to understand why both matter, It’s because they do different things. ActivityPub gives us: wide distribution, discoverability, moderation structures, federation, slow-moving cultural infrastructure. We add to this what #p2p gives us: autonomy, resilience, offline survival, local-first publishing, anti-censorship pathways,

The #OMN’s job is to bridge these layers, same metadata vocabulary, same hashtag meaning system, same open processes. Two different transport layers depending on the need. Think of it like the compost metaphor: ActivityPub is the shared soil bed. #p2p is the mycelium running underneath, keeping it alive when storms hit.

This matters, we don’t want just another Fediverse, we don’t want just another p2p experiment. We need a living ecosystem that can: publish everywhere, survive disconnection, resist capture, remain open, remain public, remain messy, remain ours. ActivityPub gives us the public commons, p2p gives us the underground root network. The #OMN ties them together through shared metadata, hashtags, practices, and governance.

Compost, not silos, ecosystems, not empires. Federation on the surface, peer-to-peer underneath. This is the #OMN path.

The #OMN Path: Openness as Revolution

This is about revolution as regeneration, not only destruction. In an era built on tech dependency, revolution isn’t only about smashing the machines, it’s about liberating them. Turning tools back into commons, not commodities. It’s composting the toxic monoculture of the #dotcons into fertile ground for the #openweb to grow again. Revolution means reclaiming agency, not blindly rejecting technology, but re-rooting it into light, human-scale, transparent, and accountable relationships.

The #openweb as infrastructure for freedom, isn’t just a technical architecture, it’s a social contract. Revolution means re-establishing that contract through the #4opens. When we build networks this way, we decentralize power, not just servers. The #KISS act of publishing, federating, and remixing information freely is itself revolutionary in a world where everything is locked behind paywalls and algorithms.

Tech as commons, not commodity, We’ve learned that “innovation” under capitalism means enclosure and surveillance. Revolution in this context looks like refusal of extraction: creating cooperative infrastructures that are not driven by profit but by maintenance, care, and shared use. Think of community built #p2p mesh networks, open hardware, peer-to-peer storage, and federated #ActivityPub publishing as revolutionary paths – not add-ons, but foundations.

Cultural and cognitive shifts, shifting the cultural narrative from “user” to participant. From “consumer” to custodian. The real struggle is against the #deathcult of endless growth and the #geekproblem of technocratic detachment. It’s about re-learning how to think together, rebuilding trust, and balancing the #fluffy (care, empathy, collaboration) and the #spiky (truth, resistance, boundaries).

Direct action in the digital today looks like:

  • Practicing digital mutual aid – sharing skills, hosting, dev, and care.
  • Bridging online and offline organising, connecting digital tools to local struggles for housing, food, land, and rights etc.

Above all, any real revolutionary network – like the #OMN – has to strip away the old skins of power. No hierarchies. No hidden structures. No property games. No fetishizing of tools, status, or “official” etiquette.

If we’re building something new, we can’t carry the unconshuse ghosts of the old world with us. That means not just saying we’re open, but being #4opens. Open in decisions, and open in how decisions are made. Transparent in process, not just in outcome. Coherent theory is practice, and practice is theory.

Everyday life has to reflect the world we want to grow. That means composting the commodity mindset, no trading social trust for personal gain. It means building through shared assemblies, through community, through small and self-directing circles that stay alive to change and challenge.

The structure of the #OMN should always be simple, transparent, and direct, so that anyone can walk in, understand it, and shape it. No special knowledge required, no gatekeeping. Thousands of “unprepared” people able to join, act, and make it their own. That’s what #4opens means, a living culture of clarity and participation.

Only when a movement reflects the decentralized, self-organizing community it wants to bring into being can it avoid becoming another elitist shell, another bureaucracy pretending to be radical.

When the #OMN does its work right, it doesn’t stand above the revolution, it dissolves into it, like a thread into a healing wound, leaving behind not an organization, but a living network.

That’s the path: community, openness, trust, and the messy joy of self-organization.

The #OMN is a simple project

It can be hard explane this, as people make the needed change complex, it is not, yes, it’s messy and the are no simple answers. So a first step is composting the #techshit:

  • Raw waste → The constant flood of mainstreaming, broken promises of #dotcons, bad-faith #NGO capture, shallow “innovation theatre.” This is the smelly mess we are swimming in.
  • Shovel work → Activists and communities don’t just sit in the mess. We work to turn it over, exposing the rot, adding oxygen. This is critique, transparency, and the #4opens in action.
  • Aeration → Sunlight + openness turns stink into something useful. Lies are exposed, corruption made visible, hidden power structures dragged out into the light.
  • Soil of change → The same waste that poisoned us can become fertile ground for new growth, but only if we do the work of turning it. This is how trust-based networks sprout, how projects like the #OMN emerge.

What it means in practice:

  • Don’t just delete the shit – we instead compost it. Bad actors, bad processes, and bad tech are made visible and contextualized.
  • Don’t hoard the shit – silos just trap the stink. Share, federate, distribute – so communities can add their own oxygen.
  • Don’t wallow in the shit – critique alone is not enough. The point is to grow fertile alternatives.

The composting metaphor says: yes, we’re drowning in #techshit, but we have the tools to turn it into the soil for something humane, resilient, and alive. #KISS

The #OMN is a simple project. But simplicity is deceptive, what makes it difficult for many #fashernista and #mainstreaming people is not the code, not the servers, not even the logistics. The difficulty is that the #OMN is rooted in a different path of human nature.

It isn’t designed to fit the old path of #stupidindividualism. It isn’t built to serve the greed of #dotcons. It isn’t here to bend the knee to the #deathcult. The #OMN is designed as a transition tool, a bridge to a different path, commons, trust, a living path. Once people arrive, they can build what they like. That’s why the #OMN isn’t just tech, it’s a toolkit for social change and challenge.

#KISS. Keep it simple. Keep it real. I’ve been building this bridge for 20 years, agenst strong counter flows, we were all pushed off the path when we handed our voices to the #dotcons. When #openweb culture gave way to #stupidindividualism, I was ready to give up.

So I bought a boat and sailed away. #boatingeurope. Not a metaphor – it’s survival. But then came the #ActivityPub reboot, the #openweb with the #Fediverse rose again. I came back. Because there was hope, there still is.

And now – five years into this reboot – we face the next predictable crisis: #mainstreaming, the sell-outs, the “respectable voices”, the NGO parasites. Yep, it’s normal, it happens to every alt project. And now it’s happening here.

The solution? Compost the mess. Not to attack individuals – most of them aren’t important. What matters are the paths they push us down. Because their “common sense” is the real danger. These are “common sense” paths that turn living networks into dusty, dry creeks.

That’s why I keep writing the #hashtag stories: to make these hidden paths visible. So we can choose differently by seeing what’s going on. . Then act to compost the #techshit to grow something real.

I started by saying the #OMN is a simple project, let’s illustrate this with the #OMN Process

  1. Gather

People, projects, and content come together.

Anyone can publish by trust, share, and tag media.

Use open standards (#4opens, #openweb).

No gatekeepers, just openness mediated by trust.

  1. Describe

Content is enriched with metadata -tags, descriptions.

Human-readable and machine-readable.

Stories are linked by meaning, not silos.

  1. Share

Feeds are syndicated (via RSS, ActivityPub, etc.).

Content flows across the network.

Local projects display, remix, and reframe.

  1. Distribute

Decentralized hosting: many small servers, not one #dotcons.

Mirroring + redundancy = resilience.

No central point of failure.

  1. Contextualize

Communities add their perspective, framing, and translation.

Different views can co-exist on the same story.

Keeps the commons diverse and contested, not controlled.

  1. Compost

Bad ideas, #mainstreaming, and #NGO co-option are made visible.

Instead of only deleting, we contextualize and critique.

This “compost” becomes fertile ground for better growth.

  1. Grow

New media projects emerge from the toolkit.

Each can shape the #OMN path to fit their community.

A living, adaptive commons.

Principles in practice, KISS → tools stay simple, human-readable, small pieces that fit together. #4opens → open data, open code, open process, open standards. Trust-based networks → rooted in commons, not control. Resilience → many weak ties are stronger than one big silo.

The #OMN is not an app you install. It’s a set of processes + tools to move us from isolation to commons, from #dotcons back to #openweb.

https://unite.openworlds.info/Open-Media-Network

Compost the blocking, keep the seeds alive, and make space for growth

It’s good to see more people turning their focus back to the #openweb. But for the past five years of the #reboot we’ve been distracted in a signal-to-noise mess from the #fashionistas. That waisted time needs to be over, we need to start looking clearly at both internal rot and the external threats.

A good first step to this is in balancing the realisation that we actually have far more direct power to deal with the internal mess than we do over the external #dotcons and their #closedweb “common sense” colonialisation. That’s why we need to put activism into composting the internal #blocking (see: https://hamishcampbell.com/?s=compost). Composting isn’t just a metaphor – it’s a way to recycle the piles of #techshit we’ve built up into soil that can grow new #openweb seeds we need to cultivate.

I understand the normal focus on the external #dotcons, yes, we need to balance this to keep pushing back against the external enclosures. But inside our own spaces, it’s clear that possessiveness, in code, in reputation, in control over projects, undermines cooperation and destroys trust. It wastes resources, it corrodes integrity – People often destroy what they love, not out of hate, but out of possession.

This is directly relevant to the degeneration of the #SocialHub project (see: https://hamishcampbell.com/why-teach-everyone-to-code-has-become-a-dead-end-slogan/). What was once the lively centre for the #ActivityPub and #Fediverse reboot is now reduced to a handful of unthinking “problem” people circling the drain. That’s not unusual, it’s a normal outcome when we fail to compost mess.

The lesson is simple: compost the blocking, keep the seeds alive, and make space for growth.

What can you do? Use the compost metaphors (#techshit, seeds, soil) into accessible non-branded messaging that sticks. You can help with editing to transform the long posts into shareable, short-form content for Mastodon, Fediverse, and allied networks.

Help is needed in curating and organizing existing #OMN writings into a structured wiki-style knowledge base. To build summaries, FAQs, and primers for newcomers who hit the projects cold. We need draft “composting guides” – how to deal with #blocking, #fashionistas, and #geekproblem inside communities. Moving this simple documentation to the Unite Forge and other new #OMN tools. Helping draft roadmaps that explain what’s built, what’s missing, and what needs contributors. Producing explainers on why #OMN is different from #dotcons and #NGO capture, why being grounded in #4opens matters.

Write out templates for horizontal decision-making (#OGB style) that projects can adapt. Suggest practical ways to “compost” blockers while keeping the wider network fertile. Help draft neticate rooted in #KISS + #4opens rather than #NGO-speak.

Each of these can be grown into living resources: wiki pages, blog posts, shareable guides, or activist toolkits – depending on where you want the energy to flow.

Why “teach everyone to code” has become a dead-end slogan

The geek answer (bad faith or blindness): “If only everyone learned to code, then society would be fairer.”

The activist answer: Code is part of the landscape, but culture, governance, and lived practice matter more. We don’t escape domination by teaching more people to type commands, we escape by changing what we do together with the tools.

Why “teach everyone to code” has become a dead-end slogan – it’s been tried, it’s been funded, and yet it hasn’t shifted power one bit. If anything, it’s reinforced the tech priesthood instead of breaking it.

The #geekproblem is exactly this blindness: geeks mistake tools for culture, skill for power, and training for change. They can’t see that the last 20 years of “learn to code” projects have failed precisely because they sidestep politics, trust, and social fabric. It’s comfortable, because it keeps power where it already is.

So, coding literacy might be useful, but it’s not transformative without social literacy – trust, collective governance, open processes. The real activist social tech path is to compost geek mess-making and build alt-cultures where tools serve the collective, not the priesthood.

Otherwise, “coding for all” is another flavour of #blocking – keeping us stuck, distracted, and blind. This is a useful example of the blinded #geekproblem. I use the word blinded to illustrate that people can’t see the sense in front of their faces. And I use the hashtag #blocking to show the outcome of this common “sense” blindness #KISS

Coding is not automatically social power, but in some contexts it does act as power, and understanding when/why helps unpack the #geekproblem.

  1. When coding is not power

Most coding done in industry is low-level labour: writing scripts, fixing bugs, maintaining old systems. These programmers aren’t powerful; they’re workers. Their code serves capital.

Teaching kids to code (“everyone can make an app!”) rarely translates to actual power, because the infrastructure, distribution, and governance of platforms remain controlled by corporations.

Coding on its own doesn’t equal voice. A line of code in a corporate repo is no more socially powerful than a line in a personal diary if the person coding has no agency over how it’s used.

  1. When coding is power

Coding becomes power when it bridges infrastructure + governance + culture.

Building #openweb infrastructure: If you can write the protocols or standards (e.g. ActivityPub, TCP/IP), you shape the possibilities for everyone downstream. That’s a kind of structural power.

Gatekeeping: If you control the codebase of a popular project, you can decide what features exist, whose contributions get merged, and which voices are excluded. This is soft but real power.

Automation and scale: Writing code that automates tasks (e.g. bots, algorithms, moderation tools) gives leverage over many people’s experience, especially when hidden in the background.

Narrative + legitimacy: In activist or grassroots spaces, coders too often get treated as “high priests” because they appear to have magical abilities others lack. This cultural framing inflates their social weight.

  1. The Catch (where the #geekproblem lives)

Coders confuse technical power with social change. They think: “If I can write the tool, I can fix the politics.” But tools reflect cultures. Without collective governance, tools just reproduce existing hierarchies.

The illusion of inevitability: because software underpins modern life, geeks assume society must organize around them. That blindness is what we’re pointing to.

When geeks push “everyone must code” as the path, they miss that most people don’t need to code to have power, they need agency in decision-making and trust networks.

  1. How it really works (coding + social power)

Coding has power when embedded in movements that control their infrastructure. Example: early #Indymedia coders had real social power because their code directly enabled publishing outside corporate media – and at the start they were accountable to activist collectives.

Coding has power when it’s used to mediate flows of attention, trust, and resources. For example, algorithms that boost or bury voices. In grassroots hands, that can be liberatory; in corporate hands, it’s oppressive.

Coding becomes shared power when it is paired with open process (#4opens), shared governance (#OGB), and cultural literacy. Otherwise, it’s generally more priesthood, likely for the #deatcult in the end.

So: coding is like fire. On its own, it’s just heat and light. In the hands of a few, it’s a weapon or a fortress. In the commons, with shared tending, it’s the hearth – collective power.

To recap, coding as social power: Myth vs Reality

Myth 1: Coding = empowerment
We’ve been told that “if everyone learns to code, everyone will have power.” Twenty years of coding bootcamps, “learn to code” initiatives, and school programs prove otherwise. Most of this simply trains people to slot into corporate pipelines. The power stays where it always was.

Reality: Coding on its own is labour, not empowerment. The infrastructure, governance, and distribution layers decide where the power flows. Without culture and collective governance, coding is just fuel for someone else’s engine.

Myth 2: Coding makes you special
Coders often act like priests, holding secret knowledge. In activist spaces, this creates the illusion that coders alone can “save” or “lead.” That’s the #geekproblem in action.

Reality: Tools are only as powerful as the cultures and processes around them. A coder without collective accountability is just another gatekeeper. A coder inside a collective, with open governance (#4opens, #OGB), can help shift power outward.

Myth 3: Coding will fix politics
The geek fantasy: “If I build the right app, the politics will fix itself.” We’ve seen this with countless “alternative platforms” that end up reproducing the same hierarchies.

Reality: Politics is culture, trust, and process. Code can mediate, amplify, or automate, but it cannot replace politics. Tools without culture are empty shells; culture without tools is still possible.

The compost view is the task isn’t to make everyone a coder, but to compost the priesthood and grow cultures where coding is a part of the collective. That’s the #KISS answer: code can support social power, but it is not social power.

What to do to compost this #geekproblem mess:

  • Build cultures, not just tools: Stop pretending apps fix politics. Tools only matter if they grow inside strong cultures. Put people first, tech second.
  • Open the process (#4opens): Keep everything open: code, data, governance, strategy. Power hides in shadows; openness dissolves the priesthood. If it’s not open, it’s not our path.
  • Practice collective governance (#OGB): It helps when decisions about infrastructure are made more horizontally. Coders are part of the collective, not above it. Shared governance turns coding from priesthood into common fire.

The path out of the #geekproblem is in composting geek blindness and building living cultures where coding is a part of growing the commons.

For an example, this post is relevant to the degeneration of the #SocialHub project, which for meany years was the place for #ActivityPub and #Fediverse #openweb reboot, but now what’s left of the social side is the few remaining active unthinking “problem” people.

This is a normal path and outcome, that we need to compost to keep growing seeds #KISS

The OMN with indymediaback and makeinghistory are paths

Most of the mess, and most of the #blocking, comes down to the same old story – ownership and control. Who holds the keys? Who decides? Who gets locked out? Instead of wrestling in that cage, the #OMN takes a simpler path: we walk away.

We put a class of media into the commons, governed openly through the #4opens: open data, open process, open source, and open standards. That means no one can close it down, hoard it, or fence it off for profit. The value comes from the shared pool, not from gatekeeping.

This is the heart of #KISS in the #OMN: make the flows work first, in ways people can understand, and build trust on top of that. The tech exists to serve these flows, not to dictate them. This isn’t about perfect crypto or hard lockdowns; it’s about commoning media so that everyone has the right to read, share, and build on it.

Yes, the #mainstreaming mess will eventually follow us – as it always does. But the plan and hope is that by the time it catches up, the habits, culture, and expectations we’ve grown around open media will have shifted society enough that the old traps won’t work the same way. If we’ve done our job, the default will be more open, collaborative, and accountable, not locked down. That’s the #KISS path: simple, resilient, and grounded in the commons.

On the #OMN with #indymediaback and #makeinghistory paths – We’re not talking about a single bridge, but a federated ecosystem, with the current example of both #DAT and #ActivityPub running on the same server, sharing a common database of media objects. As the data flows, text and metadata are redundantly stored in the open (#4opens). That way, if one server gets hacked, it can simply be rolled back and restored from the wider pool. #KISS

The P2P side works much like #nostr in that it can have a list of flows in and out to servers and can use any of these to publish and receive media on the #openweb. The advantage of the #p2p app side is that each local app in a backup for the online servers (see #makeinghistory), which as critics say can be, and will be, taken down some times. Also, they will work in their own right for people who need a more locked down path, and this will be needed in more repressive spaces and times. The clear advantage is this still gives them outflows to the wider #mainstreaming client server media outreach, to what matters, effect, so it ticks both boxes.

We aim to solve technical issues with human-understandable social paths, not hard tech for its own sake. Yes, in a minority of cases hard tech will be needed – but that’s for the #geeks to solve after the working social paths are clear, not before.

We fix problems through #KISS social processes and #4opens transparency, not by defaulting to encryption and lockdown. Hacking is outside the focus scope of the #OMN. What we’re building is about trust and flows, not code as an end in itself. Hacking belongs on the #geek paths – useful, but only after the trust and flows are established. The code should be there to secure what’s been built, not to block it before it exists.

Without trust and working flows, there’s no value at all, no matter how secure, encrypted, or elegant the tech stack. If the campaigns, activism, and people aren’t using it, the system is pointless. And being pointless is something we need to be more honest about. Building for the sake of building, while ignoring the social, community layer, feeds the #geekproblem and starves the movement.

So, what can people actually do in the real world to make this path happen?

  • If you have resources, you can help fund the development work – keeping it in the hands of the people actually building the open commons, not some corporate gatekeeper.
  • If you’re technical, you can code the applications and servers that power the flows. We need builders who understand that trust and usability come first, not shiny tech for its own sake.
  • If you work in UX or testing, you can make sure what we build is something real people can actually use and trust – simple, clear, and accessible.
  • If you do media, you can tell the story. Write, film, photograph, blog, podcast – whatever it takes to spread the word. The more people hear about an alternative that works, the more chance it has to grow.

Whatever your skills or resources, the important thing is to get involved in the flow. This is not a spectator sport, and the is unlikely to be pay, it’s #DIY so the commons will only be built if we build it together. #KISS #4opens #OMN

Building bridges instead of walls

Activist tech has been stuck in “bunker mode” for 20 years. We now need to work on building #4opens native, commons-first systems that store, share, and protect movement knowledge in ways that don’t require a priesthood of insiders to operate.

In an active movement, forum threads, shared docs, livestreams, and photos aren’t just chat noise, they’re collective memory. If we treat them as disposable, we throw away the hard-earned lessons that future activists will desperately need. The solution is #KISS-fed, redundant, federated archiving:

All public movement data sits in the commons.

Metadata + content are mirrored across multiple federated nodes.

Backups are easy to pull, restore, and re-seed by anyone who ever has trust access.

Data is grouped via hashtags, not rigid taxonomies, so it flows where it’s needed.

This is appropriate tech: low-complexity, high-resilience, built for social utility first. But for this to grow it can’t be mediated to death by the #geekproblem – code should follow social needs, not the other way round. If we can get this kind of infrastructure running, we stop losing our history, we keep movements porous instead of paranoid, and we finally start building bridges instead of walls.

https://unite.openworlds.info/Open-Media-Network

Let’s look at an example of this: For the #DAT protocol to become relevant in #FOSS activist tech, we need to stop treating it as an isolated island and start building solid bridges to #ActivityPub. The two are not enemies – they are complementary paths. p2p tools and protocols like DAT brings distributed, peer-to-peer file persistence; ActivityPub brings the social layer, discovery, and conversation. Together, they create a space where activists choose their preferred path without being siloed or alienated, and without the unhealthy isolation that comes from the current #geekproblem habit of fetishising one protocol at the expense of all others.

Diversity is the basis of any healthy ecosystem – biological, social, or technological. In nature, monocultures are fragile; in tech, monocultures are authoritarian. We need to approach activist infrastructure with the same principles that make ecosystems thrive: multiple species of tools, cross-pollination between communities, and a constant flow of ideas and resources. This doesn’t mean adding complexity for complexity’s sake; it means designing with #KISS in mind, while ensuring redundancy and adaptability.

If we take this ecological view of the #openweb, then bridges are not optional extras – they are the lifelines. In our example, by linking #DAT and #ActivityPub, we create a richer habitat for movements to live in. We make it harder for corporate capture to take root, and we give people the freedom to move between spaces without losing connection and context. That’s how we replace the bunker mentality with a real commons, not just defensive walls, but thriving, interconnected gardens.

The #OGB: A Native Path for Open Governance

The #OGB (Open Governance Body) isn’t built around the smooth, efficient ideals of platform logic or institutional control. It’s messy by design, because it’s rooted in real-world activist practice. It draws from the hard-won experience of protest camp organising, where consensus, affinity, and trust are the foundations of action.

The #OMN governance app we’re working with doesn’t come from corporate boards or #NGO playbooks. It comes from the mud, the rain, the late-night meetings under tarps and tents, where people work through differences because they have to – because they’re doing something together that matters. This is people-to-people trust, built over time, grounded in shared struggle. We’re not designing for online autocracy. We’re designing for affinity groups.

So yes, the #OGB is trying to do what many others won’t. Not because it’s easier (it’s not), but because it’s necessary.

We already know this kind of organising works, not in theory, but in practice. Sometimes badly, sometimes slowly, but it works. People come together, they make decisions, they take action, and they build power without needing top-down control. But we also know it doesn’t scale well – that’s always been the limit of these methods. Consensus is powerful at small scales, but it breaks under weight if there’s no structure to hold it.

That’s where the #Fediverse and #ActivityPub come in.

The #OGB is built on the idea that the horizontal protocols of the Fediverse can scale this kind of messy, native governance, not by centralising it, but by networking it. Federation isn’t just a technical model; it’s a political one. It mirrors the way affinity groups operate: autonomous, loosely coordinated, sharing enough common ground to work together without collapsing into uniformity.

This is what we mean when we say the #OGB is native. It’s growing from within the world we’re already in – not imposed from outside. It respects mess, embraces friction, understands that governance isn’t something you tack on later, it’s something you live through, build with, and struggle over, together.

You can see the work in progress here: https://unite.openworlds.info/Open-Media-Network/openwebgovernancebody

If we’re going to have a real #openweb, we can’t keep mimicking the logic of #dotcons, or #NGO platforms and empires. We have to build our own paths, grounded, imperfect, resilient.

We invite you to walk this path.

A story for outreach: https://unite.openworlds.info/Open-Media-Network/openwebgovernancebody/wiki/Out+reach+short+story+-+Stalls+and+Code.-

W3C fits into #OMN with shared origins and intentions

Let’s look at this from a prospective, both the W3C statement and the #OMN paths recognize that the early web was built with sharing, decentralization, and public good in mind. The #W3C calls for a web “respectful of all participants,” which aligns with the #OMN goal of building an open media infrastructure based on the #4opens: open data, open source, open standards, and open process.

Where this W3C #mainstreamin alt path falls short (and why #OMN matters). The W3C vision speaks of “taking responsibility” and “addressing the impact of our work” through technical standards, but in reality, the current web’s architecture has been co-opted by centralized, profit-driven platforms (#dotcons). As the funding and structure of the organisation its self.

In reaction to this, the #OMN is grounded in the reality that technical fixes alone won’t solve these social problems, we need working activist cultures, grassroots governance, and federated media networks to actively challenge #mainstreaming and its #deathcult values. The geeks can’t solve the problem themselves…

What #OMN brings is a social layer: W3C focuses on technology and ethics at the standards level. The #OMN focuses on the cultural and organizational infrastructure needed to build, sustain, and govern ethical activism.

Scaling what worked: The W3C admits we’ve lost the “openness” to misinformation and data abuse. The #OMN is about bringing back what worked (e.g., early #Indymedia, radical tech collectives) and scaling it using tools like #ActivityPub and the #fediverse.

Compost and regenerate: The W3C wants reform from within. The #OMN recognizes the need to compost the #techshit, grow anew, and create parole autonomous, federated spaces where community processes are native, embedded, not isolated.

A positive reboot (from within the #openweb) is needed, where the W3C gives us a narrative frame., the #OMN gives us a path to act. We need to reclaim the web not only through better standards, but through working, lived alternatives – composting what failed, and growing social tech based on what we know works.

We need bridging, if the W3C and groups like them are serious about rebuilding a humane web, then the #OMN path has much to offer:

  • A bridge to activist governance.
  • A working example of the Ethical Web Principles being practiced socially, not just technically.
  • A push for native, grassroots agency, not just safeguards built by the same #NGO centralizers who failed the first time.

Let’s do better, yes, but let’s also be native, that’s what the #OMN is about.


A thread on a different project on the same subject, “Open Source and Open Standards nerds like me, ought to know by now that the protocol is the least compelling thing about a service. Who cares if your home is built using only Stallman-blessed tools, when the walls are full of rats?” https://shkspr.mobi/blog/2025/07/im-never-going-back-to-matrix

Dig, Plant, Grow. Compost the #Techshit. Repeat

This post is talking in the sense of structure rather than individual experience. Let’s be honest, much of the so-called “alternative” tech scene is still stuck. Yes, we fled the #dotcons for something better, but ended up with copies of the same broken models. The #Fediverse, with all its potential, is still as often dominated by “mainstreaming meta” chat (“Twitter refugees incoming!”) or conspiracy-laden, #fashionista rabbit holes. It’s little wonder that even the nerdy privacy crowd struggles to find meaningful content or community. And no, shouting “fuck the system!” isn’t enough.

If we’re serious about systemic change, we need to do much more. The question is not if people will come, some always will, the real challenge is what they’ll find when they get here. Right now? It’s messy, insular, and missing the tools people need to use for change and challenge, let alone feel at home. We must move beyond building clones of corporate platforms and start composting the path that got us here.

This is why we need a reboot, not from scratch, but from memory. Projects like #indymediaback aim to reclaim 20+ years of working grassroots media practice. With tools like #ActivityPub we now have scalable tech that can bring those old social processes – based on #4opens (open code, open data, open governance, open standards) – into the present. The #OMN (Open Media Network) is such a path: combining the solid tech foundations with the radical social methods that we know worked (but didn’t scale).

To move at all, we must change and challenge the toxic norms of the #mainstreaming #deathcult, and yes, this means building real alternative identities and spaces that don’t live in the shadow of big tech. Being “alternative” used to mean something, and it can again, if we stop ONLY copying the mainstream and instead focus on nurturing something more strongly rooted and real.

This isn’t about being purist, #FOSS and Open Source already works in this way, the #OMN just brings this path to media and community infrastructure. It’s not utopian, it’s compost. And yes, that means dealing with hard questions, including our own funding. Let’s stop pretending we’re neutral when we’re not. Let’s build from honesty. It’s time to dig, plant, grow, and repeat.

#OMN #4opens #indymediaback #openweb #fediverse #techshit #KISS #NGO #deathcult #mainstreaming #altmedia #DIY

NOTE: the comments below are a useful example of #stupidindividualism, and remember this hashtag is about social groups and their #blocking of social thinking. The history matters, flaming is not a useful response.