Mirrors/chatmail-core
1
0
Fork 0
mirror of https://github.com/chatmail/core.git synced 2026-04-02 05:22:14 +03:00
Code Issues Packages Projects Releases Wiki Activity

shift to webxdc naming (#2933)

Browse Source
This commit is contained in:
holger krekel
2021-12-31 13:18:43 +01:00
committed by bjoern
parent ef333da770
commit d7e699320b
2 changed files with 55 additions and 57 deletions
Download Patch File Download Diff File Expand all files Collapse all files

57
web30.md
View File

@@ -1,57 +0,0 @@
# Web30: at least ten times more interesting than Web3 :)
We combine secure chat-messaging and web tech in a unique way to fix deep shortcomings of both Web2 and Web3 to provide:
- decentralized secure interactive web apps **without coins or chains or stores**
- super-simple UX: no-login, no-account and no-server paradigm
- a new fun P2P playground with very low barrier of entry
## How it works
1. Send a self-contained web30-app to a chat (as archive or bundled html)
2. When receiver or sender click on the web30 app message open a sandboxed system web view from the unpacked web30 app
3. relay app-state update messages between web30 apps by exposing send/receive message functionality to the sandboxed web30 apps
Note that sandboxed web30 app are barred from making any network requests, reloading code or resources. They need to bring all the resources with them (offline first!). Note that we can use the same sandboxing technology that is relied upon for online banking, social media, shopping etc.
## Benefits to users
- full web interactivity available in an offline first manner
- no need for logins or accounts because apps run privately and started
from an existing social chat context
- no peer discovery mechanisms neccessary because you start from a chat group
- web30 app messaging is e2e-encrypted by default and there is no
way to read or collect app state information, not even by the web30 app developers
because they can not perform any IO outside the constrained send/receive offered by DC.
- no need to think about creating or representing yourself as a wallet :)
## Benefits to developers of web30 apps
Web30 empowers FOSS developments in unprecedented ways:
- no worrying about hosting a server or configuring DNS
- no worrying about registering at app stores for distribution
- no worrying about login/password/expiry procedures or leaks
- no worrying about cryptographic algos or e2e-encryption complexity
On the flip side, you need to learn how to do state updates between instances of your web30 apps. This is a classic P2P problem and there are CRDT and simpler methods to arrange decentralized state. But no DHT or blockchain needed and no Crypto or coin needed, either ;)
## Other important Benefits
Apps can become small again. 640KB should be enough for everybody, right? :)
Web30 is designed to run and to be tested with end-users in low-resourced precarious contexts that suffer internet and power outages regularly.
Simple model both for users and devs that can be explained in one minute and does not require diving into a quagmire of terminology and code complexity (yes, talking about you, Web3!)
As web30 does not require browsers to make remote network requests, a lot of the attack surfaces and code complexity is cut out.
## sidenotes
the title "web30" is a work title and might change :)

55
webxdc.md Normal file
View File

@@ -0,0 +1,55 @@
# webxdc: at least 200 times more interesting than Web3 :)
webxdc combines secure chat-messaging and web tech in a unique way to fix deep shortcomings of both Web2 and "Web3" to provide:
- super-simple UX: no-login, no-account and no-server paradigm
- a new fun P2P web app development playground with very low barrier of entry
- decentralized secure interactive web apps **without coins, chains or stores**
## How it works
1. Send a self-contained webxdc-app to a chat (as archive or bundled html)
2. When receiver or sender click on the webxdc app message open a sandboxed system web view from the unpacked webxdc app
3. relay app-state update messages between webxdc apps by exposing send/receive message functionality to the sandboxed webxdc apps
Note that sandboxed webxdc apps are barred from making any network requests, reloading code or resources. We use the same sandboxing technology that is relied upon for online banking, social media, shopping and various other browser tabs, with the added blocking of network requests. They need to bring all the resources with them, allowing users to interactively work with the app in an offline-first manner.
## Benefits to users
- full & fast web interactivity available in an offline first manner
- no need for logins or accounts because apps start and run privately
from an existing social chat context
- no peer discovery mechanisms neccessary because you start from a chat group
- webxdc app messaging is e2e-encrypted by default and there is no
way to read or collect app state information, not even by the webxdc app developers
because they can not perform any IO outside the constrained send/receive offered by DC.
- no need to think about creating or representing yourself as a wallet :)
## Benefits to developers of webxdc apps
webxdc empowers FOSS developments in unprecedented ways:
- use all the existing JS/html5 libraries and designs of your choice
- very minimal API to arrange for automatically encrypted encrypted app-to-app communications
- no worrying about hosting a server or configuring DNS or AWS or the like
- no worrying about registering at app stores for distribution
- no worrying about login/password/expiry procedures or leaks
- no worrying about cryptographic algos or e2e-encryption complexity
On the flip side, you need to learn how to do state updates between instances of your webxdc apps. This is a classic P2P problem and there are simple (send full state update) and advanced ways (use CRDTs or similar) to arrange decentralized state. In any case, there is no DHT let alone blockchain needed and thus no Crypto or coin needed, either.
## Other important Benefits
Apps can become small again. 640KB should be enough for everybody, right? :)
Network usage is minimal. Webxdc is designed to run and to be tested with end-users in low-resourced precarious contexts that suffer internet and power outages regularly.
Simple dev and usage model. Things can be explained in a few minutes and do not require diving into a quagmire of terminology and code complexity (yes, talking about you, Web3!)
As webxdc does not require browsers to make remote network requests, a lot of the related attack surfaces and code complexity is cut out.