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:

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.