Silberengel @Laeserin - 10mo
You actually won't have to change the branch, to change the leaf, once the 30041s are linked in with the new "a" tags. These first editions are still using "e" tags, but soon, you'll be able to edit leaves without having to update the branch. I already produced some test publications, with the new structure, but Alexandria isn't picking up on them, yet. You only have to change a branch if you reorder, add, or remove leaves, not if you change them, so long as the d-tag stays the same.
David @mleku - 10mo
i see it... makes sense... the tag designates the root for a branch... so there must be a simple event that creates the nodes and gives you that value right? has to be a node identifier to do it this way, totally makes it flexible then the only problem i foresee is now you have the situation where someone can come along and confuse that branch identifier, it needs to be locked to an npub i think? or something?
A tags are kind:d-tag:npub .
Here's a testdata event with a tags. Easier to show, than tell. https://njump.me/nevent1qqs8hp0e6ahazxjwc6xy6hhsfwc3ayk7umnul3mc8rjygxv90y97wcspzemhxue69uhhyetvv9ujumn0wd68ytnzv9hxgq3q2umrfdjgvdxt45g0y3ghwcyfagssjrv5qlm3t6pu2aa5vydwdmwqshnnfd
ah, ok, yup, so this locks the node to the npub as i said would be necessary, and if that npub changes the event, it changes the branch from that point down, and there is no way to confuse it so long as you pin it all to the npub
