My thinking on how replies should work with respect to edits, without knowing how it actually works...
The edit should point to the original message. Clients should render the edited version if they know about it. But a reply should always refer to original id - even if they never saw the original version.
That way threads stay sane for everyone involved, including for clients that don't understand replacements.
Furthermore replacements should not be kind 1, otherwise they look like duplicates to clients that support replacements.
To avoid ambiguity about what you actually responded to, a reply could *also* point to the edited version in a separate tag. https://image.nostr.build/5a0a6a9dd17751167640e324ec9e8e249823f34ce89618824c3aeac526db1e7c.jpg
Completely separate from edits you could have a maybe-delete and write again workflow. This might make sense if you said something completely insane and want to make sure that all your followers see the newly crafted message.
This will look like a duplicate post to any client / relay that can't handle deletes. But then hopefully it's clear from context that the original was unintended.
@hzrd149 some small tweaks you could make on noStrudel: update the timestamp in edits so it shows up below the original in a thread, and above in a timeline.
Also the yolo button doesn't give any indication that it succeeded. It should probably jump to the updated message.
The event publisher tool in noStrudel is designed as a tool to let users / developers publish any kind of bote they want. Its not really designed for editing notes, at least not in the sense of editing replies
The noStrudel edit tool is improving. The ability of my brain to actually type what I'm thinking is not. https://image.nostr.build/aace7dce2a6d08bf6081557a0ac059115a565f65badd4187435bf2ff7c8e6c7f.jpg
Nostrudel has edit support, @hzrd149 ? On kind 1?
no, I just improved the event publisher so you can republish any event you see nostr:nevent1qvzqqqqqqypzqfngzhsvjggdlgeycm96x4emzjlwf8dyyzdfg4hefp89zpkdgz99qyghwumn8ghj7mn0wd68ytnhd9hx2tcpzfmhxue69uhkummnw3e82efwvdhk6tcqypdf9u9ng644asrxsfxzcaayeq0knpnlppkmm9qy9qug8wqvsr7kk6lf7x8
Still not sure if there is a good solution for edits
there should be a "replaces" tag
pretty sure i've been saying this for like 8 months or more
the problem with edits isn't tying them to the original note, but loading 2x more data
if every note could have an edit, then client has to be aware of that and try to load it
Completely separate from edits you could have a maybe-delete and write again workflow. This might make sense if you said something completely insane and want to make sure that all your followers see the newly crafted message.
This will like a duplicate post to any client / relay that can't handle deletes. But then hopefully it's clear from context that the original was unintended.
Oddbean new post about login | logout 
