You can track revisions forward that are by the same author, but you're right that finding forks is not possible with the current architecture. E.g: when I pub

You can track revisions forward that are by the same author, but you're right that finding forks is not possible with the current architecture. E.g: when I publish my website, it gets a permanent address, like: hyper://b282d5efe484143816362d33b3f9b3ea45ecfb8a6ada97e278fdfdc6a725e22f/ When I change a file on the page, it is still accessible on that address, and so are the older versions. The same peers connected to the address will transparently receive the update and seed that as well. And yes, it's totally separate from IPFS, but is built from many of the same ideas. Dat started back in like, 2011 or so? This is a good high-level overview of how protocol works: https://hypercore-protocol.org/protocol/ https://hypercore-protocol.org/protocol/ - the fundamental unit of storage is hypercore, the append-only log. IPFS's structure, the raw merkle tree, requires another layer on top to provide mutability, like IPNS or DNSLink, but I do not believe that these provide the same guarantees of "auto-propagate updates without loss of older version." Hyper*/Beaker also provides mechanisms to use centralized authority like DNS to provide human-readable resources, that simply point from the DNS entry to the hyper URL.