You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: webxdc.md
+9-6Lines changed: 9 additions & 6 deletions
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ a decentralized secure web app eco-system without servers, coins or chains.
5
5
6
6
## How webxdc works
7
7
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:
9
9
10
10
1. Send a message to a chat with an webxdc app (archive or bundled html) as attachment.
11
11
@@ -14,6 +14,8 @@ webxdc apps use existing chat groups (instead of web servers) to communicate wit
14
14
15
15
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.
16
16
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
+
17
19
18
20
## Benefits to users of webxdc apps
19
21
@@ -22,11 +24,12 @@ webxdc apps use existing chat groups (instead of web servers) to communicate wit
22
24
- no need for logins, accounts or discovery mechanisms because apps start and run privately
23
25
from an existing social chat context
24
26
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.
26
29
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.
30
33
31
34
- no need to think about creating or representing yourself as a wallet :)
32
35
@@ -35,7 +38,7 @@ webxdc apps use existing chat groups (instead of web servers) to communicate wit
35
38
36
39
webxdc empowers FOSS developments in unprecedented ways:
37
40
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
39
42
- quick onboarding: only a handful API methods to learn
40
43
- serverless (but really): no worrying about hosting a server or configuring DNS, AWS etc
41
44
- permissionless: no worrying about registering at app stores for distribution
0 commit comments