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).
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.
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.
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.
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.
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
Most of the mess, and most of the #blocking, comes down to the same old story – ownership and control. Who holds the keys? Who decides? Who gets locked out? Instead of wrestling in that cage, the #OMN takes a simpler path: we walk away.
We put a class of media into the commons, governed openly through the #4opens: open data, open process, open source, and open standards. That means no one can close it down, hoard it, or fence it off for profit. The value comes from the shared pool, not from gatekeeping.
This is the heart of #KISS in the #OMN: make the flows work first, in ways people can understand, and build trust on top of that. The tech exists to serve these flows, not to dictate them. This isn’t about perfect crypto or hard lockdowns; it’s about commoning media so that everyone has the right to read, share, and build on it.
Yes, the #mainstreaming mess will eventually follow us – as it always does. But the plan and hope is that by the time it catches up, the habits, culture, and expectations we’ve grown around open media will have shifted society enough that the old traps won’t work the same way. If we’ve done our job, the default will be more open, collaborative, and accountable, not locked down. That’s the #KISS path: simple, resilient, and grounded in the commons.
On the #OMN with #indymediaback and #makeinghistory paths – We’re not talking about a single bridge, but a federated ecosystem, with the current example of both #DAT and #ActivityPub running on the same server, sharing a common database of media objects. As the data flows, text and metadata are redundantly stored in the open (#4opens). That way, if one server gets hacked, it can simply be rolled back and restored from the wider pool. #KISS
The P2P side works much like #nostr in that it can have a list of flows in and out to servers and can use any of these to publish and receive media on the #openweb. The advantage of the #p2p app side is that each local app in a backup for the online servers (see #makeinghistory), which as critics say can be, and will be, taken down some times. Also, they will work in their own right for people who need a more locked down path, and this will be needed in more repressive spaces and times. The clear advantage is this still gives them outflows to the wider #mainstreaming client server media outreach, to what matters, effect, so it ticks both boxes.
We aim to solve technical issues with human-understandable social paths, not hard tech for its own sake. Yes, in a minority of cases hard tech will be needed – but that’s for the #geeks to solve after the working social paths are clear, not before.
We fix problems through #KISS social processes and #4opens transparency, not by defaulting to encryption and lockdown. Hacking is outside the focus scope of the #OMN. What we’re building is about trust and flows, not code as an end in itself. Hacking belongs on the #geek paths – useful, but only after the trust and flows are established. The code should be there to secure what’s been built, not to block it before it exists.
Without trust and working flows, there’s no value at all, no matter how secure, encrypted, or elegant the tech stack. If the campaigns, activism, and people aren’t using it, the system is pointless. And being pointless is something we need to be more honest about. Building for the sake of building, while ignoring the social, community layer, feeds the #geekproblem and starves the movement.
So, what can people actually do in the real world to make this path happen?
If you have resources, you can help fund the development work – keeping it in the hands of the people actually building the open commons, not some corporate gatekeeper.
If you’re technical, you can code the applications and servers that power the flows. We need builders who understand that trust and usability come first, not shiny tech for its own sake.
If you work in UX or testing, you can make sure what we build is something real people can actually use and trust – simple, clear, and accessible.
If you do media, you can tell the story. Write, film, photograph, blog, podcast – whatever it takes to spread the word. The more people hear about an alternative that works, the more chance it has to grow.
Whatever your skills or resources, the important thing is to get involved in the flow. This is not a spectator sport, and the is unlikely to be pay, it’s #DIY so the commons will only be built if we build it together. #KISS #4opens #OMN
Activist tech has been stuck in “bunker mode” for 20 years, and the only way out is to start building #4opens native, commons-first systems that store, share, and protect movement knowledge in ways that don’t require a priesthood of insiders to operate.
In an active movement, forum threads, shared docs, livestreams, and photos aren’t just chat noise, they’re collective memory. If we treat them as disposable, we throw away the hard-earned lessons that future activists will desperately need. The solution is #KISS-fed, redundant, federated archiving:
All public movement data sits in the commons.
Metadata + content are mirrored across multiple federated nodes.
Backups are easy to pull, restore, and re-seed by anyone who ever has trust access.
Data is grouped via hashtags, not rigid taxonomies, so it flows where it’s needed.
This is appropriate tech: low-complexity, high-resilience, built for social utility first. But for this to grow it can’t be mediated to death by the #geekproblem – code should follow social needs, not the other way round. If we can get this kind of infrastructure running, we stop losing our history, we keep movements porous instead of paranoid, and we finally start building bridges instead of walls.
Let’s look at an example of this: For the #DAT protocol to become relevant in #FOSS activist tech, we need to stop treating it as an isolated island and start building solid bridges to #ActivityPub. The two are not enemies – they are complementary paths. p2p tools and protocols like DAT brings distributed, peer-to-peer file persistence; ActivityPub brings the social layer, discovery, and conversation. Together, they create a space where activists choose their preferred path without being siloed or alienated, and without the unhealthy isolation that comes from the current #geekproblem habit of fetishising one protocol at the expense of all others.
Diversity is the basis of any healthy ecosystem – biological, social, or technological. In nature, monocultures are fragile; in tech, monocultures are authoritarian. We need to approach activist infrastructure with the same principles that make ecosystems thrive: multiple species of tools, cross-pollination between communities, and a constant flow of ideas and resources. This doesn’t mean adding complexity for complexity’s sake; it means designing with #KISS in mind, while ensuring redundancy and adaptability.
If we take this ecological view of the #openweb, then bridges are not optional extras – they are the lifelines. In our example, by linking #DAT and #ActivityPub, we create a richer habitat for movements to live in. We make it harder for corporate capture to take root, and we give people the freedom to move between spaces without losing connection and context. That’s how we replace the bunker mentality with a real commons, not just defensive walls, but thriving, interconnected gardens.
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 tofit 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.
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.
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.
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.
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
If we want to build meaningful alternatives, we must deal with difficult issues head-on. Sweeping things under the carpet – especially in radical spaces – always comes at a cost.
One of the more complex, and often misused, areas is around identity politics, particularly the playing of the race/gender card in ways that obscure rather than clarify the real issues at stake.
Let’s be clear: systemic racism and sexism are real. We all live with the deep, painful legacies of colonialism, patriarchy, and class oppression. These power structures are embedded in our cultures, our institutions, and, yes, in our own organizing spaces. Naming and addressing them is vital.
But sometimes, identity markers are used as shields, not in the pursuit of justice, but to avoid accountability. When this happens, especially in grassroots or activist collectives, it creates paralysis and prevents us from dealing with actual abuse of power.
A real-world example. This happened to me some years ago at a community-run space in Dalston. One person dominated meetings, spoke over others, and made every decision-making process a battleground. It was classic power politics, silencing others through constant assertion and manipulation.
When I finally took responsibility to challenge this, the room froze. Instead of engaging with the issue, some defaulted to “both sides are equally problematic.” Then, when pressure built, he played the race card, asserting that my criticism was racially motivated. No one knew how to respond. The conversation shut down. I became “the problem.” He continued unchecked.
It took 6 months of dysfunction and damage to the project before he was finally removed from collective meetings. In the end, people realised: yes, he was mentally unwell, addicted, controlling, and yes, he had useful skills. But we had all failed to support him and the group because we didn’t deal with the real power dynamics early and honestly.
Hard truths, sometimes someone uses identity-based arguments not as a reflection of structural injustice, but as a way to deflect accountability. When that happens, we can end up with unchallengeable behaviour patterns that destroy collectives from within. This doesn’t mean ignoring or downplaying racism, sexism, or mental health, far from it. It means being brave enough to hold multiple truths at once:
Someone can be from a marginalised background and be acting out of line.
Someone can be struggling with mental health and still be causing harm.
Power politics doesn’t disappear just because it’s wrapped in the language of social justice.
What Can We Learn?
Deal with issues when they come up. Don’t defer hard conversations. Don’t wait for people to burn out.
Support everyone – including people acting out – with clear boundaries, not blanket exclusion or indifference.
Distinguish real oppression from manipulative tactics. It’s not easy, but it’s essential to long-term health of communities.
Don’t collapse into false equivalences – not every confrontation is “two monsters fighting.” Trust your political instincts.
Ultimately, we need to reclaim the messy, complicated work of building trust, of calling in rather than calling out, and of recognising power wherever it appears, even when it wears familiar or “progressive” clothing. We won’t fix any of this with purism or purity politics. We’ll do it by grounding ourselves in collective care, lived experience, and honest struggle.
To use technology as a part of this social change, we need better working with the #dotcons generation. This generation is a mess. No surprise after 20+ years of submission to the #deathcult:
#Neoliberalism hollowed out our economies and replaced solidarity with consumerism. #Postmodernism fragmented identity into a battlefield of individualism over collective action. #Dotcons centralized control, turning the internet into a corporate surveillance machine.
The real question is: how do we break free? Our #fashernistas still dodge this, trapped in cycles of performative activism, #NGO co-option, and endless distraction.
The activist path out of this mess is not more chasing trendy tech stacks or branded illusions of progress. What we need is a grounded, #KISS path forward, #OMN (Open Media Network) to building grassroots, independent media beyond corporate platforms. #4opens for transparency, collaboration, and trust baked into our tech + social governance. And, reclaiming #DIY activism real-world organizing, not just digital spectacle.
At first glance, the #OMN (Open Media Network) might look like a technical project, a collection of code, standards, and protocols. But to think of it only this way is to miss the point entirely.
What we’re building is a social and technological fabric for the #openweb, woven together by shared values and practical needs. Yes, there’s tech, but the tools and standards we develop are not neutral. They lean, by design, toward openness, transparency, collaboration, and grassroots control, the principles of the #4opens.
These standards are not delivered from on high by lone developers or institutional committees. They emerge from the lived, everyday use of technology, from how communities interact, what they need, and how they grow together. They evolve from practice, leading to theory.
The code is nothing without people. The protocol withers without participation.
So, we’re not only building tech, we’re growing a community, and that community gives the technology life. It’s a symbiotic process: the social side shapes the tech, and the tech enables new social formations. One cannot thrive without the other. If you treat it only as a technical solution, it will fail, no matter how elegant the code. If you treat it only as a social project, it will stall, no matter how good the intentions. We have to hold both in balance. In that balance, real change becomes possible.
In this spirit, the #OMN is not just an infrastructure project. It’s a call to those who want to reboot the web from the grassroots up, reclaiming the digital commons from #dotcons and #deathcult systems. Let’s get to build it together, simple, federated, and open.
We all know the current state of independent and grassroots media: scattered, under-resourced, and mostly invisible to the wider public. While the content exists, the connection between producers, platforms, and audiences is too often broken. Meanwhile, corporate platforms like #Failbook, Google, and YouTube work for a few, they continue to dominate how people access and experience media and use this to push down any real radical change.
We need a reset, not by building shiny new silos or reinventing the wheel, but by connecting what already exists into a living network. This is where the Open Media Network (#OMN) comes in. The core idea is to link together the fragments of the #openweb. Rather than replace everything, OMN builds bridges between existing activist sites, blogs, podcasts, and alt media using open standards and simple, low-barrier tools.
The idea is simple: Producers publish content on their existing sites (blogs, podcasts, etc.). Aggregators bring it all together, curating, tagging, and redistributing content through RSS, ActivityPub and metadata flows.
What this means for people is easy discovery of relevant content on the topics they care about. A gateway back to the #openweb – away from algorithmic manipulation and ads. A better browsing experience than siloed social media.
What it means for media producers: Syndication, content appears on dozens or hundreds of relevant sites. More traffic, more engagement, and better visibility without having to chase algorithms. Simple tools to embed rivers of content from others, so you give back to the network while benefiting from it. In short, publish once, appear everywhere, no need to grind content for each individual silo.
Why this works, all content remains owned by the original publishers. The system simply connects and enhances what’s already there. It’s not a new platform, it’s the missing glue between platforms. Why this matters socially, we’ve been burned by both: The #geekproblem of over complication and privacy tunnel-vision and the NGO/foundation/brand-washing of horizontal, activist culture
OMN avoids both by hardcoding openness and cooperation into the foundations, using the #4opens as a social and technical guide. This isn’t a system that can be easily captured or siloed. It’s designed to move faster than co-option, and built for people who want to do, not just talk.
If this sounds old-fashioned, that’s because it is, and it works, we don’t need innovation for its own sake, we need media compost, not just another layer of glossy tech bling. We’re creating the soil for tomorrow’s social movements. Want to help us shovel the #techshit and start planting?
We live in a time of crisis. Climate, community, communication, all are breaking down. Our tools and platforms no longer serve us. To make sense of this, we need to tell stories. And in the digital world, hashtags are one of the most powerful ways we do this. But our hashtags don’t just tag, they trace the roots of our problems, and signpost paths out. Each one is a seed. Together, they are a map.
#dotcons – From #openweb to walled gardens. Once, the internet was a place of openness, built on free tools, shared protocols, and community spirit. Then came the #dotcom era, where profit became the driving force. Platforms like Facebook, Google, and Amazon, what we call the #dotcons, reshaped the web to lock us in and sell us out. A handful of corporations own the highways of our communication, and their algorithms guide what we see, say, and believe.
#stupidindividualism – A trap we set for ourselves, we were promised empowerment. But what we got was individualism without solidarity. We’re told: brand yourself, hustle alone, curate your reality. But without community, there is no resilience. Without cooperation, there is no change.
#stupidindividualism is the cultural poison that tells you “you’re on your own.” It weakens us from the inside.
#deathcult – Forty years of neoliberalism. The last four decades have been shaped by a ruthless ideology, that markets solve everything, government should step back, and people must compete, not care. This is the #deathcult – a term for the deadly logic of late-stage capitalism. It’s taken over politics, media, even our sense of self.
Climate denial, gig work precarity, housing crises, mental health collapse - these are all symptoms.
#geekproblem – The failure of trust in tech. Even our allies, the people building tech to fix things, fall into a trap. The #geekproblem is when developers replace trust with control, more permissions, more encryption, more complexity. Instead of building with people, they build over them. The result? More unusable tools, more silos, more #techshit that ends up needing to be composted in abandoned GitHub repos.
#4opens is a way out of the mess, we need this new paths, based on simplicity, humility, and openness, a compass. If a project doesn’t pass the #4opens, it’s not building for the commons, it’s just making another silo.
#OMN, shovels and compost, we already have the tools, projects that build media flows, not platforms. To connect blogs and podcasts into open rivers of content, using simple tech instead of complicated “Web3” vaporware or #dotcons mess.
We’ve built up piles of #techshit. It’s time to pick up our #shovels, compost the waste, and grow something new.
Hashtags = Soft tools for hard times. We use soft metaphors because we live in soft systems: culture, emotion, trust. You can’t “solve” these with code alone. You need care, community, and storytelling. Yes, many demand hard, scientific “proofs” or “frameworks.” But if someone can’t feel the metaphor, they’re probably not ready for the work of rebuilding. We need to focus on those who can, who’ve seen that a different world is possible.
If you can understand that different ideologies shape different realities, then these hashtags will start to speak to you.
Let’s recap the key tags in the story:
#dotcons – Corporations that own and fence in our web
#failbook – Facebook and its culture of manipulation
#openweb – The decentralized, people-powered internet
#4opens – A compass for ethical, sustainable tech
#geekproblem – Tech that controls instead of empowers
#stupidindividualism – Isolation sold as freedom
#deathcult – Forty years of neoliberalism and its collapse
#OMN – Building networks, not silos
#techshit – All the unusable tools that ignore real needs
#shovels – The work we must do
#compost – Making good soil from past mistakes
We don’t need heroes, we need gardeners, grab a shovel, let’s build a future please.
