lib-collab-automerge-examples.md

title	tags	created	modified
lib-collab-automerge-examples	automerge collaboration examples	2023-09-01 10:18:00 UTC	2023-09-01 10:18:14 UTC

lib-collab-automerge-examples

guide

popular

• https://github.com/WoelkiM/AutoCouch /MIT/202004/ts/inactive
  • AutoCouch is a TypeScript framework to create object-oriented CRDTs that supports a simple way of distribution.
  • Database is a simplified wrapper of a PouchDB that allows getting and putting documents.
  • 📕 AutoCouch: a JSON CRDT framework_202004
    • AutoCouch is a JSON framework combining the benefits of the Automerge CRDT library and CouchDB
  • https://github.com/WoelkiM/Polly_React_Example_AutoCouch
    • an example for a React app using AutoMerge

starter

• https://github.com/bpietroniro/hello-automerge /202401/ts
  • getting to know the Automerge CRDT library

examples

• https://github.com/jonfk/text-crdt-experiment-automerge-ts /ts

  • http://jonfk.github.io/text-crdt-experiment-automerge-ts
  • Small experiment project to test out Automerge text features to see if it would be a usable for the core data structure of an offline first syncing text editor.
  • 依赖automerge.v0.12、diff-match-patch、react-redux

• https://github.com/richardanaya/crdt-todo

  • An example application using CRDT library Automerge to make a TODO app

• https://github.com/andrewinci/free-retro

  • https://retroapp.amaker.xyz/
  • A retro board inspired by retrium
  • 依赖automerge.v2、mantine、react-dnd、emotion

• https://github.com/pvh/automerge-prosemirror-workbench

  • testbed for automerge/prosemirror

• https://github.com/block-based-editors/automerge-tree

  • https://block-based-editors.github.io/automerge-tree/
  • (real-time) collaboration on blocks with automerge saved in a tree

• https://github.com/ben-ryder/automerge-encryption-demo

  • A proof of concept using Automerge in a React app with client-side encryption, multi device sync via a server and more.

• https://github.com/fr3shw3b/diagramming-crdt /apache2/202402/ts

  • experimenting with CRDT for a simple diagramming application

automerge-hypercore

• https://github.com/extendedmind/peermerge /rust

  • https://codeberg.org/convivialsoftware/peermerge
  • Peer protocol (hypercore or p2panda) + Automerge in Rust

• https://github.com/Ruulul/automerge_hypercore_demos /js

  • local_sync_textareas

automerge-v1

• https://github.com/automerge/hypermerge /MIT/ts/archived

  • Hypermerge is a Node.js library for building p2p collaborative applications without any server infrastructure.
  • It combines Automerge, a CRDT, with hypercore, a distributed append-only log.
  • Hypermerge is deprecated.
  • Hypermerge is a distributed document store. It draws inspiration from databases like CouchDB and PouchDB
  • hypermerge document is built up by applying a series of changes generated on different clients.
    • Every time you open a hypermerge document, the system replays all the logs of changes from every client to recreate the document state.
    • This can be slow and expensive for large documents, but has excellent history-preserving properties and guarantees clients can always return to earlier states or merge new changes as they arrive.
  • Hypermerge stores an automerge document as a set of separate Hypercores, one per actor ID. Each actor ID in the document is the discovery key of a Hypercore, which allows recursive lookup.
  • This strategy works for a small number of documents, but is very slow to synchronize due to the vast number of Hypercores required for a large collection.
  • Every opened hypercore keeps a file handle open permanently
  • Local-first database: Hypermerge | Jared Forsyth.com_202009
    • It is designed as a fully peer-to-peer data storage system, and is electron/nodejs-only (no browser support).
    • Conflicts are automatically resolved by Automerge, although the exact behavior is undocumented.
    • Hypercore, the underlying persistence layer, uses hashing to verify consistency (from what I can tell).
    • Both client and server store a full replica of all changes made, and from some preliminary testing, it looks like the constant factor is rather high (the on-disk size increasing by multiple kilobytes when adding a single change to an attribute).
    • it is a research tool primarily, and not meant to be production ready.

• https://github.com/nornagon/autowiki /automerge

  • Autowiki is a tool for creating networked documents.
  • Autowiki is a local-first app: you own all the data you put into it, and your data never leaves your own machine unless you want it to.
  • Autowiki uses automerge under the hood to resolve edit conflicts automatically.

sync

• https://github.com/openscript-ch/automerge-repo-storage-opfs /MIT/202401/ts

  • https://automerge.org/docs/repositories/storage/
  • This implements a OPFS storage adapter for Automerge Repo.

• https://github.com/DImuthuUpe/automerge-java-sync-server /apache2/202312/java

  • Java Spring Boot Sync Server For Automerge

utils

• https://github.com/getroomservice/manymerge /202005/ts/inactive

  • A one-to-many protocol for the Automerge CRDT
  • It's a replacement for Automerge.Connection that supports many-to-many and one-to-many relationships.

• https://github.com/verygoodgraphics/vgg_automerge /MIT/202312/cpp

  • A C++ implementation of automerge, at an early stage.
  • Added several new APIs, users can operate an Automerge doc like a json object

more