> sig-chains - you know if you're missing content in PZP
You could do the same on nostr if anybody actually cared about this. Just include a "prev" tag with the ID of the previous message in the chain you're building. You could also have a "last" tag or something to indicate the chain is complete. Clients could render it as "message 3/9" or whatever, like people do manually on Twitter.
In fact, PZP's replication appears to *rely* on these hash chains, since it uses hash graph replication: https://codeberg.org/pzp/pzp-sync
I did some analysis of this sync method and if you tried to use it for non-linked data you can easily cause it to degrade into a worst-case behaviour: https://github.com/hoytech/automerge-poison
IMO RBSR/negentropy is better, one of the reasons being you can sync arbitrary collections of (unlinked) data, for example all kind 0 notes, or all notes with a certain hash tag.
Doug Hoyte /
npub1yx…8qud4
2024-12-22 17:50:18
in reply to nevent1q…ahen
Author Public Key
npub1yxprsscnjw2e6myxz73mmzvnqw5kvzd5ffjya9ecjypc5l0gvgksh8qud4Published at
2024-12-22 17:50:18Event JSON
{
"id": "bdffb0dff7838392bd64ce84bf814ad3ba88e0b6a71177a29f12324cb399ea22",
"pubkey": "218238431393959d6c8617a3bd899303a96609b44a644e973891038a7de8622d",
"created_at": 1734889818,
"kind": 1,
"tags": [
[
"client",
"oddbean"
],
[
"e",
"000011bcacf28711bc0c79c57cf3e6c90990aa3c86e11ae6d6504654c5bcfe6c",
"",
"root"
],
[
"p",
"76c71aae3a491f1d9eec47cba17e229cda4113a0bbb6e6ae1776d7643e29cafa"
],
[
"p",
"d0a1ffb8761b974cec4a3be8cbcb2e96a7090dcf465ffeac839aa4ca20c9a59e"
],
[
"p",
"3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d"
]
],
"content": "\u003e sig-chains - you know if you're missing content in PZP\n\nYou could do the same on nostr if anybody actually cared about this. Just include a \"prev\" tag with the ID of the previous message in the chain you're building. You could also have a \"last\" tag or something to indicate the chain is complete. Clients could render it as \"message 3/9\" or whatever, like people do manually on Twitter.\n\nIn fact, PZP's replication appears to *rely* on these hash chains, since it uses hash graph replication: https://codeberg.org/pzp/pzp-sync\n\nI did some analysis of this sync method and if you tried to use it for non-linked data you can easily cause it to degrade into a worst-case behaviour: https://github.com/hoytech/automerge-poison\n\nIMO RBSR/negentropy is better, one of the reasons being you can sync arbitrary collections of (unlinked) data, for example all kind 0 notes, or all notes with a certain hash tag.",
"sig": "1644edc7838ad2b71733ba7e4c1043b405d7a8f0666635799f967a9972f8ba1bb5823b0ec842324d6ec6f31247bdcf89d07dc9a7fd02a1f15f3db0e8c13af399"
}