Show HN: Noms – A new decentralized database based on ideas from Git
GC I can see a shape of solution for since you can use something like a per-object DVVset to determine the minimum set of unresolved histories required to avoid losing data during conflicts while not unnecessarily ballooning the size of the dataset.<p>However, the inner-object conflict-resolution problem seems a lot harder to solve given that there&#x27;s no obvious join-semilattice for arbitrary fields&#x2F;data.  Can you discuss what conflict-resolution strategies you&#x27;re working on for auto-resolution and&#x2F;or what metadata you intend to provide to the end-user in the event that you&#x27;re going to punt resolution to them to handle?<p>Given this is supposed to be for collaborative workloads, the conflict-resolution issue seems to be a cornerstone.  Git handles this by inserting sibling sections into the documents and forcing the end-user to manually deal with fixing problems, which is often fraught with pain and peril, and doesn&#x27;t seem like a strategy that would work for something that&#x27;s a database (as opposed to something that&#x27;s a workflow).