mirror of
https://github.com/chatmail/core.git
synced 2026-04-25 01:16:29 +03:00
refinements
This commit is contained in:
15
webxdc.md
15
webxdc.md
@@ -5,7 +5,7 @@ a decentralized secure web app eco-system without servers, coins or chains.
|
||||
|
||||
## How webxdc works
|
||||
|
||||
webxdc apps use existing chat groups (instead of web servers) to communicate with each other, with roughly this technical work flow:
|
||||
webxdc apps use existing chat groups (instead of web servers) to communicate with each other, with roughly this initial technical work flow:
|
||||
|
||||
1. Send a message to a chat with an webxdc app (archive or bundled html) as attachment.
|
||||
|
||||
@@ -14,6 +14,8 @@ webxdc apps use existing chat groups (instead of web servers) to communicate wit
|
||||
|
||||
3. webxdc apps can not reach the internet themselves and rather can only send "app-state" update message to other app users in the chat group.
|
||||
|
||||
While this describes an already working "proof of concept" usage there are already a lot of further reaching discussions. However, we prefer to avoid "early over-generalizing" and rather evolve further mechanisms and features from real-world needs, especially from people living in precarious contexts with bad networks and affected by internet outages.
|
||||
|
||||
|
||||
## Benefits to users of webxdc apps
|
||||
|
||||
@@ -22,11 +24,12 @@ webxdc apps use existing chat groups (instead of web servers) to communicate wit
|
||||
- no need for logins, accounts or discovery mechanisms because apps start and run privately
|
||||
from an existing social chat context
|
||||
|
||||
- privacy by protocol: leaking of content or metadata from app usage virtually impossible
|
||||
- privacy by protocol: leaking of content or metadata from app usage
|
||||
virtually impossible. No need for annoying GDPR or cookie consent dialogues.
|
||||
|
||||
- webxdc app messaging is also e2e-encrypted by default and there is no
|
||||
way to read or collect app state information, not even by webxdc app developers
|
||||
because apps can not contact anyone outside the chat
|
||||
- webxdc app messaging is e2e-encrypted by default and there is no
|
||||
way to read or collect app state information, not even by webxdc developers
|
||||
because their apps can not contact anyone outside the chat.
|
||||
|
||||
- no need to think about creating or representing yourself as a wallet :)
|
||||
|
||||
@@ -35,7 +38,7 @@ webxdc apps use existing chat groups (instead of web servers) to communicate wit
|
||||
|
||||
webxdc empowers FOSS developments in unprecedented ways:
|
||||
|
||||
- just use all the existing JS/html5 libraries and designs of your choice
|
||||
- well-known paradim: use all the existing JS/html5 libraries and designs of your choice
|
||||
- quick onboarding: only a handful API methods to learn
|
||||
- serverless (but really): no worrying about hosting a server or configuring DNS, AWS etc
|
||||
- permissionless: no worrying about registering at app stores for distribution
|
||||
|
||||
Reference in New Issue
Block a user