We are not the first people to want – or to build – tech based on the values we share here. Other communities have many people committed to parts of our mission.
So what are we doing differently? What’s our project?
First up, we define and nurture Tech We Trust collaboratively – we know that everyone needs to be able to recognize it, find it, support and contribute to it with confidence.
It's not enough just to be able to recognize it. Too many projects representative of Tech We Trust are currently struggling. They are often under-resourced and frequently built out only to the point that makes them usable for the developer community that made them, leaving them inaccessible to everyone else. Such projects may disappear quickly, have spotty support for those who rely on them, and are too rarely adopted widely enough to have a meaningful impact on trust, equality, privacy or decentralization.
So, we are going to do three things:
1. Help people identify Tech We Trust
By reaching out across the technology, academic, and business sectors, we are bringing together people aligned with our purpose with deep domain knowledge about tech and how people use tech. We hope many will be active Collective members and we’ll convene conversations with other relevant experts.
Tech is not something that can be directed well by the crowd. Lacking information about how the Internet and World Wide Web work, the crowd may call for a solution that really doesn’t help, that’s been tried unsuccessfully before, or that has unintended consequences. We will rely on the collective intelligence of recognized domain experts to clarify the technical details of what constitutes Tech We Trust, and to help the broader Collective decide what projects to support, fund and create.
2. See what already exists
We need to see the ecosystem of projects that could qualify as Tech We Trust. This ‘Collective Ecosystem Map’ will offer those working on such projects the opportunity to discover alignments and better coordinate amongst themselves without needing the Collective to mediate.
Nominate a project indirectly, or help with this mapping effort:
3. Determine what tech the Collective should build
When we combine the insights from domain experts with the data we collect about various projects in our ecosystem, we’ll be able to choose better where to invest our combined time, talent and money. In the meantime, we are building a few small projects to support team coordination and Collective communication.