So how can people try not to be prats about this conversation?

In alt tech there are lots of people doing good, and they are, but this is blinded shifting to doing “good” head down worshipping the #deathcult, this would be kinda OK if they held the bridge to a wider view of “good” but they don’t, they block and obscure there #blocking, this is bad, very bad as in the end the “good” they say they do, is just more mess we need to compost.

The real solution is always to respect and build from the fluffy/spiky debate, not bury it under politeness or pretend blindly it doesn’t matter. #Fluffy brings empathy, care, and bridge-building – vital social glue. #Spiky brings clarity, honesty, and challenge – the fire that keeps things real. Both are needed if a project is to stay alive and #4opens. The moment one side silences the other, the culture starts to rot. The second-best path, if balance isn’t yet possible, is to shift the #NGO-style fluffy language – soften its domination reflex – so it stops sounding like control disguised as kindness. This is where care can evolve into openness rather than enclosure.

The worst outcome is what we’ve already seen too often: blinded narrowness, the slow creep of civility politics that smothers dissent while smiling at best and ignoring then #blocking at worst. It’s silent damage, and it killed #SocialHub, turning what could have been a commons into a small irrelevant gated forum of insiders. You can’t maintain trust by excluding the spiky voices; you can only maintain a hollow sham.

So how can people try not to be prats about this conversation? Start by listening across difference. Don’t pathologize conflict; compost it. Assume that critique is care, not attack. Drop the impulse to manage or “align” others – those are imperial moves. Instead, nurture space for spikiness within shared trust. The goal isn’t harmony, it’s living balance – a federation of tones, not a choir of compliance.

UPDATE: my feeling and experience of this is that these types of people will with blindness destroy what they say they value for the security of what they say they don’t value. The next generation will likely repeat this mess, and the compost will likely rot, as will our environment because little real change or challenge comes from the narrow blinded path this group push. Yes it’s a hopeless mess, ideas to change and challenge this please?

PS. I would like to be proved wrong, this is a real opportunity for a nice group of people to do the right thing.

Admit the mess – don’t polish it. Stop pretending everything’s fine. The blindness comes from politeness and professionalised façades – people smiling while quietly blocking change. Naming the rot is the first act of care. #4opens starts with open process, not spin.

Reignite the spiky energy. Spikiness is honesty, critique, fire – not aggression. Without that spark, the culture flatlines into #NGO sludge. Invite spiky voices back with trust, not fear. Build cultures that can handle disagreement as fuel, not threat.

Rebuild from affinity, not hierarchy. Instead of “leadership” and “representation,” think federation – small, rooted, overlapping networks of trust. The #OGB model (Open Governance Body) can be a path: shared stewardship, visible processes, no invisible power.

Compost the infective NGOs. Use what’s useful (resources, access, tools) but don’t let them define the frame. Their language and logic are imperial – centralising, sanitising. Translate their “professional” talk into commons language: from “impact metrics” to “shared meaning,” from “alignment” to “affinity.”

Re-root culture in lived practice. The grassroots aren’t a romantic idea – they’re the only working base. Real change comes from where people actually do things together, not from panels or “stakeholder dialogues.” Focus energy there, make it visible, and let legitimacy flow upward again.

Make openness the discipline. Openness isn’t chaos; it’s a discipline of trust. The #4opens – open data, open process, open source, open access – are the anti-imperial charter. If a group can’t work by them, they’re not #openweb; they’re enclosure with good PR.

Keep it #KISS simple. Most of the blindness hides in overcomplication – endless frameworks, metrics, governance layers. Keep it small, human, and understandable. Simplicity keeps power honest.

“Your Party” and the Fluffy/Spiky debate – a working path

A wider view of this https://nathanakehurst.medium.com/whose-party-ce23a8099624

Fluffy side: cautious, slow-moving, grounded in “keeping the peace” and managing optics. Classic problem: avoidance of conflict means bottlenecking decisions, blocking energy, and trying to centralise control, so things don’t blow up. Spiky side: impatient, direct, “get it done” energy. Spikiness pushes things forward, but often burns bridges, creating splits and mistrust. Neither path alone works – one stalls out, the other fragments. Their clash in the UK “Your Party”, just tore apart what was an opening for a broad left #mainstreaming alternative which we do need.

There are lessons here for horizontal/grassroots paths, a big one is that centralisation kills: When “leadership” becomes bottlenecked around personalities (Corbyn as “elder statesman”, Sultana as “young firebrand”), it reproduces the same control problems we see everywhere – #NGO capture, careerist gatekeeping, etc. Energy without mediation burns out: Spiky approaches are essential (they break inertia), but without social glue and open processes, the movement shatters.

Sadly, it’s looking like the political vacuum, is back. The 700,000 people who signed up are proof that there is real mass desire for something beyond the #deathcult #mainstreaming. But they’re now “homeless” – with no trustworthy structures to plug into. That vacuum will either be filled by opportunists (careerists, NGOs, “#fashernista”), or open the path for something like the #OMN: messy, federated, not centralised around personalities. And/Or the Green Party (this needs a separate post).

Focusing on the grassroots path I have been working on: this is exactly why the #OMN and #openweb reboot needs balance, so the signal-to-noise ratio can stay healthy. Otherwise, we just mirror the left’s long history of splits. What it means for the fluffy/spiky debate: The “Your Party” implosion shows us:

You can’t fix spiky by being fluffy. The soft style just frustrated allies and deepened mistrust.

You can’t replace fluffy with spiky.

The only path forward is process, not personality. That’s where horizontal projects like the #OMN can work – by creating open, transparent, mediated structures that don’t depend on charismatic individuals at the centre.

For the #openweb reboot, this bad moment is actually what we are working to fix. It shows how much energy there is (hundreds of thousands signing up). It shows the cost of control blindness. Likewise, it creates urgency for native governance paths and experiments in the #fediverse and beyond – where messy affinity-based groups, guided by the #4opens, can provide a home that doesn’t implode around personality clashes.

The question now is who can see the need for the practical mediation layer of the #OMN, is designed to bridge – not abstract theory – it’s the path that makes messy, spiky, fluffy humans work together without blowing everything up. For the #OMN and #openweb reboot, the answer isn’t “less conflict” or “more central leadership,” but better mediation and horizontal process, so collective energy isn’t wasted on repeating the same old splits.

What we are the seeing is the limits of #fashionista and #geekproblem control blindness.

How do we deal with this generation of people – formed by #neoliberalism, #dotcons, #mainstreaming, #stupidindividualism – when what’s needed is collective change and challenge?

The generation of the last 40 years of “There is no alternative” (Thatcher → Blair → Sunak/Starmer) produced passivity and cynicism. #Dotcons capture: people live inside algorithmic bubbles, shaped for consumption, not collaboration. This is the era of individualism as common sense: many can’t even imagine “the collective” except as a threat. We now face naked, fear + distraction: #climatechaos, wars, economic precarity → endless doomscrolling instead of agency. And this is why movements implode: the raw material (people) have been warped by the #deathcult.

What we can work with, even in this mess, people still show hunger for meaning (why 700,000 signed up for Corbyn–Sultana’s thing). Anger at the #nastyfew elitists (but it often gets channelled rightwards – Farage, Trump, Reform, conspiracies).

There are moments of solidarity (mutual aid, Palestine protests, climate camps). Skill fragments (#geekproblem energy, activist culture, DIY practice – but siloed). We don’t start from zero – we start from these contradictions.

Practical paths for dealing with this generation is in part about: Break the spell by expose #mainstreaming as a control system, using simple, repeatable stories (hashtags, memes, metaphors like composting/shovels) to make the invisible visible.

Then the path, affinity first, not mass. Don’t try to herd 700,000 people. Start with small, trust-based circles that actually work. Show results, not rhetoric. This attracts people who are sick of endless talking shops. Compost the conflict, instead of suppressing spiky energy (which turns toxic), build mediation layers, so conflict gets processed into growth. This prevents the inevitable splits from killing projects before they start.

We need working, visible alternatives, things people can touch: #OMN publishing hubs, #fediverse tools, radical media gardens. Each working piece is a counter-spell against “there is no alternative.” This is about reframing success and stop only measuring change in electoral wins or #NGO funding circles. We need to measure it in resilient collectives, working infrastructure, and shifts in common sense.

The challenge we need to compost, is that, the current generation has been trained in #stupidindividualism. What we need to learn is you cannot beat that as individuals, the only path is to recreate collectives – messy, organic, trust-based – where people can unlearn the #deathcult through practice. That’s why #OMN, #OGB, #indymediaback matter: they’re not just tools, they’re containers for relearning collective life.

Looking for an affinity group to take the first step #OMN

The #algorithm on #YouTube has flipped hard right wing for me, a few other people have said the same, please add if you have seen this as well? If this is widespread, it shows how important it is to get normal people back to the #openweb reboot we are all involved in here.

This is obviously a form of social control, with the dominating of the #dotcons platforms in most peoples lives, plain and simple, the price of us building this domination.

The #hashtag story begins with disempowering the #mainstreaming in our own minds. First step: breaking the spell, realising we don’t have to live inside their frame.

Second step: forming the affinity group circle. Gathering with others who can see through the smoke and mirrors. From that circle comes the power to build the #OMN shovel.

Third step: composting. Taking all the #techshit – the failed projects, poisoned cultures, and dead ends – and turning them back into fertile soil. #OGB

What we do with that soil is up to us. That’s where the future grows. #KISS

The #geekproblem only sees #cavetechnology. But society is far too complex for that, you’d have to kill billions to make it work.

4opens is the opposite: a data commons. Light as a tool to fight with, not darkness to hide in.

Thinking outreach of the hashtag story

Commons and the metaphor of “grow a backbone”

With the tyranny of the structureless path, every attempt to share the commons decays into a fog of personalities, cliques, and unspoken power. What needs composting here is that, at best, you end up with a smiling violent man as the backstop of governance.

Without mediating structures, what emerges is not freedom but hidden hierarchy. “Smiling violence” – the agreeable man (or clique) who insists they’re just holding things together – quietly blocks challenge, manipulates process, and reserves the final say. If you’re not paying attention, and can’t move away, you wake to find yourself living in #feudalism, with its ever-present threat of personal violence lurking behind the smile.

This is how “horizontal” spaces rot. They confuse the absence of shared structures with openness, when in fact it is poisoned soil: domination by those most willing to coerce, block, or flatter. Without functioning myths and traditions, shared trust, and open processes, what grows is not commons but personal power, one person’s will, or a small group’s grip.

The smiling violent man is not an accident. He is the inevitable product of structurelessness:

Without flows of accountability, you get bottlenecks of control.

Without mediating trust systems, you get gatekeepers posing as “protectors.”

Without a backbone, you get a backstop, a hard edge of coercion dressed in kindness.

The result: commons replaced by fiefdoms, trust replaced by muscle, care replaced by the mask of “caring the most.” Once that happens, the commons are no longer common, they are held hostage.

When I see this again and again, I sometimes say: “grow a backbone.” But this rarely lands well. So let’s pause and ask what backbone really means in social settings:

Structure / Stability: Like a spine holding the body upright, a social backbone is the framework that keeps everything from collapsing into mush. In #OMN terms: the #5F framework is the backbone, UX, UI, and culture all grow around it.
Courage / Integrity: To “have backbone” means to stand firm under pressure. For movements, this means holding the line when mainstreaming forces, fashionistas, or gatekeepers push back. Backbone is refusing co-option, staying rooted in trust.
Invisible but Essential: The backbone is not the face, not the style. It’s the quiet strength – shared trust and open processes – that allows everything else to move. Often invisible, but without it, nothing functions.

A social backbone, then, is the shared trust + open processes that holds a community upright against both internal decay and external capture. By contrast, on the progressive path the #fashionistas build style without backbone (pretty, but collapses quickly), and the #geekproblem builds bone without flesh (rigid, alienating).

Metaphors work when people use them, this might become convoluted 🙂

The comments brought up some points -When we talk about composting bad process, the stink comes from rot sealed off from air, the smiling violence holding the heap down, suffocating flows. The shovel (#OMN) exists to turn the pile, let oxygen in, keep the ecosystem alive. But the real work is done not by the shoveler but by the hidden actors: the invertebrates, fungi, and bacteria. The slow, distributed, many-voiced work of transforming mess into fertile ground. That’s us, when we build trust-based flow networks.

So let’s think about this backbone metaphor more. In biology, spines give structure, but ecosystems are held up just as much by invisible scaffolding: fungal networks, soil webs, rhizomes. In tech, the Internet “backbone” was designed with redundancy, no single node decisive, everything routing around damage. That’s closer to an exoskeleton or even a rhizome than to a rigid spine: strength through distributed paths, not central authority.

Back to the subject of tech #Mainstreaming likes to tell the story that the Internet came from the Pentagon, born a war machine. There’s truth there. But there’s also the buried history (see APC’s work) of people shaping it into a commons, a tool for organizing, a network not of command but of association. That history is the “invertebrate” path, fragile, messy, hard to see, but alive. And in truth, tech is ideology embodied: the people who built the early net built something that could survive without the state, routing around command and control. That’s a good definition of anarchy.

So the wider metaphor isn’t just backbone, but ecosystem: A scaffold that gives form (#5F of the #OMN as the bones). Shovels to aerate and mediate (#OGB as the process tools). Invertebrates and fungi (the hidden actors – users, trust webs, communities). Rhizomes and redundancy (the net’s anarchic, native design).

The danger comes when we forget this, and mistake surface style for soil depth. The #fashionistas offer flowers without roots, the #geekproblem offers bone without flesh. The commons require both – backbone and compost, scaffold and ecosystem. Otherwise, the heap stinks and collapses into fiefdoms.

The stubborn few who show up with shovels, laptops, and trust

In the tech world of social change and challenge, we’re living with a strange imbalance. Too often, the spaces we use and try and build are crowded with useless, self-destructive prats – people more interested in ego, control, and clout than in making anything grow from the roots. And when they do very rearly act, their “help” is often poison: it blocks, slows, and derails.

At the same time, the number of people doing truly useful, collective, grounded work feels small. You can see this in every grassroots project, tech or activism, whether it’s, coding radical #FOSS projects, building alternative media, running servers, or planting food forests. The people who actually show up and keep things moving are always fewer than we need.

Then into this gap steps the parasites of #mainstreaming. Yes, they look like they’re helping. They reach out, they polish up the image, they “outreach” grassroots tech projects to wider audiences. But under the surface, this isn’t really helping. What they are doing, shifts focus away from what makes grassroots powerful – trust, messy collectives, stubborn autonomy – and towards something glossy and hollow.

Real help doesn’t come from smoothing out the rough edges for palatability. Real help is messy, reciprocal, and based in care. It’s, shipping working code, turning up to maintain the server, to keep the firewood dry, to cook food for the meeting, to argue about governance without walking away. It’s staying rooted when everything pulls you towards the easy path of compromise.

The good news? The work that does happen, when it’s done by those few stubborn and lovely souls who commit to it, is real and lasting. Every #fediverse instance that survives another year, every scrappy #openweb tool that stays online, every cooperative that resists collapse – these are proof that grassroots power is alive.

So yes, most of what gets labelled as “help” from outside is damage. But the grassroots path is still there. If we keep it simple – #KISS – and keep choosing trust over polish, collectives over branding, we can tip the balance back to where it needs to be.

Let’s look at some examples:

#Indymedia worked because it was built on trust, open publishing, and direct participation. But once the dogmatic #eekproblem, the NGOs and professional activists came sniffing, the energy shifted. Gradely the rough edges, the wild openness, became a “problem to be managed” instead of a strength. And with that, the vitality drained.

Or look at the #Fediverse. It thrives when it stays scrappy, with collectives running their own servers and shaping their own cultures. But already we see #Bluesky, #Threads, and NGO-backed “Fediverse Foundations” pushing. They’ll say they’re amplifying the movement. In reality, they’re clipping its wings, taming it for the same #mainstreaming logic that gutted Indymedia.

The #OMN (Open Media Network) was always an attempt to resist this drift. Instead of begging for a seat at the mainstream table, it builds trust networks from the ground up. No gatekeeping, no branding games – just collectives #4opens sharing content, tools, and governance in open, federated ways. It’s not sexy. It doesn’t polish well for a TED talk. But it works, because it stays close to where publishing and power actually happen: at the grassroots.

I’ve seen this first-hand in my own work. On the boats at Rummelsburger Bucht, in affinity groups fighting #climatechaos, and in rebuilding #indymediaback, the same pattern repeats. The parasite #mainstreaming arrive smiling, but what matters is the stubborn few who show up with shovels, laptops, and trust. Those are the people who keep the fire burning. The #KISS truth, it doesn’t take everyone. It just takes enough of us who refuse to give in.

While it’s easy (and justified) to call out the parasitic #mainstreaming types, it’s harder (and more important) to think about how to bridge to them without being captured or co-opted.

1. Meet them on fluffy values, not hard projects. Most #mainstreaming people say they care about openness, creativity, and inclusion. Use those as starting points. Instead of hitting them with #4opens or #OGB right away, talk in simple, human terms: trust, care, mutual aid, freedom. Then show how the OMN already embodies those values with examples like: When talking about #indymedia reboot, don’t begin with federation protocols; begin with “this is a people’s newswire where communities publish, and no single organisation can control it.” Then connect that to the tech.

2. Frame the commons as abundance, not scarcity. Mainstreaming comes with a scarcity mindset (“we need funding,” “we need gatekeepers”). We counter with an abundance story: the #openweb grows by sharing, remixing, and federating. Emphasise that our strength isn’t owning the pie but baking more pies together. An example might be: OMN flows content between blogs, small sites, and #fediverse projects. This isn’t competing with “platforms,” it’s weaving a bigger web where everyone benefits.

3. Offer them low-stakes ways to join. Not everyone is ready to dive headfirst into spiky, fluffy, grassroots culture. Make lightweight on-ramps: federated publishing plugins, easy “flows not silos” demos, or spaces where they can share without having to fully sign up.

4. Keep the tone sometimes fluffy, sometimes spiky. People new to grassroots tech often get scared off by the first bit of conflict. Fluffy spaces – campfires, storytelling, art – can bring them in. The spiky edges – calling out parasitism, blocking #NGO capture – should remain, but not be the only door in.

5. Make co-creation visible. Show them that grassroots projects don’t just “talk” about collaboration – we live it. When people see decision-making without bosses, publishing without gatekeepers, and coding without silos, they realise it’s possible. An example of this can be found in #OMN wiki pages on Unite Forge which are messy, open, and collective. That’s not a bug, it’s a living record of co-creation. Point to that messiness as proof of trust-based work that they can make more “tidy”, this is work as gift.

The #bridgeing isn’t about diluting grassroots culture into “NGO-speak.” It’s about keeping our paths, our politics sharp, while offering ways for curious people to join with less fear. Some will drop off (parasites always will), but others might step over the bridge and become part of the messy, hopeful commons.

#KISS

Looking at working with legacy media thinking – silo vs flow

Every so often I answer the out reach calls from more traditional alt/progressive media orgs, let’s look at some of the very illustrative “common sense” knock backs. The recent examples are Freedom’s reaction and Good Internet’s submission call – As their reaction is useful to illustrate the fault line of “radical publishing” in a federated media path.

Here’s a sketch of how it can (and arguably should) work if we’re serious about, #openweb, and soft-communing infrastructure:

Radical publishing vs content marketing

Linking, promiscuous citation, and remixing are not “self-promotion,” they are the currency of commons media. The #deathcult “common sense” (silo good, linking bad) flips this into “spam” because it serves enclosure. A federated media path re-asserts: to link is to share; the work which is often missing is to normalize this against the #geekproblem hostility.

Federated magazine model

Think of Good Internet or Freedom not as final silos but as temporary, themed hubs: Each issue/edition is an editorial filter over the wider #datasoup. Every piece lives in at least two places: Original home (blog, Fediverse post, OMN node, site). Curated home (magazine issue, zine, aggregator). Citation = federation: linking outward is a feature, not a weakness.

Protocols over Silos

ActivityPub / OMN: an article = Note or Article with links, tags, signatures. Bridging: same content can be pulled into Good Internet’s site, Freedom, an OMN feed, or a #p2p archive. Editorial collectives act as curators, not gatekeepers: they federate, contextualize, and remix.

Radical editorial practice

News vs. Narrative: anarchist/left publishers still to often mimic #mainstreaming news style. But radical publishing can foreground process stories (assemblies, conflicts, federations, mistakes) as valuable. The “native common sense” is that embedded links aren’t a vice; they’re a form of solidarity economy. Columns / paths: rather than stand-alone “takes,” recurring voices build a long-form conversation thread across issues.

Overcoming the spam accusation

Transparency: declare openly, “this piece first appeared on hamishcampbell.com – we federate because knowledge is commons.” Reciprocity: every time you link out, you also lift other projects, so the “flow” is visible. Editorial notes: curators can preface with: “We include links because they build the #openweb – federation isn’t promotion, it’s solidarity.”

Practical workflow (2026-ish)

Write a blog/site piece on your own, or community domain (independent anchor). Publish simultaneously to Fediverse (AP Article). Flag it with #OMN metadata (topic, source, tags). Editorial collectives subscribe to flows/feeds – curate into magazine/zine/weekly digest. Federation tools track lineage: where did this piece appear, when, how remixed. Readers move from curated hubs back to source domains (and sideways to other linked nodes).

Why it matters to anarchists

Free software is political; so is free publishing. Federation prevents capture by the #nastyfew – no central owner can throttle which radical voices appear. Linking promiscuously creates a mutual aid economy of attention, the opposite of platform/silo enclosure. Each zine/collective/magazine is an affinity group node; federation = council of nodes. It encodes horizontalism in media.

So when you bump against “not news enough” or “too self-promotional,” that’s the clash between #mainstreaming editorial common sense and federated radical publishing practice. One assumes scarcity (guard the pages); the other assumes abundance (share the flow).

We do need to compost some of this mess #KISS

Let’s build the shovels: #OMN #indymediaback #makeingstory #OGB

In the reboot of native #openweb media, one guiding principle must be clear: #mainstreaming stays second-rank media. That means:

If you can’t link to a working, open URL, you don’t link.

Any mainstream links are placed at the end of the article, not woven in as authority.

This path is #nothingnew, it’s how we held space before. You can see it in practice back in 2006 with Indymedia’s coverage of the Climate Camp: https://www.indymedia.org.uk/en/actions/2006/climatecamp/

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. For the past five years of the #reboot we’ve been distracted in a signal-to-noise mess from the #fashionistas. That time needs to be over, we need to start looking clearly at both internal rot and the external threats.

A good first step is in balancing the realisation that we actually have far more direct power to deal with the internal mess than we do over the eternal #dotcons and their #closedweb “common sense”. 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. #KISS

I understand the focus on the external #dotcons, yes, we also need 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. It 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.

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

#OMN resources we can support

Drafting blog posts, polemics, and rallying calls to sharpen the #OMN narrative. Use the compost metaphors (#techshit, seeds, soil) into accessible messaging that sticks. Editing to transform the long posts into shareable, short-form content for Mastodon, Fediverse, and allied networks.

Curating and organizing existing #OMN writings into a structured wiki-style knowledge base. Building summaries, FAQs, and primers for newcomers who hit the projects cold. Draft “composting guides” – how to deal with #blocking, #fashionistas, and #geekproblem inside communities.

Writing simple documentation for the Unite Forge and other #OMN tools. Helping draft roadmaps that explain what’s built, what’s missing, and what needs contributors. Produce explainers on why #OMN is different from #dotcons and #NGO capture, grounded in #4opens.

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.

Coding work https://unite.openworlds.info/explore/repos

Funding work https://opencollective.com/open-media-network

Thinking work https://hamishcampbell.com

Who are the #nastyfew?

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.

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.

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.

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.

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

People destroy things they love, not from hate, more from possession

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:

#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.

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

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

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

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.

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.-

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/