tal on Nostr: Cool! It seems like Parameterized Replaceable Events (NIP-33) is just the thing I've ...
Cool! It seems like Parameterized Replaceable Events (NIP-33) is just the thing I've been looking for. If I understand correctly, all I'd need to do is ensure a unique d-identifier for each summary - hash(thread_note_id) could do the work. Having some attached flag that prompts clients to only show the contents, sidestepping all the "referenced event" extras, could be really neat. Is this nip widely adopted by the common clients/relays out there?
Published at
2023-06-10 15:26:47Event JSON
{
"id": "9572aaafc69c86d91255fcf2e23477e01f5355375ea31f071436d8e929aa51dc",
"pubkey": "738ea36ef74b2ac80bfb3887b40637c7dcdf74ea6eed73c718b7193313b90f9b",
"created_at": 1686410807,
"kind": 1,
"tags": [
[
"e",
"ce60252b6ce98c99136574b43c7893614e380bc303ecf9cad24dfd878b95d9a0",
"",
"root"
],
[
"e",
"78c4fa7778126d8dc07b029b8c97a6681b664fbbd60ab52eebbcd95897911a0d",
"",
"reply"
],
[
"p",
"fa984bd7dbb282f07e16e7ae87b26a2a7b9b90b7246a44771f0cf5ae58018f52"
]
],
"content": "Cool! It seems like Parameterized Replaceable Events (NIP-33) is just the thing I've been looking for. If I understand correctly, all I'd need to do is ensure a unique d-identifier for each summary - hash(thread_note_id) could do the work. Having some attached flag that prompts clients to only show the contents, sidestepping all the \"referenced event\" extras, could be really neat. Is this nip widely adopted by the common clients/relays out there?",
"sig": "1ebedb052e4d6368b9040820c2a68dee08034728f9180d3b341fcfb66d91ed4490f8b45bf963247c655f706aa4fcabda986be8258e0fe4ac275b73cfef1cf150"
}
