One of the useful arguments in the debate around decentralisation, blockchain and the #openweb is also one of the simplest – We do not actually live in a trustless world, we live in a world built on different kinds of trust. This is why the Fediverse worked because it was #4opens with a good #UI.
The problem it had to overcome and still does is that much of #geekproblem pushing technology is obsessed with trying to eliminate trust rather than understanding how trust works. The idea of the “trustless” technology sounds attractive. If we cannot trust governments, corporations, banks, platforms, administrators or even other people, why not build digital systems where nobody needs to trust anybody?
This is a simple mindset, instead of trusting a person, trust the mathematics, instead of trusting an institution, trust the protocol. Instead of trusting a moderator, trust the code. Instead of trusting a community, trust the ledger. It sounds wonderfully clean, but there is a problem – you cannot eliminate trust, the social truth is you can only move it somewhere else.
A #blockchain can make it difficult to alter records after they have been entered, but it cannot magically make the information entered into the system true. Someone still has to enter the information, someone has to write the software, someone has to maintain the infrastructure, someone has to interpret the results and someone has to decide what happens when reality doesn’t fit the rules. That distinction, people, is important for thinking about the future of the #openweb as the path to trustless is usually just displaced trust.
Imagine buying a digital object through a “trustless” smart contract. The theory says that you don’t need to trust the seller. The contract automatically enforces the transaction. But do you trust the person who wrote the smart contract? That the code does what you think it does? Do you understand the code well enough to audit it? Do you trust the software running on your computer? Do you trust that the thing described by the contract is actually the thing you want? Suddenly, the system isn’t trustless in any way.
On this blinded pushed #geekproblem path, you are exchanging trust in people and community for trust in software, tech infrastructure and your own technical ability. A tiny number of people are grasping for power, in this it is a “grassroots” mirroring of the current #dotcons mess. Supposedly trustless transactions always fall back on reputation, previous experience, known counterparties or the assumption that somebody will behave fairly.
And this isn’t necessarily a failure, it is a recognition of how society actually works, trust is basic infrastructure. We think of trust as something soft and personal, a handshake, reputation, knowing somebody. Being part of a community, a history with an organisation. But trust is actually a form of core social infrastructure.
When you buy something from a local shop, you don’t individually audit every component of the business. You trust the shopkeeper, the reputation of the shop, the legal framework. You trust food standards, trust that if something goes badly wrong, there are mechanisms for dealing with it. None of this means that the shop is perfectly trustworthy, it means that layers of “soft” trust, accountability and social mechanisms make cooperation possible.
The same thing happens online, we trust websites, moderators, administrators, developers. We trust maintainers, communities. They all have reputations, the interesting question here isn’t – how do we eliminate trust? It is, how do we build better systems of trust? The #geekproblem problem of pretending that trust doesn’t exist, is a fantasy of the trustless system that makes things less democratic. If trust is made invisible inside code, people lose sight of where power shapes process and actually sits. So replacing a human decision with a technical decision doesn’t remove politics, it hardens and hides it by simply hiding politics inside infrastructure.
The #geekproblem isn’t about technical people being bad or that technical knowledge isn’t relevant. Quite the opposite, complex systems need technical knowledge. The current problem comes when technical expertise becomes a substitute for social and political accountability. The system says, “The code says so.” But somebody decided what the code should say, decided what the code should not say – that is governance.
This is where the #4opens become useful.
Open Data.
Open Source.
Open Standards.
Open Process.
The point of this simple clarification of #FOSS is to make the system trustworthy enough to participate in and transparent enough that people can understand how that trust is produced. Open source allows people to inspect and modify the software. Open standards allow different systems to communicate. Open data allows information to be examined and reused. Open process makes decision-making visible. They together make trust more accountable, a much healthier goal.
On this current broken path, some people assume that decentralisation means removing trusted intermediaries. But decentralisation does not mean removing relationships, it means distributing relationships and accountability. Instead of one corporation controlling everything, you have many independent communities. Instead of one giant moderation department, you have distributed moderation, one platform deciding the rules, instead communities establish their own rules while communicating through shared standards. Instead of one central archive, many organisations hold copies and contribute metadata flows.
That is not in any way trustless, it is distributed trust, and distributed trust is much closer to how healthy communities actually operate. Reputation matters, people have always used reputation to decide whom to trust. You recommend a builder because someone you know had good experience with them, choose a restaurant because friends recommend it. You work with someone because they have a history of doing good work, participate in a community because you know the people involved.
An example of this #geekproblem in tech the last 20 years of #blockchain projects, is that they have to recreate reputation systems, off chain, to grow trusted parties because people need them to function. This shouldn’t surprise us, reputation is accumulated social knowledge, a record of relationships, it is one of the ways communities remember.
And that common sense is something that technology should help communities develop rather than trying to replace with abstract technical mechanism. This is the danger of “code is law” a seductive idea, if the rules are encoded into software, nobody can arbitrarily change them. But real life doesn’t work like software, people make mistakes, circumstances change. Sometimes the rules themselves are wrong.
A genuinely sustainable social system needs the ability to interpret, moderate, appeal, correct and change, this requires people, relationships and basic governance. It requires trust, were a completely rigid system may be technically predictable while being socially disastrous. Trust needs accountability, this is particularly important for grassroots technology. When we build alternatives to the #dotcons, we shouldn’t simply recreate their power structures with different software. We need to ask:
- Who can make decisions?
- Who can see what is happening?
- Who can challenge a decision?
- Who can correct mistakes?
- Who can leave?
- Who can fork the system?
- Who can moderate?
- Who controls the infrastructure?
- Who owns the data?
These are trust questions, a trustworthy system isn’t one where nobody has power, it is one where power is visible, distributed and accountable. Trust isn’t blind faith, yes, there is a danger in romanticising trust, trust doesn’t mean blindly believing people. Good trust is built through evidence.
- You trust somebody because you have a relationship with them.
- You trust an organisation because it has demonstrated competence.
- You trust a process because you can see how it works.
- You trust a community because people hold each other accountable.
- You trust software because it is open, tested and maintained.
- You trust a system because there are ways to challenge it when it fails.
So the opposite of “trustless” isn’t “blind trust”, it is earned, observable, and accountable. This gives us a useful direction for the current #openweb reboot. It points to the mess we need to compost, we don’t need to recreate the fantasy of an entirely trustless internet. The commercial internet already tried extreme centralised trust – for 20 years the #dotcons became trusted intermediaries for almost everything, owning the infrastructure, controlling the algorithms, identity, data, moderation. They controlled visibility, they still control the economic relationship with users. That isn’t trustless, it is concentrated trust and concentrated power.
Trust is the missing layer, there is a tendency in narrow #geekproblem paths to think in terms of infrastructure first. Servers, protocols, APIs, encryption, algorithms. But underneath all of these sits a social question – why should anyone trust this system? And the answer cannot simply be “Because the code works.” as a system can work perfectly and still be socially terrible. The important question is whether the technology helps people create relationships that are transparent, accountable, resilient and capable of self-correction. That is a much bigger challenge than creating a trustless protocol, but it is also much more useful.
To build on a different path, we need networks where communities can trust their own infrastructure. We are already doing this on the #Fediverse, building on #ActivityPub standard that allow communities to communicate. Moderation systems where decisions are kind of visible and accountable. What is lacking is building governance that people can participate in, this is where projects such as #OMN and #OGB become interesting. There goal isn’t to make human relationships unnecessary, it is to build technical infrastructure that supports better human relationships.
From trustless to trustworthy, means accepting that trust is unavoidable and then making trust visible and accountable. It means combining open standards with open governance, decentralisation with community and recognising that humans aren’t bugs in the system – humans are the system.
Technology should therefore not be designed around the fantasy that people are unreliable components that need to be eliminated. It should be designed around the reality that people cooperate through relationships, reputation, shared history, norms, institutions and accountability. The #KISS task of the #openweb is not to eliminate these things, it is to build better versions of them, real alternative to the #dotcons – not more dead-end trustless technology.
The #OMN path is distributed trust, supported by open technology and democratic governance. And perhaps a more radical idea – rather than trying to remove trust from society, we should get much better at building it, sharing it and making it accountable #KISS.

#Trust #Trustless #OpenWeb #OMN #OGB #4opens #FOSS #Commons #Fediverse #Decentralisation #Governance #Democracy #Technology #Community











