It’s challenging to design a social collaboration layer for distributed/decentralized productivity apps.
- Users are very familiar with opening a web app and performing mutations (often with an account that is specific to this app). An example is adding a comment to a PR on GitHub.
- In a decentralized setting, you often have cryptographic identity, which means that you have to sign mutations (or really anything that needs to be identifiable). This is currently tricky to do in a web browser (unless there are solutions I am not familiar with).
- So the pattern often is, mutate in the desktop app which has easy access to the private key. Web views become view-only (mostly for public data).
- Web apps are typically very useful for accessing information edited by many people easily.
- Is web very tied to the client-server model? Do we need a post-web social layer when we do things with cryptographic identity?
Major Challenges
Identity
Authorization
Post-Web / Post-Internet
Requirements (Decentralized Social Collaboration)
Data ownership (local-first)
Identity not controlled by central authority (sovereign?)
Content is searchable in the web for public projects