What Makes Something
Freedom Tech?
Understanding Digital Self-Sovereignty
Core Requirements
Essential
- • Sovereign Identity
- • Signed Public Data
- • Encrypted Private Data
- • Self-hostability
- • Cryptographic Data Integrity
Bonus Features
- • Local First
- • Interoperability
- • Good Architecture
1. Sovereign Identity
Can I generate my identifier without permission?
Self-generated
No permission needed
Assigned by others
Permission required
Permission Hierarchy Example
How @basanta_goswami requires permission from multiple layers:
Each layer needs permission from above:
- • ICANN controls the root DNS system
- • Verisign operates .com under ICANN contract
- • GoDaddy sells domains via Verisign
- • Twitter bought twitter.com from a registrar
- • Finally, Twitter assigns usernames
Without permission at any layer, the entire chain breaks.
Human Readable Names
Contact Names vs Globally Unique Names
- • Globally unique names always need a central coordinator
- • Cryptographic identifiers aren't human friendly
- • Can use centralized names as overlay on pubkeys (lightning address)
- • Best: Use contact names to refer to pubkeys (like phone contacts)
2. Signed Public Data
Are we signing our data using private keys for authenticity?
Cryptographically Signed
Verifiable authenticity
Unsigned Data
No proof of origin
3. Encrypted Private Data
Are we encrypted our data using a private keys we control?
4. Self-hostability
Where is your data hosted?
5. Cryptographic Data Integrity
Are your content identified by hashes?
Why we need this:
- • Without hashes, content can be changed
- • References to content can be lost or hijacked
The Twitter Handle Problem
Why this happens:
- • Usernames can be recycled
- • Links use handles instead of permanent IDs
- • No cryptographic proof of original identity
6. FOSS
Can we check and verify the app's source code to make sure it does what it claims?
License matters:
- • MIT/GPL etc encourage code review
- • Community can verify security claims
- • Others can build upon and improve the code
Bonus: Local First
Can our app work without internet?
Many Nostr apps don't, but they theoretically can
Bonus: Interoperability
Can data generated using one app be accessed in other apps?
Architecture Debates
- • You might not like IPFS for trying to decentralize storage itself
- • You might not like Nostr for using websockets and JSON
- • You might not like Bitcoin for being too limited
- • You might not like altcoins because Bitcoin already solved digital scarcity
But once we have established the other points, this is the one we can argue about
Freedom Tech Comparison
How different technologies measure up against our criteria
| Technology | Sovereign Identity | Signed Public Data | Encrypted Private Data | Self-hostable | Cryptographic Integrity | FOSS |
|---|---|---|---|---|---|---|
| Nostr | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Bitcoin | ✓ | ✓ | ~ | ✓ | ✓ | ✓ |
| Reticulum | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| Signal | ✗ | ✗ | ✓ | ✗ | ✗ | ✓ |
| Proton Drive | ✗ | ✗ | ✓ | ✗ | ✗ | ✗ |
| CryptPad | ✗ | ✗ | ✓ | ✓ | ✗ | ✓ |
| Yakihonne (Nostr) | ✓ | ✓ | ✓ | ✓ | ✓ | ✗ |
| Amethyst (Nostr) | ✓ | ✓ | ✓ | ✓ | ✓ | ✓ |
| ✗ | ✗ | ✓ | ✗ | ✗ | ✗ | |
| Google Drive | ✗ | ✗ | ✗ | ✗ | ✗ | ✗ |