Skip to content

Commit 0b98390

Browse files
hpk42r10s
authored andcommitted
refinements
1 parent cd1f164 commit 0b98390

File tree

1 file changed

+9
-6
lines changed

1 file changed

+9
-6
lines changed

webxdc.md

Lines changed: 9 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ a decentralized secure web app eco-system without servers, coins or chains.
55

66
## How webxdc works
77

8-
webxdc apps use existing chat groups (instead of web servers) to communicate with each other, with roughly this technical work flow:
8+
webxdc apps use existing chat groups (instead of web servers) to communicate with each other, with roughly this initial technical work flow:
99

1010
1. Send a message to a chat with an webxdc app (archive or bundled html) as attachment.
1111

@@ -14,6 +14,8 @@ webxdc apps use existing chat groups (instead of web servers) to communicate wit
1414

1515
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.
1616

17+
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.
18+
1719

1820
## Benefits to users of webxdc apps
1921

@@ -22,11 +24,12 @@ webxdc apps use existing chat groups (instead of web servers) to communicate wit
2224
- no need for logins, accounts or discovery mechanisms because apps start and run privately
2325
from an existing social chat context
2426

25-
- privacy by protocol: leaking of content or metadata from app usage virtually impossible
27+
- privacy by protocol: leaking of content or metadata from app usage
28+
virtually impossible. No need for annoying GDPR or cookie consent dialogues.
2629

27-
- webxdc app messaging is also e2e-encrypted by default and there is no
28-
way to read or collect app state information, not even by webxdc app developers
29-
because apps can not contact anyone outside the chat
30+
- webxdc app messaging is e2e-encrypted by default and there is no
31+
way to read or collect app state information, not even by webxdc developers
32+
because their apps can not contact anyone outside the chat.
3033

3134
- no need to think about creating or representing yourself as a wallet :)
3235

@@ -35,7 +38,7 @@ webxdc apps use existing chat groups (instead of web servers) to communicate wit
3538

3639
webxdc empowers FOSS developments in unprecedented ways:
3740

38-
- just use all the existing JS/html5 libraries and designs of your choice
41+
- well-known paradim: use all the existing JS/html5 libraries and designs of your choice
3942
- quick onboarding: only a handful API methods to learn
4043
- serverless (but really): no worrying about hosting a server or configuring DNS, AWS etc
4144
- permissionless: no worrying about registering at app stores for distribution

0 commit comments

Comments
 (0)