hyperhyperspace-core VS plastic-editor

Not all CRDT libraries focus on text editing. For example, I'm working on a Byzantine fault tolerant general-purpose data sync library loosely based on CRDTs: https://www.hyperhyperspace.org

I'm finding it painfully difficult but it is evolving steadily.

I'm thinking there's an interesting parallel between my browser-based p2p project [1] and cloudflare workers / DurableObjects. Instead of DurableObjects, we got HashedObjects [2], and instead of workers running on an edge network somewhere, we got in-browser p2p nodes running a browser-to-browser mesh network.

[1] Hyper Hyper Space: https://www.hyperhyperspace.org

I agree with the author on the merits of the file abstraction, but I think the concept should be updated for networked devices. We need file formats that support both offline usage and seamless sync over the network.

For example, here I use a merkle DAG-based file format to represent CRDT-like types:

https://www.hyperhyperspace.org

The resulting abstraction can be universally looked up using a hash (or short sequence of words), can be modified offline and synchronized flawlessly. It's still WIP (for example, you still can't export it to an actual file, hehe).

> I've been kicking around the idea of writing a CRDT-based editor using this model.

I got around to creating a data layer (p2p, browser-based, CRDT-backed) for something like this:

https://github.com/hyperhyperspace/hyperhyperspace-core

I'd be interested in collaborating on your editor

I'm working on it, Ben [1].

Believe me, it is not easy thing to do.

[1] https://github.com/hyperhyperspace/hyperhyperspace-core

Look at Hyper Hyper Space!

https://github.com/hyperhyperspace/hyperhyperspace-core

Its goals are similar, the approach is more pragmatic (p2p data layer using standard web browsers and webrtc).