2,244 karma · joined October 27, 2010
Get in touch via hn.9vma5ivse705uf3zwxddp3vc@giurgiu.net
So my initial comment merely tried to make the point that there is a design space where you’re not stuck with the tradeoff of carrying the full Merkle DAG history just to be able to reconstruct the latest version of your document.
Thanks for the video, will check it out!
Prolly trees allow you to store history independent data which is trivial to sync, diff and merge, regardless of insert order, merge order or originating peer. A Merkle DAG layered on top of prolly trees (event reference prolly tree roots) gives you causality so that peers can agree on a common view of history. So it's very useful because you can check integrity and travel in time, but you can keep as much of it as you want, because it's not necessary for constructing the current state. Prolly trees give you the current state and the easy syncing, diff,merge. So you can truncate the history as needed for your use case.
For a production ready implementation of prolly trees you can check Dolt. For a combination of Merkle DAG (https://github.com/storacha/pail) and prolly trees you can check https://github.com/fireproof-storage/fireproof
Regarding distributed schemas, I agree, there's a lot of complexity there but it's worth looking into projects like https://www.inkandswitch.com/cambria/ and https://github.com/grafana/thema, which try to solve the problem. It's a young space though. If anyone else knows about similar projects or efforts, please let me know. Very interested in the space.
- 5k resolution at HIDPI (27inch)
- 120hz refresh rate
- TB5 and single cable connectivity.
There are a couple of other HIDPI displays at 5k with 120hz refresh rate but they don't do TB5.
What do you think about the general approach in Uncloud? It almost feels like a cousin of Swarm. Would love to get your take on it.