https://onp4.com/@vadim/~collaborative-editing Collaborative Editing Mon, 11 May 2026 11:43:03 GMT https://validator.w3.org/feed/docs/rss2.html P4 - P for posting en Copyright, P4 https://onp4.com/@vadim/p/mxx8yi4jml https://onp4.com/@vadim/p/mxx8yi4jml Tue, 27 May 2025 00:53:06 GMT https://onp4.com/@vadim/p/53t15p9aa7 https://onp4.com/@vadim/p/53t15p9aa7 Wed, 11 Sep 2024 14:58:14 GMT https://onp4.com/@vadim/p/b2sdna4rgj https://onp4.com/@vadim/p/b2sdna4rgj Tue, 20 Aug 2024 12:06:37 GMT https://onp4.com/@vadim/p/t6vu7pm4r3 https://onp4.com/@vadim/p/t6vu7pm4r3 Wed, 13 Mar 2024 22:44:51 GMT https://onp4.com/@vadim/p/ofg47urmg9 https://onp4.com/@vadim/p/ofg47urmg9 Tue, 13 Feb 2024 10:32:45 GMT https://onp4.com/@vadim/p/wzfncd3yjk https://onp4.com/@vadim/p/wzfncd3yjk Tue, 13 Feb 2024 08:54:03 GMT https://onp4.com/@vadim/p/scjty6oj2l https://onp4.com/@vadim/p/scjty6oj2l Wed, 06 Sep 2023 08:42:34 GMT https://onp4.com/@vadim/p/85zodnsaoj https://onp4.com/@vadim/p/85zodnsaoj Thu, 31 Aug 2023 08:18:17 GMT https://onp4.com/@vadim/p/9lyxctf6eo https://onp4.com/@vadim/p/9lyxctf6eo Sun, 27 Aug 2023 14:58:12 GMT https://onp4.com/@vadim/p/089f2twvxf https://onp4.com/@vadim/p/089f2twvxf Sun, 27 Aug 2023 13:04:49 GMT ` inside of `^{`. That way arbitrary complexity math formulas should be possible to edit. - Algorithm support: JSON CRDT supports just two algorithms RGA and Last-write wins registers. Out of those more complex data types can be built, for example, out of RGA a sets and multi-value registers can be constructed. Consider if it is necessary to introduce more/other algorithms into the implementation. - Reconsider clocks - JSON CRDT supports two clock types: (1) Logical vector clock; (2) Total Order Broadcast server clock. - For JSON CRDT 2.0 consider if any of the following clocks could be used: (1) Merkle clock; (2) bounded version vectors; (3) Hybrid logical clock; (3) Dotted version vectors; (4) Tree clocks; (5) Interval tree clocks; (6) GUN-like wall clock with constraints. - Merkle DAG CRDT native support. Maybe embrace Merle DAG: - Clocks would be Merkle clocks. - All objects could reference each other by CIDs. - There could be "infinite" length CRDTs, such as HAMT CRDT and Feed CRDT in P4. Infinite-length data type support: - HAMT CRDT --- an infinite size key-value LWW CRDT. - Feed CRDT --- an infinite size ordered list. - Maybe group CRDTs into: (1) finite size; (2) unbound size ones. - For performance, could be still useful to group some objects into blocks: say, RGA objects are their separate blocks but LWW objects could be grouped in one DAG block. - Consider how to work around IPFS block size constraints for large CRDTs. - Adding additional pointers to the DAG to work around thin DAH problem. - Natural evolution to v2. Maybe, instead of the stop-the-world-full-rewrite the JSON CRDT could seamlessly migrate to JSON CRDT 2.0, e.g. JSON CRDT 2.0 would be a superset of JSON CRDT. - Consider embedding "stored procedures" inside the CRDT or having an ability for operations to be custom defined by some scripting language. For example, use the [JSON Expression](https://github.com/streamich/json-joy/blob/master/src/json-expression/README.md) language. - Consider adding Reference Value type, which is a value which refers to another CRDT. - GraphQL-like API, IPLD-like lenses, "projectsion API", ability to subscribe to a subset of data, especially if CRDT is a graph of nodes in CAS. - Research why YATA algorithm generates less chunks than Blockwise-RGA. (At least that is the case using Martin's trace.) - Rich-text/Peritext integration into the main spec? - Code editor support---they require quick navigation by line number. Maybe Peritext could insert virtual block at every newline `\n` position and provide fast line indexing. - Dealing with loss of context (large deletions)---imagine in a collaborative rich-text editor user selects few paragraphs (maybe whole document) to copy the text `Ctrl + C`, but accidentally presses `Ctrl + X`, instead, then---to fix the document---user re-inserts the text with `Ctrl + V`. This results in complete loss of content and all causal context for other users (other user cursors get lost, other user inserts get inserted into a void). - Optimization: local RGA inserts do not need to follow the standard RGA algorithm. Local inserts do not encounter *preemptive siblings*, i.e. when doing a local insert, there should be no IDs between the `ref` ID and the new op ID. - RGA is composed of two binary trees. It is serialized by text-order. Consider ability to serialize by ID-order. This way on the server the RGA could be unserialized with balanced ID tree and insertion could be implemented without hydrating the text-order tree. Even if text-order tree is hydrated, the main advantaged is to have the ID-order tree balanced, as that tree will be used to perform an insertion lookup. - When unserializing balance the by-ID tree, instead the by-text tree. - Are there better algorithms then RGA? What about YATA? - Consider explicitly support deep integration with UI to be able to perform local operations at `O(1)` speed. For example, a cursor in a text editor can maintain a direct pointer to the RGA chunk to which the cursor is pointing. - Use real world traces to compute relative frequencies of different insert/delete code paths. (Inset at root, insert at root with concurrency, insert after a block, insert after a block with merge, block split, deletes ...). - When doing splay rotations, consider moving tobstones as low as possible in zig-zig rotation. - Consider implementing triple-zip rotations, where tombsones are extra rotated down. - Consider storing the whole causal graph, i.e. each operation would also contain the "parent"---the last know operation in the document or the last known operation in a specific object. - Maybe Peritext can be integrated somehow into JSON CRDT such that internal timestamps are not exposed. Maybe using some format like Quill Delta. - Switch to Fugue algorithm? Or, execute RGA by default and add ability to optionally switch into Fugue-mode, when the right origin is presented in the operation. - Sync9 and Fugue result into the same sorting order, because, apparently, to solve for interleaving there is not much possibilities for alternative sorting variants. Maybe, it is possible to solve for all interleaving problems without much extra metadata (with less metadata than proposed in Fugue)? - *Permanent Range Deletes* --- RGA delete operation where: (1) a range is deleted; (2) tombstones are deleted forever, with exception for the last character in the deletion range, which is left as a tombstone.]]>} https://onp4.com/@vadim/p/16xlv8ayq1 https://onp4.com/@vadim/p/16xlv8ayq1 Sun, 25 Jun 2023 19:39:40 GMT https://onp4.com/@vadim/p/jy4shqsrau https://onp4.com/@vadim/p/jy4shqsrau Fri, 19 May 2023 22:37:38 GMT https://onp4.com/@vadim/p/5z4zj1qdoe https://onp4.com/@vadim/p/5z4zj1qdoe Sun, 23 Apr 2023 19:26:26 GMT https://onp4.com/@vadim/p/iyc64k1k7h https://onp4.com/@vadim/p/iyc64k1k7h Thu, 13 Apr 2023 17:16:18 GMT https://onp4.com/@vadim/p/uwue84oxwn https://onp4.com/@vadim/p/uwue84oxwn Thu, 13 Apr 2023 17:00:31 GMT https://onp4.com/@vadim/p/wi207kyue0 https://onp4.com/@vadim/p/wi207kyue0 Mon, 10 Apr 2023 12:52:42 GMT https://onp4.com/@vadim/p/rdge4odxp1 https://onp4.com/@vadim/p/rdge4odxp1 Mon, 10 Apr 2023 12:52:27 GMT https://onp4.com/@vadim/p/x2p2f1qilq https://onp4.com/@vadim/p/x2p2f1qilq Mon, 10 Apr 2023 12:52:16 GMT https://onp4.com/@vadim/p/ff7hbx91oi https://onp4.com/@vadim/p/ff7hbx91oi Mon, 10 Apr 2023 12:51:58 GMT https://onp4.com/@vadim/p/1uili1bbww https://onp4.com/@vadim/p/1uili1bbww Mon, 10 Apr 2023 12:51:50 GMT https://onp4.com/@vadim/p/jxij2td6yb https://onp4.com/@vadim/p/jxij2td6yb Wed, 05 Apr 2023 18:31:07 GMT https://onp4.com/@vadim/p/ykxv9fjbib https://onp4.com/@vadim/p/ykxv9fjbib Mon, 27 Mar 2023 22:41:47 GMT https://onp4.com/@vadim/p/7uod7b3tf2 https://onp4.com/@vadim/p/7uod7b3tf2 Mon, 27 Mar 2023 22:41:24 GMT https://onp4.com/@vadim/p/m8f4gpp4jp https://onp4.com/@vadim/p/m8f4gpp4jp Tue, 20 Dec 2022 21:08:42 GMT https://onp4.com/@vadim/p/nmb9fwx8ce https://onp4.com/@vadim/p/nmb9fwx8ce Tue, 20 Dec 2022 21:07:51 GMT https://onp4.com/@aleks/p/m46f53dvsu https://onp4.com/@aleks/p/m46f53dvsu Mon, 19 Dec 2022 20:52:30 GMT https://onp4.com/@vadim/p/2cfgo3gdpo https://onp4.com/@vadim/p/2cfgo3gdpo Sat, 03 Dec 2022 00:18:18 GMT https://onp4.com/@vadim/p/ux2dyr78ed https://onp4.com/@vadim/p/ux2dyr78ed Fri, 02 Dec 2022 23:58:59 GMT https://onp4.com/@vadim/p/el4t4hgfqr https://onp4.com/@vadim/p/el4t4hgfqr Fri, 02 Dec 2022 22:33:17 GMT https://onp4.com/@vadim/p/y3zwtmx9as https://onp4.com/@vadim/p/y3zwtmx9as Wed, 30 Nov 2022 22:57:03 GMT