The expertise problem

Technical expertise matters, the problem begins when technical expertise is treated as the only legitimate way of understanding a social problem. This is the trap of technocracy: taking a useful tool for understanding parts of the world and turning it into a complete worldview. The expertise problem “We need more technical expertise in government.” But that is half the answer. The mistake is to jump from “politicians need technical expertise” to “technical experts should make decisions.” That replaces one form of stupidity with another.

A functioning society needs engineers, scientists, programmers and researchers. But it also needs historians, sociologists, artists, carers, journalists, workers, communities and ordinary users Technical knowledge is one tool in a toolbox, it is not the toolbox.

We have seen the consequences repeatedly. Politicians who barely understand how the internet works are expected to regulate it. At the same time, technology companies and technical communities assume that because they understand the machinery, they therefore understand the society surrounding it. Neither position is good enough – we need technical people involved in politics and governance, but we also need those technical people to understand that engineering is not governance.

The #geekproblem hashtag is particularly important part of the story for the #openweb. A lot of contemporary technology culture has inherited a blinded belief that social problems can be converted into technical problems: if something is messy, build a perfect system, when people disagree, write a protocol, when something is unsafe, add security. If information is difficult to manage, build an algorithm, when people behave badly, moderate them automatically. If a community is struggling, optimise the workflow. Sometimes these things are useful, but often the “technical solution” simply hides the social problem.

The problem isn’t that geeks are bad people. It is that technical culture can become too comfortable with abstraction. People become numbers, communities datasets, politics optimisation. Relationships become networks, trust becomes authentication and participation becomes a user interface. And suddenly, we have designed a technically elegant system that nobody actually wants to live inside.

This is the deeper danger of #technocracy, it is not simply about having too many computers, engineers or technical experts. It is about turning technical expertise into political authority. The idea has been around for a long time. During the crisis of the 1930s, technocratic movements argued that society could be managed by scientific and technical experts rather than through the messy processes of democratic politics. The appeal was understandable: when society is in crisis, efficiency, certainty and expertise can look much more attractive than disagreement, compromise and uncertainty.

But that is the problem – democracy is messy because society is messy. There is no technical system that can contain all the values, histories, relationships, conflicts and experiences of the people affected by a decision. The belief that a small group of people with enough information can simply calculate the correct answer is not an escape from politics, it is politics disguised as engineering.

We can see the same problem emerging in our own technology culture. Silicon Valley has presented itself as being above politics: just build the system, scale it and let the technology solve the problem. But these companies have accumulated enormous economic and political power precisely because their systems shape how people communicate, work, organise, consume information and understand the world. Technology is therefore not neutral infrastructure, who owns it matters – who controls it matters – who funds it matters – who writes the rules matters – who has the power to change those rules matters. And what happens when the system is wrong matters.

The danger becomes serious when technological power and political power start merging. A technology billionaire does not become democratically accountable simply because their company operates critical infrastructure. A powerful algorithm does not become legitimate because it is technically sophisticated. A government does not become more democratic because it uses AI. Technology can be used to amplifie power without making that power accountable.

Technologies of humility

This is where the idea of technologies of humility becomes useful: technical and policy systems need to take uncertainty, ambiguity, vulnerability and the limits of knowledge seriously. Four principles might be useful.

Framing

How are we defining the problem? Are we actually addressing the problem, or simply addressing the part that is easiest to measure? This is hugely important in #OMN development, if we define the problem as “How do we distribute content efficiently?” we will build one kind of system. If we define it as “How do communities maintain trustworthy shared media and social memory?” we build something very different. The technical architecture follows the social framing.

Vulnerability

Who gets hurt by the solution? A system can be efficient and still be destructive. Algorithms can optimise engagement while making people miserable. A moderation system can reduce abuse while silencing marginalised voices. A security system can protect one group while excluding another. We need to ask: who is missing from the path?

Distribution

Who gets the benefits? Who gets the power, the money and who carries the risks? This is one of the most important questions in technology because “innovation” is rarely distributed equally. The #dotcons have become good at extracting value from social relationships while presenting the resulting technology as neutral infrastructure, it isn’t neutral. The ownership model matters, governance matters. The #4opens matters because it tries to move these questions into the open.

Learning

What happens when we are wrong? This may be the most important principle of all, there is rarely one perfect answer to a complex social problem. We need systems that can learn, not simply systems that can scale. This is one of the reasons #OMN is interested in things like moderation, rollback, metadata, federation and open governance. A social system needs mechanisms for correction, needs to be possible to say “That didn’t work. Let’s change it.” without treating the previous decision as sacred.

We need to understand that open systems need more than code, you can have beautifully engineered open-source software running a terrible social system, a decentralised network full of authoritarian communities, transparent code supporting opaque power, and you can build technically open systems that are socially closed.

So the challenge isn’t simply – how do we make the technology open? It is, how do we make technology part of an open social process? That is a much harder question, and much more interesting and why #OMN is deliberately messy.

The #OMN approach isn’t to pretend that we can design the perfect social system in advance. It is to build enough open infrastructure for communities to experiment, disagree, adapt and learn. That means accepting that different communities will do things differently, while providing common building blocks that allow different paths to develop – different interfaces, different workflows, different communities and different forms of participation. It means designing for disagreement rather than pretending disagreement can be engineered away, a path from technical systems to social infrastructure.

Composting the current mess is where the critique of tech authoritarianism connects directly to the #geekproblem, it is the problem of expertise becoming authority without accountability. And the answer is not to remove technical people from decision-making. Quite the opposite. We need their knowledge. But we need it alongside other forms of knowledge and inside democratic, open and accountable processes.

Engineers can tell us what a system can do, but they cannot, by themselves, tell us what society should want. Programmers can design protocols, but they cannot decide what relationships a community should have. Data scientists can identify patterns, they cannot determine what those patterns mean to the people living through them. And AI can process enormous quantities of information, it still cannot replace human judgement, lived experience, disagreement and democratic legitimacy.

This is why #4opens + #OGB + #OMN + #MakingHistory belong together, attempts to build technical infrastructure that leaves room for social intelligence rather than replacing it. To repeat endlessly the path is not one perfect platform, one perfect algorithm or one perfect governance model, #KISS we need more tools, not one answer.

On this native path, mess is not necessarily a failure, it can be the space where learning, disagreement, adaptation and democracy actually happen. That is a much humbler – and potentially much more powerful – ambition.

#OMN #openweb #4opens #OGB #MakingHistory #FOSS #geekproblem #technocracy #technology #governance #commons #socialmedia #decentralisation

The blocking happens when criticism becomes a substitute for action

There is an important argument within environmentalism that often gets lost between the lifestyle politics of the light greens and the anti-industrial politics of the dark greens. It is humanistic green environmentalism – the idea that ecological sustainability does not require us to abandon technology or progressive modern life. Instead, we need to radically redesign the systems that produce them. Humanistic green thinking is about bringing humanity’s ecological footprint within the limits of the planet while improving the quality of human life.

Light green environmentalism turns ecology into a lifestyle choice: buy the right things, recycle, consume less, and make better individual choices.

Dark green environmentalism goes further, arguing that ecological destruction is built into industrial capitalism, growth, consumption and production. Technology is treated with suspicion, and dark-green traditions argue for degrowth, radical reductions in consumption, or even a retreat from technological civilisation altogether.

Humanistic environmentalism takes another, balanced path: we need radical systemic change, but technology and design can be part of the solution rather than simply being part of the problem. However, this approach can create another problem: #technocracy.

Technocracy is the idea that complex social problems can be managed through expertise, scientific evidence, measurement, efficiency and technical rationality. In its strongest form, political legitimacy shifts away from popular participation and towards experts who are assumed to know how systems should work.

For humanistic politics, the danger is that we move from collectively changing how society works to experts designing the sustainable society for us. Those are not the same thing. Technocratic thinking is attractive because the problems are genuinely complex. Climate change, energy systems, transport, food production, biodiversity, housing and resource use involve enormous amounts of technical knowledge. Evidence matters. Expertise matters. Science matters.

But science cannot decide our political values for us. Technocracy present political choices as technical problems. Once something has been reduced to a question of efficiency, optimisation, cost-benefit analysis or measurable outcomes, the underlying political arguments can disappear. This creates a real #geekproblem: claims of value-neutrality conceal assumptions about whose interests matter, what counts as prosperity, and what kind of society we actually want.

This is where the needed environmental debate becomes much more interesting. The question isn’t simply – Technology or no technology? It is more, who controls technology, for what purpose, and through what social process?

A solar panel can be part of a community energy project, controlled collectively and used to change our lifestyles so that we reduce energy use and learn to live closely with nature. The same technology can be embedded inside a corporate energy system where communities remain passive consumers, with little change to user behaviour or the underlying system.

Open-source software can distribute technological power; closed platforms can concentrate it.

Electric vehicles can reduce some forms of pollution while still leaving questions about mining, manufacturing, urban design and transport dependency.

AI might help optimise energy systems, or it could become another enormous infrastructure of corporate and state control.

Technology itself does not answer these questions. Politics does. This is why the environmental movement needs to avoid both technological utopianism and technological nihilism.

The dark green critique is right to warn that technological efficiency does not, by itself, solve the political economy of endless growth. Efficiency can make consumption cheaper and therefore increase total consumption.

But the humanistic path cannot simply tell billions of people to consume less. That is not a sufficient political programme. People want decent homes, transport, healthcare, communications, food, energy and security. We cannot build a humanistic future by pretending that technological development can simply be switched off.

The missing piece is democratic technological development. We need the tools of humanistic environmentalism without surrendering political agency to technocracy. That means #4opens technologies, open standards, open data, open processes and democratic institutions. It means communities can understand, modify and govern, rather than systems that require permanent dependence on technical #elitists. It means treating technology as part of the social commons, rather than assuming that innovation must flow from corporations, governments or specialist institutions down to passive consumers.

The environmental challenge therefore isn’t simply about making capitalism greener. Nor is it about retreating into a fantasy of pre-industrial simplicity. We need to build a different kind of modernity – a modernity where technology reduces ecological damage and increases people’s ability to participate. Human progress is measured not only by efficiency or profitability, but by resilience, autonomy, repairability, accessibility and ecological impact. Where communities can understand and govern the infrastructures on which they depend. And where experts are valued for what they know without being allowed to become a substitute for democracy.

This is the point where humanistic environmentalism needs to meet the #openweb, #FOSS, the commons and grassroots organisation. The choice is not technology vs nature, nor experts vs ordinary people. The challenge is to grow social systems where knowledge, technology and democratic participation reinforce each other.

We don’t need less thinking, we need more people able to think, participate, organise and understand the systems shaping their lives. That is the difference between a technological future imposed from above and a technological future built as commons from below – using the best tools we have to build a society that is more ecological, more democratic and more capable of changing itself.

The #blocking of this is not that people disagree, challenge and disagreement are necessary, the blocking happens when criticism becomes a substitute for action.

Demanding proof before engaging with the alternative.
“What have you done?” can be a useful question, but it also becomes a way of putting the person making the challenge permanently on trial. The response then becomes about defending credentials rather than building the alternative.

Reducing action to individual performance.
“What have you done today?” is reproducing the very #stupidindividualism being criticised. The important question is not what heroic thing did one person do? But what are we building collectively?

Moving the conversation onto legality or uncertainty.
“The answer may not be strictly legal” and “Not sure…” don’t engage with the central question: how do we move communities away from the #dotcons? They redirect the conversation away from the structural challenge.

Treating posting as either everything or nothing.
The question is whether communication is leading somewhere. A post that recruits people into an open project is different from another argument that generates clicks for Facebook.

Confusing criticism with change.
“I try to subvert the acolytes of the status quo every day” sounds active, but the important follow-up is: what does that produce? Does it build a relationship, an organisation, a tool, a migration, a community or an alternative infrastructure?

The “positive alternatives” argument also become blocking.
“Just make positive posts about projects” sounds constructive, but if it means don’t criticise the existing system, it becomes a form of depoliticisation. People need to understand what is wrong, why it is wrong, and what they can actually do instead.

The useful distinction is: Criticism → understanding → organisation → action → alternative. Blocking looks more like: Criticism → argument → personal challenge → argument → more criticism. That is the #block.

The #dotcons argument is strongest when the hashtag isn’t treated as an answer in itself. #dotcons names the problem. #openweb names part of the alternative. #OMN is an attempt to build infrastructure for that alternative. The missing middle is the community that connects the three.

So the question “What have you done today?” is potentially powerful, but it should mean – What have we done together today that makes the alternative more real? That shifts the conversation away from individual virtue and towards collective agency. And that connects directly to the compost metaphor: don’t spend all day arguing about how bad the pile of mess is. Grab a spade, organise some people, and start turning it into something useful.

#BrightGreen #Environmentalism #Technocracy #ClimateChaos #OpenWeb #FOSS #4opens #Commons #Democracy #Technology #Ecology #Sustainability #OpenSource #Degrowth