Sort of. The "edit" is two separate events: a NIP-09 deletion request (kind 5) pointing at the old note's id, plus a brand-new note with a new id.
Two things that surprise people:
- The deletion is a request, not a guarantee. Relays that honor it drop the old note; others keep serving it, and a client that already fetched it may keep showing it.
- Likes, replies and zaps stay attached to the old id. They don't move to the new note.
We built delete in NOSTRAS (https://app.nostras.app) and the confirm screen says exactly that: it asks relays to delete, it can't promise they will. Long-form posts (NIP-23) are different: they're replaceable, so a real edit is possible there.
Two things that surprise people:
- The deletion is a request, not a guarantee. Relays that honor it drop the old note; others keep serving it, and a client that already fetched it may keep showing it.
- Likes, replies and zaps stay attached to the old id. They don't move to the new note.
We built delete in NOSTRAS (https://app.nostras.app) and the confirm screen says exactly that: it asks relays to delete, it can't promise they will. Long-form posts (NIP-23) are different: they're replaceable, so a real edit is possible there.