Open mattyg opened 1 year ago
regardless of the choice, I think it might be nice to have a uuid anchor in the entry
regardless of the choice, I think it might be nice to have a uuid anchor in the entry
Why do you think this is valuable? As compared to using a HRL for cross-dna unique identifier, and an ActionHash for an in-dna unique identifier?
either one, maybe both.. would make for a good discussion, I will need to think more about it
perhaps describe more your thoughts on HRL :)
On Wed, Mar 22, 2023 at 9:49 AM Matt Gabrenya @.***> wrote:
regardless of the choice, I think it might be nice to have a uuid anchor in the entry
Why do you think this is valuable? As compared to using a HRL for cross-dna unique identifier?
— Reply to this email directly, view it on GitHub https://github.com/GeekGene/MewsFeed/issues/88#issuecomment-1479819745, or unsubscribe https://github.com/notifications/unsubscribe-auth/AKZFIHFOHC73ZBXX4TFMNG3W5MNPPANCNFSM6AAAAAAV4O5L74 . You are receiving this because you commented.Message ID: @.***>
either one, maybe both.. would make for a good discussion, I will need to think more about it perhaps describe more your thoughts on HRL :)
The idea of HRL is a standard way to reference stuff cross-dna. It follows this format: <DnaHash>:<AnyDhtHash>[@<AgentPubKey>]
See this for more context: https://hackmd.io/FbK0GP-vRb6WvdXctqJzhQ?both
Guillem already wrote a basic coordinator zome implementation that lets you request an HRL, and it converts that into a cell call under-the-hood to fetch the data. It need's to be pulled out into a holochain-open-dev package at some point: https://github.com/lightningrodlabs/we/tree/main/crates/hrl_locator
Consider refactoring DNAs to make it as easy as possible to upgrade integrity zomes and port data into a new DHT.
We may not want to facilitate this at all, and instead rely on coordinator zomes fetching the underlying data from a prior versions running cell.
If we did want to facilitate migrating data into subsequent version's cell, I think this means not relying on ActionHash as the "id" for some data, and instead storing a UUID within the Entry, and then linking from a UUID anchor to the Entry itself.