Korean FE Article is an activity that selects good FE articles every week, translates them into Korean, and shares them. It is not used for commercial purposes, and the source must be identified.
I second this -- Scuttlebutt and Dat (Beaker is a browser built on Dat) are quietly doing the real work of making the P2P part of things a reality. They don't explicitly solve the problem of app-level conflict resolution/merging, but they provide good infrastructure to build it on top of. I also think IPFS is a decent option, along with Holochain (disclaimer: I work on the Holochain project).
https://croquet.io/ promises an alternative to P2P without requiring a trusted central server either. The idea behind Croquet stems back to the days of SmallTalk, even.
As long as the original authorship is maintained and the original publication is referenced feel free to translate and cross-post. Let me know when this is live. Thanks.
Love this & agree very much with the vision. You should check out yjs if you haven't. We're using it as the backend for a multiplayer collaborative 3d world.
Dropbox is a great example of local-first, but the authors of the Local First paper go way beyond that into the realm of collaborative work -- editing the same document and having two people's updates merged automatically, for instance. Along with @adlrocha they stress the value of P2P to remove centralised failure points.
Hi! I'm Bohyeon Seo, a front-end developer at Korean FE Article Team.
I read an article that was introduced on https://localfirstweb.dev/ at https://news.ycombinator.com/item?id=34857435. It was a very good article and was very helpful. I am going to translate the article into Korean and post it on the Korean FE Article mailing substack https://kofearticle.substack.com/ Is that okay?
Korean FE Article is an activity that selects good FE articles every week, translates them into Korean, and shares them. It is not used for commercial purposes, and the source must be identified.
Please consider and reply. I'll be waiting!
These ones does a great job at solving a huge bulk of the problems described:
https://beakerbrowser.com
https://scuttlebutt.nz
Mentioning them here since they are not widely known.
I second this -- Scuttlebutt and Dat (Beaker is a browser built on Dat) are quietly doing the real work of making the P2P part of things a reality. They don't explicitly solve the problem of app-level conflict resolution/merging, but they provide good infrastructure to build it on top of. I also think IPFS is a decent option, along with Holochain (disclaimer: I work on the Holochain project).
https://croquet.io/ promises an alternative to P2P without requiring a trusted central server either. The idea behind Croquet stems back to the days of SmallTalk, even.
As long as the original authorship is maintained and the original publication is referenced feel free to translate and cross-post. Let me know when this is live. Thanks.
Love this & agree very much with the vision. You should check out yjs if you haven't. We're using it as the backend for a multiplayer collaborative 3d world.
Omg... cant imagine... but nice article. https://www.youtubeviewsup.com | https://www.adddzz.com
Git is a tool for doing collaborative decentralized software development.
This is the future. Imagine Facebook like this.
You are describing Dropbox world, aren't you?
Dropbox is a great example of local-first, but the authors of the Local First paper go way beyond that into the realm of collaborative work -- editing the same document and having two people's updates merged automatically, for instance. Along with @adlrocha they stress the value of P2P to remove centralised failure points.