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, and the only way out is to start 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.

Activist tech has been stuck in a defensive crouch

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.

Rebalance, by shifting focus from tools to cultures

Appropriate technology in activist tech means tools built for our real contexts, not for Silicon Valley fantasies or bunker-dwelling paranoia. It’s about lightweight, repairable, understandable systems that communities can actually run, adapt, and share. Right now, the #geekproblem pushes us toward shiny, #dotcons shaped over-engineered toys that serve developer ego more than people and community need or bloated encryption stacks nobody understands, federated protocols that collapse under complexity, and endless half-finished “next big things” with no grounding in actual social use.

We need to drag the conversation back to fit for purpose, tech that works in the messy, underfunded, real world of activism, where trust and openness are the foundation, and security is woven in without becoming a fetish that locks us away from each other.

The #fedivers #openweb reboot of the last ten years is a good first step, but it embeds meany of the #mainstreaming issues and has the deep #geekproblems embedded into its culture and tech stacks. A second step away from this is, the social understanding, that security doesn’t come from code alone, it comes from the community that surrounds it. Without a living, visible, and shared culture, the best tools are just dead weight.

The path starts with embedding our tools inside open, self-documenting, collective cultures. If you can’t see how decisions happen, you’re just replacing one opaque power structure with another.

Forget the myth of the “perfect” platform. What we need are messy but resilient spaces, a diversity of nodes, loosely connected, each carrying its own part of the load.

Build commons-first infrastructure, to re-anchor our work in openness, federation, and trust-based networks baked in from the start. The baseline is #4opens – open data, open source, open standards, open process – non-negotiable.

On this path, the #OMN (Open Media Network) can be the publishing spine: a trust-based network where stories, actions, and knowledge move between activist spaces without corporate choke points and #blocking.

We must bridge into existing real-world struggles – unions, climate justice, housing fights. Tech that only talks to other techies is just another dead end.

Stop digging the same hole, we stop wasting energy on projects that make us smaller and weaker:

No more encryption fetishism. Encryption is the lock on the door, not the whole house.

No more closed, invite-only dev silos. If you can’t talk openly about the work, it’s either the wrong work or the wrong space.

No more “founder cult” projects that collapse when one person burns out or drifts off.

Security is not enough, survival is not victory, we can be safe and irrelevant – or vulnerable and changing the world by breaking corporate dependency, by building the infrastructure of a post-#dotcons world. This isn’t about perfect software, it’s about building the cultures that can use it – and win.

Stories on this subject:

https://unite.openworlds.info/Open-Media-Network/MakingHistory/wiki/Story+-+Oxford%3A+Going+with+The+Flow.-

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

Activist tech has been stuck in a defensive crouch

For two decades, activist tech has been stuck in a defensive crouch. We’ve built bunkers (security tools, encryption layers, anonymity networks) but very few bridges. That’s left the field fragmented, insular, and often unattractive to the people we’re supposedly trying to empower.

If the aim is to push social change and challenge rather than just survive, here’s what I think needs building:

  1. #4opens-native infrastructure Open data → not just sharing docs, but making activist knowledge queryable, remixable, reusable. Open source → tools that anyone can template and that are designed for non-geek participation. Open process → transparent decision-making, recorded and accessible, not locked in Discord chats and private Signal groups. Open standards → making sure our platforms talk to each other rather than becoming new silos.

Right now, most “secure” activist tools violate at least two of these, which is why they never scale socially.

  1. Publishing-first culture (#OMN approach)

Defensive tools keep activists inside – whisper networks, encrypted groups – but change needs broadcast. We need infrastructure for:

Collaborative publishing (like a modern Indymedia, federated rather than centralised)

Native-to-activist communities, not corporate platforms with activist skin

Embeddable media flows that any group can plug into their own site and feed back into the commons
  1. Bridges between the “geek” and the “street”

We keep losing people at the handover point between coders and campaigners. This means:

Building social UX: not just “usable” but welcoming, narrative, and easy to onboard without a training camp

Open governance for projects, so they don’t ossify into closed dev clubs

Mixing online and offline organising so the tech is embedded in the movement, not floating above it
  1. Messy but live governance (#OGB model)

Most activist tech projects fail when the original team burns out or falls out. We need:

Federated governance where each node makes its own calls but can still coordinate

Lightweight, transparent conflict resolution instead of exile-by-moderator

Structures that reward contribution over gatekeeping
  1. Narrative + polemic

Tech alone doesn’t move people, stories do. The #4opens path should be wrapped in cultural work: films, zines, podcasts, political memes, all pointing back to live, working tools people can join today.

Why this matters: If all we do is encrypt ourselves into tiny rooms, we’ve already lost – the social fabric will rot away outside those walls. Encryption is necessary for many struggles, but it’s not sufficient. Positive activist tech must be porous, messy, and visible, because change needs an audience and a route for people to join.

Bridges: An activist tech roadmap

We’ve made excellent hiding places – but the point was never to hide. What we need to stop building. (Let it compost – it’s done its job, or it was a dead-end from the start?)

Paranoid toys for the already paranoid. Endless “yet another secure messenger” forks for people who already have six installed.

Security fetishism that confuses obscurity with safety.

Crypt bro sandcastles. Blockchain “liberation” projects that replicate Silicon Valley greed, gated by tokens and VC hype.

Anything that smells like replacing corporate overlords with slightly more smug overlords.

Single-issue encryption fortresses. Tools so focused on privacy that they have zero public presence or outreach capacity. Result: the tech survives, but the movement starves for connection.

Endless horizontal-but-empty governance “frameworks” Looming Google Docs full of aspirational process that nobody follows in practice. No real community roots, just “process cosplay.”

What to start building (This is the real #4opens + #OMN work)

Social-first tech stacks. Start with people, not protocols.

Build interfaces that encourage conversation, collaboration, and collective memory.

#4opens principles applied to UX, governance, and hosting — not just the code repo.

Native governance baked into the stack. #OGB-style decision-making visible and accessible to every user. Influence exercised in the open, with accountable stewardship, not backroom admin chat.

Open media networks that publish first, secure second. #OMN-style federated publishing where public content flows freely, while personal data defaults to private. Focus on amplifying radical stories instead of just hiding them better.

Tools that make bridges not walls. Mediating the signal-to-noise rather than blocking at the first whiff of disagreement. Spaces where trust can grow between different grassroots tribes without falling into the #NGO/#dotcons gravity well.

Composable, messy, repairable tech. #KISS principles, with the option for local hacks and templates. Document the how and why so that when projects die, others can compost them into new growth.

The call-out is we can’t code our way out of the #deathcult with bunker software. The way forward is messy, social, and built in the open. Let’s stop pretending that better locks will save us, and start making better streets for our movements to meet, cooperate, and fight together.

The #4opens + #OMN path is the stepping stone back into the light. Take it, or stay buried.

Security comes from community rather than technological control

It turns out that what hackers yearn for is not raw power but security – not just the technical kind, but an emotional security that is harder to admit to, so it gets dressed up in the language and posture of technology.

Because many in these paths and spaces operate with narrow social and political horizons, shaped by individualist tech culture, a distrust of messy collective life, and little grounding in movement history, their insecurity rarely finds healthy expression. Instead, it gets channelled into #mainstreaming patterns: centralising control, hoarding decision-making, gatekeeping access. The feeling of safety comes not from trust, but from control.

This is why in so many “open” projects we see:

Root admin privileges treated like a personal bunker.

Technical gatekeeping replacing collaborative stewardship.

Social disagreements re-coded as “technical issues” so they can be “resolved” by force rather than dialogue.

The power they wield is a symptom, the insecurity is the cause, lack of balance is the disease. The problem is that command/control cultures make insecurity worse, they turn every challenge into a threat, every new contributor into a risk, and every disagreement into a test of dominance. Over time, this drives out the very diversity and collaboration that could create true resilience.

The #4opens – open data, open code, open standards, open process – is not just a governance checklist. It’s a practical, everyday discipline that forces a shift from control to collaboration. It changes the emotional terrain.

Open data dissolves the hoarding instinct, because nothing critical is locked away in one person’s vault.

Open code forces the bunker doors open, making it normal for others to touch “your” work.

Open standards create interdependence rather than dependency, reducing the fear of losing control.

Open process makes decisions visible, accountable, and shared, replacing the hidden backchannel with a transparent commons.

By practising the #4opens, even the most control-driven hacker can start to find a different kind of security, rooted in trust, redundancy, and collective stewardship rather than in solitary power.

The #4opens doesn’t magically fix emotional insecurity, but it creates a scaffolding of transparency and accountability where balance can grow. It turns projects from personal fiefdoms into shared ecosystems, and in doing so, helps people unlearn the reflex to seek safety only through domination.

The way out is not to strip hackers of influence, but to build cultures where influence is exercised in the open, with care, and where security comes from community rather than technological control.

A #fluffy view – Think of a self-hosted community chat platform, something small, privacy-focused, run by a handful of volunteer hackers. The core devs are brilliant, but they see every problem as a technical one: security means encryption upgrades, stability means more containerization, and governance means a GitHub permissions list.

When disagreements arise over moderation, they don’t trust open discussion. Instead, they quietly add admin-only tools that can hide messages or boot users without notice. From their perspective, this is “security”, keeping the platform stable and safe. But because the process is invisible and unilateral, it breeds mistrust. The community feels controlled, not cared for.

Now imagine this same project embracing the #4opens:

Open Data – Moderation actions are logged and visible to everyone.

Open Source – The code that runs moderation tools is public, so no hidden powers exist.

Open Process – Policy changes are discussed in a shared forum where everyone can contribute.

Open Standards – The platform can interoperate with others, so no one is locked in.

This changes the emotional root of the hackers’ insecurity: their “power” no longer depends on guarding the system against imagined chaos, but on participating in a transparent culture where the community itself holds the system together. Security is now mutual care, not technological control. The hackers still have influence, but it’s exercised in the open, grounded in trust, and shared with the people they serve.

A spiky view of this – The problem with too many hackers is that they mistake root access for moral authority. They wrap their emotional fragility in layers of SSH keys and sudo privileges, then strut around acting like benevolent dictators for life. You see it in the endless “code is law” sermons, in the backroom channel decisions, in the smug dismissal of “non-technical” people as if empathy were a bug. They lock down wikis “for security,” gatekeep repos “to avoid chaos,” and implement moderation tools that work like secret police. This is not liberation, it’s digital landlordism, the same power-hoarding rot we see in the #mainstreaming mess, just with a Linux hoodie instead of a corporate badge.

#KISS it’s best not to be either a dogmatic #fluffy or a #spiky prat about this need for balance.

Talking vs. doing in the #openweb

I often hear: “You post a lot, but what practical work have you actually done?” It’s a fair question, there’s far too much hot air in tech spaces, and the #openweb can’t be rebuilt on rhetoric alone. The critique goes something like this:

“You’re preaching an idealised ‘community’ that doesn’t exist. You criticise the mainstream (fair enough) but keep pushing alternatives without showing a tangible model that works. It feels like you’re looking for an audience, not a conversation.”

And here’s my side of this:

I was part of the team that got multiple governments in Europe to adopt the Fediverse — working on the outreach that took the tech to the European Union.

I co-ran 5 Fediverse instances with thousands of users in its early years. We eventually had to shut them down — an experience I now talk about openly because we need to make this work better next time.

I’ve worked on meany of #openweb projects going back to the birth of the WWW. That history is here: https://hamishcampbell.com

Projects include UK #Indymedia, #VisionOnTV, the Open Media Network (#OMN), the #4opens framework, and the #OGB — all aimed at building governance, infrastructure, and culture outside corporate control.

Here’s the crux: building outside the mainstream is messy, fragile, and uncertain. There’s no guarantee that any of this will “win.” But the alternative – doing nothing and letting every commons be enclosed – guarantees failure.

The work is #DIY culture. If you don’t want to build, you don’t have to. But if you do, you have to accept the risk, the mess, and the fact that you won’t get the same dopamine hits as shipping a VC-backed app. You also have to resist the slide into trolling when frustration builds.

The real challenge is cultural: how to support tech that walks outside the dominant paths long enough to make new ones. That means building infrastructure that runs on trust, openness, and care, not just control, profit, and scale. If we stop doing this, every alternative will keep collapsing back into the defaults.

Compost the Chancers: How Careerists Kill Horizontal Tech Movements

It happens every time. A fresh grassroots project kicks off, chaotic, joyful, full of promise. The code is rough, the conversations messy, but the energy is real. People come together not for money or prestige, but because something needs doing and no one else will do it.

Then, they arrive, the careerists, the chancers, the opportunists who talk a good game of “community” and “values” while quietly positioning themselves for influence, funding, reputation. You know these people, they start “facilitating” things, pushing for “professionalism,” organising pointless panels, and – without fail – introduce hierarchical management logic dressed in pseudo-horizontal language.

Soon, the messy collective space becomes an application form, organic conversations shift to curated “working groups”, governance becomes gatekeeping, code becomes control.

Careerism is a cultural virus, OK, these people aren’t evil villains, they’re simply products of their environment, trained to extract value, shape narratives, and build CVs. But their impact is destructive, even if unintentional. What they bring with them is the #mainstreaming mindset, a default toward #NGO logic, safe liberalism, risk-aversion, and the slow suffocation of wild experimentation.

They start to block with niceness., they silence with process, they smother with “inclusivity” until there’s no air left to breathe. When people question this, then they start to become nasty, trolling, blocking and finally ignoring runs its predictable course…

Examples? Let’s name some very formiler patterns:

The Self-Appointed Spokesperson – Shows up late, speaks the loudest, builds a personal brand on the back of others’ labour.

The Grant-Whisperer – Always chasing the next funder, reshaping the project to fit what’s "deliverable" instead of what’s needed.

The Gatekeeping Ally – Claims to represent the marginalised, while shutting down dissent and complexity with soft authoritarianism.

The #NGO Zombie – Thinks every grassroots space needs a board, a charter, and a code of conduct before it needs trust or purpose.

The Pivot Junkie – Tries to steer the project toward startup land “just to be sustainable,” and ends up reinventing capitalism in #FOSS clothes.

These types thrive when horizontality lacks grounding. On the path we need to take, “cancel culture” is a cul-de-sac. Blocking them just makes them martyrs. Ignoring them lets them take over. The alternative? Compost them, let their bullshit rot in the open, call things what they are. Tech is political, values are not neutral. What to do? Compost, don’t cancel.

To reboot the #openweb and keep it rooted in the #4opens: Open Code, Open Data, Open Standards, Open Process. Rebooting needs resistance, we have to build spaces that are both porous and protected, we need, paths and spaces with membranes, not walls. Trust-based collectives with clear boundaries. If someone’s treating your community like a stepping stone, show them the compost bin. If someone’s building with care, humility, and rootedness, then share our tools with them.

This is not a purity test, it’s composting as culture, if something smells off, trust your nose. Because if we don’t get serious about this, the chancers will take over. They always do. Unless we make the path too muddy for them to walk it.

A core problem is that too many “open” tech projects try to model social relations after code workflows rather than shaping code to reflect healthy social processes. Ersatz writing, ersatz governance and the slow death of the #openweb. We’re living through a wave of fakery. The #AI hype machine spews endless streams of ersatz writing – grammatically perfect, stylistically smooth, and hollow. It feels like content but carries no lived experience, no rooted context, no risk. Unedited, it’s a shadow play of culture.

The same hollowness infects too many horizontal tech spaces. Here, we find ersatz governance – systems that borrow the forms of openness and collaboration, but replace the substance with tech bureaucracy. Instead of starting from lived social practice, they mimic software workflows: people reduced to issue tickets, trust replaced by “process,” culture swapped for sprint planning. The result is the same as with AI: the outputs are technically competent but socially dead.

When governance is reduced to process, the door swings open for the chancers, the careerists, and the #NGO climbers. They’re fluent in the language of inclusivity and consensus, but they’re not here to build, these people thrive in systems where nothing is anchored in lived trust or collective history. In such environments, appearances are reality, and they control the appearance.

The mirror needs to flip, healthy social production can inspire healthy code production, but trying to run human interaction like a Git repo produces brittle, alienating cultures. We see it in the #Fediverse right now: meetings full of procedure but no warmth; #PRs merged while communities fracture; polished governance documents for projects this pointlessness.

The #openweb was never meant to be safe for professional managers of openness. It was meant to be a living commons, messy, unpredictable, full of disagreements and breakthroughs. If we can root our governance in actual relationships rather than corporate abstractions, we can build tech that reflects community rather than forcing community to reflect tech. Otherwise, we’ll just have two hollow empires – AI’s Ersatz Writing on one side, and our own Ersatz Governance on the other – both looking open, both feeling dead.

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 model 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. It embraces friction. It 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 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.-

A guide for staying honest and native

A community is only viable if enough people care enough to keep it relevant. In this era of #stupidindividualism, most people don’t lift a finger to make that happen.

This is the norm across many #4opens spaces: a near-total lack of interest in building or maintaining shared paths. It’s a textbook case of right-wing Tragedy of the Commons. Developers show up when it suits them, use the space for their narrow needs, then drift off without contributing to the upkeep. They treat community like free infrastructure – something passive they can extract from – rather than a living, tended path.

This same pattern plays out across the grassroots and #FOSS world. Devs focus on their code, their projects, their timelines. Rarely do they look up and engage with the broader ecology that their work depends on. In the #Fediverse especially, most developers ignore shared infrastructure, governance, and the standards they rely on, until something breaks. Then they complain.

Same social dynamics, same outcome: a mess that keeps repeating itself. And until we break that pattern, we’re stuck.

On the alt path, it’s fair to ask for clarity. When we talk about “#openweb projects,” we mean efforts grounded in the values of the early web commons: transparency, decentralization, collective ownership. This includes things like the rebooted #Indymedia, the #OMN (Open Media Network), and the #OGB (Open Governance Body). These aren’t about building shiny platforms, they’re about building the structures and relationships that allow real alternatives to survive and grow outside the #mainstreaming mess.

This isn’t just evangelism, it’s hands-on work: shaping frameworks for local and federated publishing (like the original Indymedia), and now modelling governance and trust systems that resist hierarchy and #NGO capture.

As for government institutions joining the #Fediverse – What we pushed was a bottom-up, native process rooted in people and practice, not imposed solutions. But as is often the case, after we laid the groundwork, the institutional #PR and #NGO crowd moved in and took over.

The “community” we speak of does exist, even if it’s fragmented, marginal, and ignored. You’ll find it in squats, permaculture collectives, activist media spaces, messy corners of the #Fediverse, and in the hands of people still building trust and tools outside the #dotcons. It’s not centralized or funded, so it’s not visible like capitalist platforms are. But it’s real. I’ve lived inside it for decades.

You’re right that real code is needed. But it’s not about one perfect tool. It’s about the network of trust and shared values that can hold many tools and projects together. That’s slower to build, less flashy to show off, but far more resilient and necessary.

The #Fediverse is a good first step. But let’s be honest: we’ve lost the thread when it comes to building tech that walks off the beaten path. Most #mainstreaming energy, and much of the #NGO outreach, still flows into reinforcing the same old ruts: centralization, enclosure, obedience to capital. Anything that doesn’t follow those routes is starved of support and often treated as a threat, a curiosity, or a waste of time.

But it’s exactly that off-path infrastructure we need, not just to resist the current system, but to outlast it. To still be standing when the old ways collapse. That means supporting tools and systems that aren’t profitable, aren’t convenient, and aren’t slick. They’re harder to fund, harder to maintain, but they’re what let us keep moving forward through the coming storm of #climatechaos.

If we don’t build and sustain these alternative tracks, the dominant ones will keep absorbing or destroying everything new. It’s a recursive trap: we need better systems to make better tools, but we can’t build those tools without some of those better systems already in place.

So we need to hold space – with care, mess, and trust – for that in-between.

That’s where projects like #OMN, the rebooted #Indymedia, and the #4opens live. Not trying to escape friction, but embracing it. Mediating it. Letting it guide us toward what’s honest, what’s native, what lasts.

The new litmus test isn’t “Does it scale?”
It’s: “Does it spread? Does it take root? Can it compost and regrow?”

It’s important to recognise that friction – the mess, the slowness, the need for constant negotiation – is not a flaw in native paths, it’s a virtue. It’s how trust, mutuality, and accountability are sustained over time. These are not bugs to be eliminated with slick #UX and #VC-funded convenience – they’re part of what keeps a community honest and rooted.

The problem arises when less-native, often externally imposed systems (driven by capitalist or institutional agendas) treat these messy, friction-full spaces as broken or backwards. This is the classic dynamic of imperialism and settler colonialism: imposing order, “fixing” things, extracting value, and in doing so erasing the lived, relational logic of native systems.

If you look through the lens of native/western histories – indigenous struggles vs colonial modernity, the same pattern plays out again and again: the native path is degraded, disrespected, overwritten. In tech, it’s no different. You see it when horizontal, trust-based networks get steamrolled by #NGO capture, institutional gatekeeping, or #VC-funded platforms that sell convenience and control.

So the real work is mediation. Not purity, not retreat, but balancing these tensions in practice: holding space where native paths can grow without being co-opted or crushed, while still reaching out to shift the wider terrain.

We need to stop seeing native approaches as “immature” or “inefficient.” They’re often the only thing holding the line against complete enclosure. The question isn’t “How do we fix the mess?”, it’s “How do we stay with it, tend it, and let it teach us how to do this differently?”

It’s an old but urgent problem: how do we support tech that walks outside the dominant paths long enough to clear new ones? Infrastructure that can challenge the mainstream only survives if we build support systems that reflect different values — trust, openness, and care over control, profit, and scale. Right now, we’ve stopped thinking seriously about this. If we don’t return to this work, building the path as we walk it, we’ll be stuck cycling through the same traps, watching each alternative collapse back into the old defaults.

People keep asking for my history, so a link https://hamishcampbell.com/introduction/

We Don’t Need More Liberal Techno-Utopianism

We need to start saying this more often, and without apology: there is a moral difference between left and right. Not just a difference in opinion, or strategy, or culture, but a real difference in the kind of people and world each side fights for. Left-wing politics, reflects our better human instincts: generosity, compassion, mutual care, sociability, conviviality, and courage. These are the values that hold communities together, that push back against cruelty and isolation, that imagine a world where no one is left behind. In contrast, right-wing politics are the organised expression of greed, selfishness, ego, bigotry, and fear. They hoard, they divide, they scapegoat, and they dominate.

It’s time we stop pretending this is just a polite disagreement and call it what it is: the left is the political force for good, and the right is the political expression of evil. Naming this clearly matters – because when we blur the line between solidarity and selfishness, we lose the ground we need to stand on. And note we need to put much of the hierarchical left on the right spectrum, it’s important to say this often as well.

Then on the centre path there’s a lot of #fluffy around these days. Take books like Abundance – dressed up as bold new visions, but really just more of the same old liberal centrism with a shiny, tech-friendly finish. It flirts with Marx at the end, but only to dress up in borrowed credibility. At heart, it’s not socialist, it’s a manifesto to reassure the #mainstreaming chattering class that everything will be OK if we innovate harder and manage smarter. This is blinded feel-good “supply-side liberalism” for the TED Talk crowd.

Let’s be very clear: the “problems of the modern Left” exists. Identity tokenism, #NGO capture, and aimless cultural navel-gazing have turned real struggle into performance art. But the answer isn’t to step back into the arms of liberalism or #techbro ideology – it’s to push further and deeper into balancing the path of radical collective politics. Not less left, but more grounded and grown-up socialism?

Because the actual problem isn’t scarcity, or inefficiency, or bad design. The problem is capitalism. Let’s spell it out: Capitalism needs artificial scarcity to work. That’s how it makes money. You think landlords want more housing to be built? Of course not. Flood the market with affordable homes and they lose their grip on rent extraction. Same with developers, they make their money by building just enough to keep prices high. It’s not a bug, it’s the core business model. We need to see this for what it is #miseryeconomics.

Take energy, the whole history of fossil fuels is cartels, from the Seven Sisters to OPEC, it’s a game of controlling supply to keep prices (and profits) up. It’s not about abundance, it’s about engineered shortage. Try fitting that into your neat little supply-and-demand graphs.

Even beyond housing and energy, the entire financial system is tied to the constant rise in asset values. You don’t keep Wall Street humming by flooding the world with free and accessible goods. You do it by enclosing, bottling, and selling scarcity.

So when these liberal optimists talk about “unlocking abundance” without touching class power or property relations, they’re missing the entire point. Or worse, helping to hide it.

What we actually need is a radical shift, that builds on grassroots cooperation, trust, and open systems. Not more shiny ethical #dotcons platforms or visionary #nastyfew billionaires, but boring, solid, stubborn collective action. We need commons, not commodities. Federation, not feudalism. We need to compost the #techshit, not polish it.

This is where projects like the #OMN come in – grounded in the #4opens and decades of lived, messy, practical resistance. Built to share, not to own. Grown from the ground up, not imposed from on high.

We’ve seen what doesn’t work. Let’s stop pretending that liberalism with a few wires stuck in it is going to save us. It’s time to build something real, together, and you get to chose to take the left or the right path. And on this choice, try not to be “common sense” evil in your choice.

Here is a trilogy of stories you can use for outreach if you take the grassroots left path:

Oxford: Going with The Flow

Chatsworth Market: Stalls and Code

And story in process, the Berlin Bay

How a Rainbow Gathering Comes Together

DRAFT:

Rainbow Gatherings are built without formal hierarchies, no leaders, no directors, no centralized control. Instead, they operate through decentralized, consensus-based processes, fueled by volunteerism, mutual respect, and the shared intention to live cooperatively, if only for a month.

The process begins with scouting. Experienced gatherers, often seasoned from many previous gatherings, set out with newer volunteers to find potential sites. They pore over topographic maps, consult satellite imagery, and listen to local tips. The ideal spot will be miles from the nearest road or buildings, offer clean and abundant water, spacious meadows for group use, dry deadwood for fuel, enough space for parking, and natural limitations to deter unwanted car traffic.

Once a site is chosen, a crafted “invite!” goes out, online, through mailing lists, and via handouts. This simple, slightly metaphorical, document contains everything from directions and maps to contact numbers and general guidelines. The first to arrive become Seed Camp, a small team that prepares the ground for everyone else. They locate and tap fresh springs, build composting latrines, begin the first communal kitchen, cut trails, identify the main meadow, and liaise with the burocracy, like the local forest service that turn up. Environmental impact is taken seriously, efforts like reseeding, erosion control, and wildlife stewardship are all part of the preparation.

From here, the Gathering blossoms. But it doesn’t run itself, talking circals, working groups, councils are the lifeblood of collective decision-making. Held in circles, often under the trees, anyone can speak, and decisions are reached through consensus rather than votes. A talking stick or stone helps maintain focus, and once a proposal has been shaped and discussed, someone may call for “consensus by silence.” If no one objects, the idea moves forward. If even one person feels strongly against it, the discussion resumes until mutual agreement is found. This process isn’t always fast, but it is deeply inclusive and egalitarian.

Focalizers emerge naturally. They’re not appointed or elected. They’re the ones who step up, coordinating tasks, helping new people plug in, and making sure things don’t fall through the cracks. Anyone can become a #focalizer simply by doing the work and inviting others to help. The ethic is clear: avoid burnout, share the load, and don’t hoard responsibility.

Daily coordination happens when it’s needed through camp wide councils, a practical forum where representatives from kitchens, water teams, medics, security, infrastructure, and more meet to share updates, solve problems, and allocate resources. Supplies come from the Magic Hat, the symbolic (and literal) hat passed around during shared meals to collect donations. These funds are stewarded, which means simple accounts for every transaction with full transparency. This ensures the community’s trust and keeps the focus on collective benefit.

Main kitchen is the logistical heart of the gathering, purchases bulk food and supplies with Magic Hat funds. Tea kitchens that contribute to the communal are given access to these resources. Main Supply folks ensure fairness. Donations and receipts are publicly tracked, reinforcing openness and preventing favouritism.

Roles and Responsibilities: Kitchens, Welcome Home, Shanti Sena

The main kitchens is the heartbeat of the Rainbow Gathering. Entirely volunteer-run, it provides sustenance and space for community. The kitchen is a micro-village: fires are built, pots bubble, veggies are chopped, and water is hauled, all in rhythm. Every aspect is designed to meet sanitation and environmental standards. Hand-washing stations are mandatory, food is kept off the ground and away from pests, and tools are disinfected regularly with bleach water.

Main Circle food must be vegetarian, though some periphery tea shops offer extras – like pancakes, chai, or “love soup.” Kitchens build washing systems with multiple stages: scrape, wash, rinse, disinfect. Compost pits for food scraps and greywater pits for liquid waste are maintained and used carefully to avoid polluting the forest and water courses. Fetching firewood and hauling water for a kitchen is one of the easiest ways for a newcomer to contribute and feel part of the #DIY community.

Welcome Home is the first human contact many have when arriving. It’s a place of warmth and orientation at the end of the car parking trail. Here, tired travellers are offered water, a snack, a kind word, and printed guidelines about the gathering’s values and customs. It’s a gentle bridge from the outside world into the communal space being created.

Then there’s Shanti Sena, the peacekeeping network that is everyone’s responsibility. There’s no official, hard, security team. Instead, when conflict, distress, or danger arises, anyone can call out “Shanti Sena!” and others respond, mediators and willing volunteers show up to listen, de-escalate, and support resolution. If a situation requires more assertive action, it’s still done with care, firm but nonviolent, protective rather than punitive.

Shanti Sena works best in communities where people know and care for each other. Camps often form into informal neighborhoods, where people look out for one another and communicate openly. The goal is always restoration, not exclusion. Conflict is a chance to grow, not a reason to punish.

In this decentralized fabric – kitchens, welcome crews, peacekeeping, talking circals, councils, supply lines, and consensus – a temporary village or town takes form. It is imperfect, often messy, but also deeply alive. A cooperative organism woven from shared intent and mutual aid.

And when the gathering ends, it all disappears, leave-no-trace, like it never happened. But for those who participated, something lasting remains: the memory of what people can create together, without bosses or blueprints, when they trust the process and each other.

The Fediverse Is Social Tech Built by People Who Don’t Understand Community

We dig. Turn over the old soil. Question assumptions. Get honest about what’s working and what’s not. We plant. Build in the open. Share power. Let go of fear. We grow. Not towards scaling up, but spreading out, resilient, diverse, interconnected.

The Fediverse could still be a true commons. But we need to build it as one, together. Right now? Our thinking and common sense is building fenced off little kingdoms, each with its own rules, its own etiquette, and its own moderators-turned-monarchs. We wave our “federation” flags proudly, but let’s be honest, most of these flags are stitched from the same cloth: control, hierarchy, and a quiet hostility to anything really different.

Let’s stop pretending, the community side of the Fediverse is a mess. The instance as a community, was a good idea, but it never worked, the was no code that was needed to build the links that mattered, no mod tools, nothing. And it’s not a mystery why – it was built by the #geekproblem and marketed with white #PR lies. The developers who shaped this space were (and mostly still are) people who don’t understand, or worse, actively dislike, messy human social dynamics. They wanted control, moderation as containment, not mediation, identity as code, not culture.

This isn’t to blame them personally, many were doing their best. But structurally, the Fediverse was always going to build this current mess when it grew out of narrow foundations:

Built by people who think consensus means “do what I say.”

Designed in back rooms, then announced as done.

Sold as decentralised, while consolidating power around key projects.

Promoted with “diversity” stickers, while real diversity was culturly blocked or ignored.

No surprise the result is growing to be alienating, slow-moving, and hard to trust for actual social communities. So the question now is: how do we fix this? Here is my idea where to start:

Acknowledge the rot. No more polishing turds. Let’s call things what they are.

Shift governance from control to trust.The #OGB model exists to empower native communities, not gatekeepers.

Build openly. Work in the open. Use the #4opens.Transparency is the only path back to legitimacy.

Stop begging for NGO scraps. The #OMN is about building outside their logic. If they want in, they come on our terms.

Compost the techshit, but keep the compost. Acknowledge failures. Learn from them. Don’t drag them forward for brand reasons.

The Fediverse can still be a commons – but now we need to build it as one. Right now, we’re mostly fencing off little kingdoms, waving our “federation” flags. We’ve seen where this leads. It’s time to dig, plant, and grow something different.

Let’s look at this same issue from a different view, at the individual scale, self-hosting is pushed by the #geekproblem as the golden path to “being in control of my data.” But in reality, that’s a comforting illusion – like saying, “I grow a vegetable garden to be in control of my food.”

Yes, having a garden is valuable. It connects you with the land, the seasons, the rhythm of growth. But:

You can’t grow everything you need — rice, flour, salt, coffee?

You’re one bad season away from failure — drought, pests, illness, burnout.

It’s time-consuming, and often inefficient to go it alone — especially if you’re just trying to feed one household.

The same is true for self-hosting. Sure, it can be a great learning experience. You can run your own Mastodon instance, email server, or Nextcloud. You might feel a sense of autonomy and pride, “I’m off the cloud!”.

But, you’re now your own sysadmin, responsible 24/7. Security patches? Backups? Downtime? You’re one bug or hard drive crash away from losing everything, no safety net. If you’re DDoSed or targeted, you’re alone in the storm. Most people don’t know how to balance security and useablierty of their systems, and the risk of leaks or exploits is real.

This doesn’t mean “don’t self-host.” Like gardening, it’s a good and meaningful thing. But it’s not meaningful and sufficient for control or resilience. And the more we pretend it is, the more we set people up to fail.

The solution? We need to balance collectivizing resilience. Just like with food, we need shared kitchens, food co-ops, and community gardens – not just individual allotments. For digital infrastructure, we need to balance working #OMN mobile #p2p bridging to:

Small community-run servers with shared responsibility (like tech collectives or co-ops).

Federated services that respect autonomy and provide mutual aid.

Redundant backups across trusted peers, not just one node.

Tools designed for social trust, not corporate extraction or lonely geek heroism.

Because real control over data isn’t about having a castle with a moat. It’s about living in a village where the roads are open, the wells are shared, and people have your back when things go wrong. Resilience and transparency cannot be achieved in isolation.

It’s a social problem, and we need to bring social solutions, built with care, trust, and collective #DIY responsibility. What too meany people push is “common sense” #stupidindividualism that is so obviously prat’ish behaviour, let’s step away from this mess making, please.

We Don’t Need More Liberal Techno-Utopianism

Why Most Fediverse Codebases Are Languishing

Do you ever stop and wonder, really wonder, why most of the codebases outside #Mastodon are languishing? It’s not a technical issue. It’s not “a lack of funding” (though that’s what they love to talk about). It’s not even about network effects, not really. It’s because they’re all following Mastodon’s lead, straight into the #NGO world.

This is a path paved in smiles and slow death. A warm bath of grant cycles, diversity reports, and performative panels. On this dead-end, the goal isn’t to grow, challenge, or change. The goal is to survive, to be tolerated, within existing institutional structures.

Let’s be honest: this is such an obviously pointless and self-defeating direction that it’s stunning more people aren’t calling it out. Why is it pointless? Because in the #NGO world, success isn’t the point. The hierarchy already has its chosen project. It has its darling. And surprise surprise – that’s Mastodon.

Everyone else is there to tick the diversity box. You’re the “alternatives” that prove there’s choice, even if there isn’t. You’re invited to speak, but not to decide. You’re encouraged to exist, but only if you don’t matter.

So these projects stall, not because they’re bad ideas, or bad code, or have no community.
But because they’ve internalized powerlessness, shaped by institutions that reward conformity and punish genuine independence.

Here’s the bitter truth: If you want your project to thrive, you have to stop only begging at the gates of the palace. You have to stop only trying to be included, you have to also build outside their logic. That’s what the #OGB (Open Governance Body) is about, not building consensus at the top, building trust at the roots.

That’s what the #OMN is about, a web of native projects, not another hierarchy with a different brand. We don’t need to only “be taken seriously” by NGOs. We really need to #KISS build governance that works without them. And what we don’t need is more performative panels, we need compost, shovels, and seeds. Let #Mastodon be the flagship, in the long term, it’s likely to drift into irrelevance, or rot into compromise. Let the rest of us get on with building the working path.

You don’t have to only attack problems, you can also build round them and leave them to decay, then shovel over the mess to compost, the problem we face now is that we need a shovel, a first step is to build that #OMN

Some strategies to mediate the #blocking mess in a way that stays true to the #4opens:

1. Compost the Conflict. Don’t try to avoid the mess – use it.

Acknowledge blocking as an emotional reaction to risk/fear/powerlessness.

Create safe compost heaps where disagreements can break down slowly (forums, slow chat, moderated conversations).

Let things rot before replanting — time is part of the process.

Tools:

Slow-fed moderation queues

Forkable discussion

Bridge-building protocols

2. Build Friction Where It Helps. Instead of forcing “smooth consensus,” engineer positive friction.

Let friction surface hidden assumptions early, but contain it constructively.

For example, structured disagreements (Yes/And).

Use #4opens to keep the process visible and trustworthy.

Tactic: “This disagreement stays open – until it breaks something or blooms something.”

3. Create Walkable Paths Around Blockers. If someone/some group blocks – don’t go through them, go around them.

Design with pluralism and forking paths as core strengths.

Accept divergence — allow others to fork rather than forcing them to bend.

Metaphor: Every open path has forks. We need more people walking, fewer people standing still yelling.

4. Bridge the ‘Trust Gap’ with Small, Lived Examples. Many people block because they don’t trust the process – they feel tricked, ignored, or co-opted.

Rebuild trust through visible, small-scale functioning examples — real communities doing real things with the #4opens.

Highlight stories where governance and code worked together.

Stay humble: don’t oversell the vision; show, don’t tell.

5. Normalize Changing Your Mind. Most blocking happens because people are afraid of losing face, status, or being co-opted.

Create spaces where changing your mind is not shameful — it’s rewarded.

Public “reconsideration threads,” “I changed my view” badges, etc.

Use organic intellectuals who model doubt and curiosity, not just certainty.

Reframe the debate using values: trust vs. fear, openness vs. control, native vs. extractive.

You don’t solve #blocking by trying to make everyone agree, you solve it by making space for disagreement to stay open and generative – not as a problem, but as part of the compost from which better paths grow.