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

What is it that blocks this needed change and challenge? #Geekproblem is about when the “solution” Is the problem. One of the most frustrating things is how often its defenders mistake their narrow fixations for universal solutions, or worse, offer them up in bad faith to derail the real conversation.

You’ll raise an issue – social, political, cultural – and instead of engaging with the messy, human, collective work needed to address it, the geek brain rushes to replace it with a neat technical patch. The tool, the workflow, the protocol. As if the complexity of human trust, governance, and solidarity can be debugged into submission.

This isn’t just misunderstanding; sometimes it’s sabotage. By framing the “solution” purely in terms of tech or procedure, they strip the problem of its social and political context. What remains is something sterile, depoliticised, and ultimately unfit for purpose.

It’s why I keep bringing this up. Because if we don’t name the #Geekproblem for what it is, we’ll keep circling in the same loops, patching over social fractures with shiny but hollow code. The answer isn’t more complexity; it’s #KISS – Keep It Simple, Stupid. Simple in the sense of clear, human-first, and grounded in open, accessible processes.

The truth is, solving problems in the #openweb isn’t about cleverness or code alone. It’s about people, and unless the geeks can learn to work with that, rather than overwrite it, they’ll stay part of the problem, the #geekproblem

Please, please try not to keep being a prat about this.

Smiling-faced vileness: How enforced politeness becomes a weapon in grassroots paths

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

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.

Trust is the foundation of moderation in decentralised networks like the #OMN

In the world of decentralised, peer-to-peer, and federated networks, from the Fediverse to grassroots projects like the #OMN, moderation works differently. It’s not a matter of top-down control or terms-of-service written by #process lawyers. Instead, the basic unit of moderation is trust – and this shifts everything.

Yes, we need practical moderation tools – blocking, filtering, reporting, curation – the whole established toolkit. But more importantly, we need to root these tools in a tech shaped culture of care, responsibility, and openness. This is where the #4opens come in:

Open data
Open source
Open standards
Open process

These aren’t #FOSS buzzwords, they’re guides to building (tech) trust in messy, real-world communities. In this path, you don’t have many hard “rights” in the liberal legalistic sense, there’s no authority swooping in to save you. Instead, you build #DIY community “safety” through the act of creating and sustaining relationships of trust. You find people. You then build a crew to join or establish norms and commoning practices.

This isn’t a call to abandon boundaries, it’s the opposite. You draw your boundaries with others and work to hold those, with #4opens bridges in place. You don’t demand control over others, you build spaces that work for you and find ways to federate, connect, and mediate with others doing the same. Your rights are your relationships. Your safety is your crew. Your power is your network.

This is the #KISS path – Keep It Simple, Stupid – agen, not in a naive way, but in a native way. It’s the opposite of the bureaucratic, compliance-obsessed, legal control systems of the #dotcons and the #NGO gatekeepers. Those are alien models people keep trying to drag into our “alternative” spaces and paths. And every time we do, we replicate the very systems we claim to oppose.

A #mainstreming view on this

We don’t need more frictionless tech platforms with “Trust & Safety” departments that answer to advertisers and #PR teams. We need open communities of care, rooted in shared values, transparency, and mutual responsibility. On this path its about working to compost the mess and growing something else.

This is how moderation works in a decentralised network, not by pretending we’re neutral, but by showing up with care and accountability. It’s messier, more human, and it works, when we let it.

On this path, we need a reboot of the #Indymediaback Infrastructure. As a core to reboot the radical media commons. Bring back trust based publishing, peer moderation, and local focus Why? Because #mainstreamin media isn’t neutral – it mainstreams the crisis while making resistance invisible. We need native alternatives.

Why #NGO and fluffy #openweb tech events should include radical real grassroots projects

If you need a working definition of the #geekproblem, it’s the habit, no, the reflex, of putting the social side of tech outside of tech. It’s the behaviour of someone sticking their head in the sand and mumbling, “That’s not my department.”
It’s “I just write the code.”
It’s “We’re neutral tools.”
It’s “Let’s keep politics out of it.”

This isn’t just naivety, it’s a deep, culturally reinforced avoidance of responsibility. And it’s one of the key reasons why even alternative tech replicates the same failures and power structures as the mainstream.

Worse, this behaviour is too often mainstreamed in the alt-tech spaces themselves, turned into best practice by #NGO people who should know better. It becomes active #blocking of any progress on alternative paths. New governance? Too political. Radical accountability? Too messy. Grassroots involvement? Too slow. Let’s just build it and hope for the best.

We can’t afford this any more, in the midst of #climatechaos, rising authoritarianism, and the enclosure of digital commons, building better tools without building better relationships, better communities, and better politics is a dead-end.

This is the core of the #geekproblem, and if we’re serious about anything more than shiny toys, it’s something we must talk about at our conferences, meetups, and hackathons. Let’s stop pretending code is apolitical, let’s start with this: tech is social, or it is very likely more wortless #tecshit.

Let’s be blunt, “inclusive” tech/#NGO events talk about change but don’t platform the people doing the hard, messy work of building this path. This is a real problem, rooted in comfort, control, and careerism.

Radical grassroots projects like the Open Media Network (#OMN) exist precisely to challenge the #mainstreaming mess, not to dress it up. We aren’t here to repeat feel-good slogans and deliver polished #PR. We’re here to offer lived solutions grounded in the #4opens and decades of collective, hands-dirty work.

So why should OMN and similar voices be invited in?

We speak from the grassroots, not the conference stage.
We build tools that people have historically used, not just write funding proposals about.
We hold space for #DIY, for #p2p, for real change, not only the reform theatre.

If your event doesn’t include these voices, like almost all of them, it’s the #mainstreaming problem of locking out knowledge, networks, and resistance, which the events #PR claims to support. This clearly makes the people involved into hypocrites.

On a positive, #KISS, this doesn’t need to be a fight, let’s make events better together. Can you imagine real dialogue between grassroots builders and NGO funders? Imagine shared workshops where friction leads to function, messy, honest space that acknowledges power dynamics – and really then starts to do something about this mess.

Want a better event?

Put grassroots groups on the stage, not just in the audience.

Pay people for their time — especially those working outside institutions.

Focus on practice, not just policy.

Drop the gatekeeping.

Build open process into your event — make your own structure accountable to the #4opens.

But, remember, we aren’t going just to play nice, to be seen, we’ll come to compost the status quo, and plant something that might actually grow. Let’s try and maybe do this right, please.

The #nastyfew in the era of #climatechaos and social breakdown

In this accelerating collapse – where #climatechaos spirals and #neoliberalism guts the very idea of society – we urgently need to confront a painful truth: it’s simple, the #nastyfew are a parasite class. And that this class feeds on the very foundations of well-being, survival, and joy that the majority of the global population desperately needs. They are the ones who keep the engines of destruction humming, not out of necessity, but out of greed and fear of irrelevance. These people and their institutions flourish precisely because most of us are lost in the distractions of #mainstreaming and false hopes of reform.

The big picture is Capitalism’s global predation – Zooming out, this is the capitalist class – those who own, hoard, and manipulate the resources, labour, and attention of billions. They weaponise economics, push debt, drive resource wars, and now greenwash their way through #climatecollapse while investing in bunkers and surveillance. They bankroll right-wing populism and push for austerity, while lobby for tax cuts as profits soar.

The close-up: People you might know, zoom in, and things get messier. This parasitic drive isn’t only held by billionaire industrialists. In many cases, it’s people close to us, sometimes unknowingly, sometimes not. These are the minor functionaries of capital, the wannabe gatekeepers, and the careerists who believe that “playing the game” will protect them from collapse.

In tech, it is clearer, parasites wearing hoodies. The Bitcoin Bros: Obsessively libertarian, they fetishise decentralisation while promoting hyper-individualist economics that mirrors the worst of Wall Street. They talk about freedom but build systems of exclusion, greed, and extraction. If you spend your energy pushing #crypto as liberation while ignoring ecological and social costs, you are enabling the parasite class – and likely dreaming of becoming one.

The #mainstreaming talking about this “inside” issue

#Dotcons Executives: The Zuckerbergs, Bezoses, and Musks of the world are obvious examples. But look further down the food chain: the startup bros who pivot endlessly looking for #VC buyouts, the marketing execs who gut communities for ad metrics, the devs who code endless optimisations to squeeze more value out of users. If your business model depends on surveillance, addiction and enclosure, you’re the problem.

The careerist #NGO tech elitists: Yes, even the “good” sector can be captured. NGO professionals who endlessly hold conferences and produce whitepapers while blocking actual grassroots projects. They take seats at tables designed to exclude the people doing real, messy, transformative work. They don’t oppose the #nastyfew; they stabilise their control.

So what do we do? First, see clearly, name the parasitism. Understand that systems don’t just fail; they are designed to benefit the few and contain the many. Second, build bridges away from this mess – rooted in the #4opens: open data, open source, open process, and open standards. This is the beginning of composting the parasite class. Third, support native projects: not the VC-funded copies or the corporate-friendly NGOs, but the messy, local, collaborative tools and networks that build resilience and joy from the ground up. Projects like #IndymediaBack, #OMN, and others pushing against the tide are places to start.

Because in the end, the parasite class only exists as long as we feed it.

Let’s stop, please.

Frictionlessness is a Poisoned Fantasy – an #OMN Reflection

In our current mess of a world, one of capitalism’s illusions is the promise of #frictionlessness, that everything should just work, that all interactions should be smooth, efficient, and untroubled. In tech this is the logic of the #dotcons, keeping the “users” engaged, never give them time to think, and above all don’t let the real world get in the way of the pipeline between their attention and your profit.

This has infected the #geekproblem deeply. In software culture, especially, friction is seen as a flaw to be eradicated. You get endless talk about seamless UX, microservices glued together with endless APIs, “AI” interfaces that complete your thoughts before you’ve had them. But in this drive for “smoothness”, we erase the very stuff that makes us human. Friction isn’t a bug, it’s the thing that matters.

We in the #OMN path think differently, humanistically, friction is where we bump up against each other, where ideas collide, where something has to be negotiated, not assumed. It’s where care, conflict, and collective learning live. Real life and community requires discussion. It forces mutual understanding. It invites shared responsibility. Not only that, but it’s slower – yes. Messier – absolutely. But in that mess, something native grows.

This is the fundamental difference between a society built for people and one built for control. A people-based network has thick edges, blurry boundaries, and rough interfaces, you feel each other. A control-based network is sterile. Optimized. Soulless.

This is what the #deathcult calls “progress”, the drive to strip the world of friction so that each of us can float through our own private consumerist delusion, never encountering anything real. Currently you feel this in the emerging cult of “AI as Everything Machine”, the idea that you’ll never need to interact with anyone ever again. Need something? Ask the machine. It won’t argue, won’t misunderstand, won’t push back. It’ll stroke your ego and reinforce your (their) worldview. It’s like having a compliant servant with no wages, no needs – and no truth.

We are encouraged to see this as liberation. But it’s so obviously the opposite. It’s a deepening of the loneliness machine. This is what happens when we build networks to eliminate community. No neighbours to disagree with, no comrades to compromise with, no community to be accountable to. Just you, “your” machine, and your carefully filtered feed, all controlled by the “invisible” #nastyfew in a feedback loop of isolation.

But, simply put, the real world doesn’t work like that, it is messy. The river floods. The server crashes. The refugee needs a place to sleep. The boat needs fixing. Your project needs people who don’t agree on everything, but care enough to stay and work it out. This is the world the #OMN needs to be built for.

Humanism is not removing friction, it’s mediating it. Friction can hurt, but it also brings growth. It’s how we learn, we feel our need for each other. And yes, how we fight, but also how we forgive.

If we’re serious about challenging the broken paths we’ve been led down – from #neoliberal isolation to techno-dystopian escape – we need to stop chasing the dream of #stupidindividualism, and start building networks that build communities of interest, that touch back. That remind us we’re not alone and push back, gently, when we try in our misery to float away.

Because only in activism – in tension, in movement, in shared resistance – can we build anything real #KISS