Everywhere we look – what we see, touch, and use – we are living inside systems shaped by decades of economic and technological assumptions. This isn’t only something happening “out there”. It has been normalised and internalised over the last forty years.
The dominance of #stupidindividualism, combined with rigid economic dogma, influenced how we design technology, how we organise communities, and how we imagine progress itself. The outcomes are now starkly visible: #climatechaos, social fragmentation, and a weakening of collective sense-making.
The internet reflects this reality. Online and offline are no longer separate spaces; they feed back and reinforce each other. Recognising this isn’t only about blame, it’s more importantly about understanding the terrain we’re all navigating. These are the technology limits of the current path and why we continue to repeat familiar patterns. New platforms emerge, new interfaces are launched, yet the underlying values remain unchanged. The result does feel like endless churn to people who notice, innovation that rearranges surfaces while leaving deeper structures intact.
This isn’t simply the fault of individuals or communities. Many developers, especially within #FOSS and the #fediverse, are actively trying to build alternatives. But the broader ecosystem still pushes toward centralisation, scaling, and extraction because those are the dominant incentives of the wider paths.
So recognising our #geekproblem isn’t about rejecting technical culture – it’s about expanding it. Technical excellence alone cannot solve social problems without grounding in alt collective needs and lived social realities. This is what the #openweb means, it’s more than #blinded nostalgia for the early internet. It represents a shared direction many communities are already moving toward.
The #openweb is an internet where #4opens information is accessible regardless of platform or location, content can be shared, linked, and reused, participation is not gated by proprietary control. It’s basic: open data, open source, open standards, and open processes.
The growth of the Fediverse demonstrates that alternatives like these are possible. Decentralised social networks, community-run servers, and cooperative governance models show glimpses of a healthier digital ecosystem. Yet within these paths, tensions remain between “native” grassroots values and pressures toward #NGO #mainstreaming and power politics institutionalisation.
For this space to grow, we need to keep moving beyond false choices. On institutional paths, many proposed solutions focus solely on regulation or institutional reform, imagining that better rules will fix systemic problems. While governance matters, relying exclusively on top-down solutions risks becoming another form of dependency to add to the mess.
Another path exists alongside institutional change: horizontal, grassroots approaches rooted in #DIY practice, #4opens shared infrastructure. This path is imperfect and often messy, but it keeps agency within communities rather than outsourcing change to distant structures.
The goal is not purity, it is balance, the #OMN approach grows from this perspective. Grassroots, #DIY, non-corporate, human-scale, not disruption for its own sake, not scaling driven by venture logic. Instead, building social technology that serve collective needs while respecting individual agency. Many people within #FOSS and the Fediverse are already working toward these goals, even if they use different languages. The opportunity now is to deepen collaboration, connect projects that share values, and strengthen the social foundations alongside the technical ones.
So the path we need is about finding each other, it’s the path we made work for a while then failed on socialhub, so I need to repeat, the question isn’t whether alternatives exist, they do. The challenge is finding alignment among people who are already trying to move in similar directions, but feel isolated or fragmented.
Who recognises that technology must serve communities rather than extract from them. If you see value in grassroots, cooperative approaches to technology – if you believe the #openweb is still worth building – then the invitation is simple. Stop churning, start building. Who is ready to move beyond endless reinvention toward shared infrastructure and shared purpose?
Seeds, Safety, and the Chicken-and-Egg Problem – A Q&A on Practical Building vs Intellectual #Blocking. This explores a recurring tension in grassroots technology projects: the gap between practical historical paths and fresh “intellectual” critique, it reflects on a broader patterns seen in #openweb, #FOSS, and #DIY spaces.
Q: What is the “shared path” and why describe it as a seed?
A: The shared path is a practical response to repeated historical failure. It is not a finished solution, a moral demand, or a complete alternative system. It begins as a seed, something small, imperfect, and grounded. If you judge a seed by whether it is already a tree, nothing will ever grow. The idea is to start building despite uncertainty and allow structure to emerge rooted organically through practice.
Q: What is the main critique of this “seed” approach?
A: Critics argue that metaphors like seeds and growth avoid addressing concrete mechanisms. They focus on first-step effects: What signals are being sent? Who carries risk or unpaid labour? What moral pressures are created? What happens when survivability is deferred? From this perspective, issues must be addressed at the beginning rather than grown from the seed.
Q: Why does this debate often become circular?
A: Because both sides are asking different questions. Practical builders ask: Where do the resources come from to implement safety before anything exists? Critics ask: How do we prevent harm if we begin without safeguards? Without answering the resource question, discussions loop endlessly between ethics and feasibility.
Q: What is the “chicken-and-egg” problem here?
A: Many grassroots projects face a structural paradox: You need resources, tools, and commitment to build sustainable alternatives. But those resources only appear after something exists and demonstrates use value, agenst mainstreaming pushback Waiting for perfect conditions prevents starting; starting without resources has risks, but it’s the only thing that can grow change and challenge.
Q: What work is actually happening in practice?
A: Practical work often remains messy, distributed, and unpaid. Examples include: Supporting student journalists in rebooting grassroots media projects like Oxford #Indymedia. Motivating unfunded technical communities to collaborate on shared codebases such as #indymediaback. Maintaining ongoing organisational and community infrastructure through long-term volunteer labour. These efforts are naturally invisible and impossible to summarise because they work organically rather than following formal project structures.
Q: Why is documentation itself a source of conflict?
A: Critics ask for clear summaries or structured documentation of ongoing work. Builders simply see this as additional unpaid labour imposed on already stretched contributors. External demands that assume others should organise information for them, creates friction between expectations of accessibility and the working realities of #4opens and #DIY grassroots work.
Q: What role does #DIY culture play?
A: In #DIY culture, participation is active rather than observational. If someone believes something needs improvement – documentation, tools, funding guides – the expectation is that they step in and contribute rather than stand outside only pointing critique. Critique without participation is too often lazy negative pressure rather than constructive help on “native” DIY paths.
Q: Is this simply a disagreement about ethics?
A: Not entirely. Both sides often share ethical concerns. The deeper disagreement is about sequence: Should, impossible and irrelevant in a practical sense, safety and compensation frameworks exist before building begins? Or can these frameworks emerge better through #DIY messy real-world working practice?
Q: What is the takeaway?
A: Grassroots building requires balancing, ethical awareness and practical starting points. Intellectual critique can help identify risks, but when detached from material constraints it too often unintentionally blocks action at best or turn into trolling at worst. Likewise, practical work can benefit from reflection, but cannot wait for perfect theoretical clarity.
The challenge is to compost both approaches into something that moves forward.
