LockeShor on Nostr: #[0] #[1] what do you think about a NIP that introduces the ability to edit ...
fiatjaf (npub180c…h6w6)
jb55 (npub1xts…kk5s) what do you think about a NIP that introduces the ability to edit kind 1 notes? Long-form content posts are already parameterized replaceable, but i don’t see a way that could be implemented while retaining backwards compatibility. The solution that comes to mind is that you could publish a new event referencing the old one, similar to a deletion, and clients could search for those whenever pulling a note. However the drawback is that checking every note for edits would be very resource consuming. Do you have any thoughts?
Published at
2023-05-11 03:17:52Event JSON
{
"id": "f19fc67fc2290e240f7dcfab7012aa3b5e201f4a8cf9bfbbd9bbd389ffac0c39",
"pubkey": "1e5a1e20559975c1cd44a4d041cfd22bab69edba975f87e64ee9f80ee23b3968",
"created_at": 1683775072,
"kind": 1,
"tags": [
[
"p",
"3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d"
],
[
"p",
"32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245"
]
],
"content": "#[0] #[1] what do you think about a NIP that introduces the ability to edit kind 1 notes? Long-form content posts are already parameterized replaceable, but i don’t see a way that could be implemented while retaining backwards compatibility. The solution that comes to mind is that you could publish a new event referencing the old one, similar to a deletion, and clients could search for those whenever pulling a note. However the drawback is that checking every note for edits would be very resource consuming. Do you have any thoughts?",
"sig": "0e939c0721c77227a9f10793f4f1e88d18fb1cc45e9c9d221007ca0edf4e55aea2dbc58f4a8b9a299a2b02502117df544335299ae6291db462a6214884e4fa33"
}
