neilck on Nostr: Just a thought about replaceable events. Overwrites of metadata or follower lists by ...
Just a thought about replaceable events. Overwrites of metadata or follower lists by clients who don't include the data from previous events causes users headaches.
What if a new replaceable event includes the current event's id as a tag? It proves the publishing client was at least aware of the previous event.
Client could choose to ignore the latest replaceable event if the tag doesn't exist, and fall back to either its own cached values or the last replaceable event with that has this tag. #nip01
Published at
2024-06-05 09:25:54 GMTEvent JSON
{
"id": "7d1b4dbabcaa4324b9e82aad39b7bf18974323656ccaf7ab9b6aeee0bbf610cf",
"pubkey": "00000003775402413595ac9e1612bed508815e98ec4aa9d68a2628ff6154856f",
"created_at": 1717579554,
"kind": 1,
"tags": [
[
"t",
"nip01"
]
],
"content": "Just a thought about replaceable events. Overwrites of metadata or follower lists by clients who don't include the data from previous events causes users headaches.\n\nWhat if a new replaceable event includes the current event's id as a tag? It proves the publishing client was at least aware of the previous event.\n\nClient could choose to ignore the latest replaceable event if the tag doesn't exist, and fall back to either its own cached values or the last replaceable event with that has this tag. #nip01",
"sig": "5b1e272dcbbf15aad7e1e7b20bdf423b77c7cdb50b0ef7581af0dbb24ac08ed85b812e5b694ad937fc4dffe67ed9040df67f588e212bbe0aa94b3c6719faf3e4"
}
