There is a point that often gets misunderstood in conversations about the future of the #openweb and #FOSS that #mainstreaming itself is not inherently good or bad. What matters is who is influencing whom. We can think of it in two very different directions.
- Good #mainstreaming is when the values of the #openweb move outward into the wider world: Transparency, decentralization, cooperation, shared infrastructure and community governance. In this case, mainstream society learns from the cultures that grew around free software and open networks. But there is another direction.
- Bad #mainstreaming happens when the mainstream flows inward and reshapes the open ecosystem in its own image. The values that arrive tend to look like this: corporate control, surveillance capitalism, hierarchical governance, branding over substance leading to growth and extraction over community. In this case, the #openweb is not influencing the mainstream, the mainstream is absorbing and reshaping the openweb. And historically, that absorption rarely ends well.
This second bad option of co-option Is the default, in the current context, mainstreaming tends to dilute radical alternatives into market-friendly compromises. This is not accidental, the system many of us are working inside – what I often call the #deathcult of neoliberalism – does not absorb things in good faith, it absorbs them in order to neutralize them.
We have seen this pattern repeatedly when open communities become venture-backed platforms, cooperative tools become monetized services, grassroots networks become brands. What begins as a commons to often ends as a product. For people building or funding #FOSS infrastructure, this pattern should be familiar.
Because of this messy dynamic, we need active mediation when interacting with mainstream institutions. Not blanket rejection, but not naïve acceptance either. The question is always contextual: Is the mainstream being influenced by open values or are open communities being reshaped to fit mainstream power structures? Right now, the balance is heavily tilted toward the latter, which means the priority is not endless integration. The priority is protecting and strengthening the roots of the #openweb.
Thinking about this kinda mess making helps to highlight the problem of the #NGO Path, where the NGO layer becomes problematic. The people involved are sometimes well-meaning, many think they are genuinely trying to help. But the institutional incentives they operate under reshape projects in subtle but powerful ways.
Our #FOSS funding structures push toward professionalization, opaque centralized governance, brand management, risk avoidance that is compatibility with existing power structures. Over time, this acts like a kind of social poison inside grassroots ecosystems. That might sound harsh, but it is simply a reality of social dynamics and institutional gravity. People working within those systems carry those assumptions with them, often without realizing it.
For the health of the ecosystem, we need to mediate our intake of that poison. This is not about demonizing individuals, it is about recognizing structural effects. There is no contradiction in saying both things at once: They may be good people – Their institutional logic still damages grassroots culture. So a useful rule of thumb is simple is don’t drink too deeply from the #mainstreaming.
Visibility Matters – Another issue for #FOSS projects is much more practical – Grassroots infrastructure often stays invisible. If people don’t know a project exists, they cannot adopt it. And when that happens, the public will naturally drift toward the next “ethical” platform marketed by the very companies reproducing the #dotcons model. The difference is that those companies have huge PR budgets. If open projects do not communicate what they are building and why it matters, the narrative will be written elsewhere and it will not favour the commons.
The real value of the #OpenWeb at its simplest, the #openweb path does something very straightforward in that it empowers horizontal, DIY culture and dis-empowers vertical, closed systems. That shift alone has enormous value.
- It changes who gets to publish.
- It changes who controls infrastructure.
- It changes who participates in shaping the network.
Yet one of the strangest things in the current moment is how many people actively reject or ignore this possibility. Part of that blindness comes from habit, part from career incentives, part from the cultural gravity of the mainstream. But the result is the same: the tools that could strengthen public digital space are sidelined in favour of systems designed primarily for profit.
So what can maintainers and funders do? If you maintain or fund #FOSS infrastructure, there are a few practical steps that can help strengthen the ecosystem:
- Fund the commons, not just products. Support infrastructure that serves communities, even if it does not generate revenue.
- Protect open governance. Funding models should strengthen community decision-making rather than centralizing power.
- Support grassroots visibility. Help projects communicate what they are building and why it matters.
- Resist quite capture. Watch for subtle shifts where open projects become shaped by market logic or branding priorities.
- Invest in horizontal ecosystems. The long-term health of the web depends on many small interconnected projects, not a few dominant platforms.
The choice in front of us is the future of the #openweb will not be decided by technology alone. It will be decided by culture, governance, and resource flows. If the current trend continues, open infrastructure will increasingly be absorbed into corporate platforms, #NGO programs, and venture ecosystems.
But there is another path, slower one, messier, more grassroots one. One that keeps the web as a commons rather than a marketplace. Whether that path survives depends heavily on the choices made by #FOSS maintainers and the people who fund the work.
