Principles

Design Principles

P2P
Local First
Easy, Distributed Account/Identity Recovery
Data Sovereignty
Algorithmic Sovereignty
Flood Search Routing
Ant Routing
Small World Networking
Correct by Construction Code
Data Balancing, Distribution and Management
Knowledge Horizons (Compartmented Data)
E2EE
Encryption at Rest
Rebooting the Web of Trust
Make the protocol difficult/impossible to snoop/identify (see OFFSystem)
Distributed is better than Decentralized/Federated (Should not require administration)
No pre-planning to increase “truck factor”
Microtransactions increase friction
- Jaron Lanier’s original thoughts
- See the mess that is modern gaming
Avoid metrics fixation
- Seeking the largest number of views is always toxic (See Context Collapse)
Prevent problems via system topology (Topologies of Harm Talk by Elio)
Co-ownership of data
Promote long term collection, curation and refinement of data and knowledge. Discourage, rapid thoughtless posts.
Curation is better than search
Protocols over programs over services
NO DRM! Ever!

Distributed systems don’t scale (Google Borg and Moxie Marlinspike’s Writings on the Necessity Centralization. Moxie is wrong!)
CAP Theorem is a bigger problem than it should be due to grouping too much data
Zooko’s Triangle and “pet names”

Adoption of these protocols is critical
Jujutsu version control system
Context Resilience
Promotion of Content (e.g. Micro-blog -> Blog -> Article -> Book)
Usability is crucial for devs initially, and for the general public longer term.
Must be simple, discoverable, and understandable

What license should this be released under?
- MIT/BSD
- AGPL
- BPL
How do we keep the project moving forward as it grows and there are inevitable conflicts between devs, users, and adversarial attacks.