rabble on Nostr: I think we need to rework how we handle lists in Nostr. The way we do it now, any ...
I think we need to rework how we handle lists in Nostr. The way we do it now, any client can republish a list without any diff or reference to it's knowledge of the previous version means that clients will get a partial list or fail to get a list from relays and then publish an empty one. I just now noticed that i've lost all the people in my contacts...
If we had diff's or a signature chain for previous versions, we could handle this and merge / restore lists...
Published at
2025-10-16 02:12:35 UTCEvent JSON
{
"id": "1494bcfc8b76edf22a44d5899460b9be8d4f3e5868668e1c1067dd05525beaea",
"pubkey": "76c71aae3a491f1d9eec47cba17e229cda4113a0bbb6e6ae1776d7643e29cafa",
"created_at": 1760580755,
"kind": 1,
"tags": [
[
"client",
"Yakihonne",
"31990:20986fb83e775d96d188ca5c9df10ce6d613e0eb7e5768a0f0b12b37cdac21b3:1700732875747"
]
],
"content": "I think we need to rework how we handle lists in Nostr. The way we do it now, any client can republish a list without any diff or reference to it's knowledge of the previous version means that clients will get a partial list or fail to get a list from relays and then publish an empty one. I just now noticed that i've lost all the people in my contacts... \n\nIf we had diff's or a signature chain for previous versions, we could handle this and merge / restore lists... ",
"sig": "d591e155ef97ecc2da769535c20fc9f161eabbf7eb6395a379a7ffdc7b5e1c1314e2367632b2612b1e2dd1b9dd54764fba7c4d8a919824ef687a36eb8180ca89"
}