I agree, but I also think that nostr has adopted mutable state, for better or worse. I'm more concerned now about the complexity that this introduces to nostr's most important event kind. It's one thing for blog posts to support edit, which forces complexity onto only long-form clients, it's another thing to force everyone to support it.
Discussion
Definitely icky, but users have needs 🥲
i think we just need to put textnote and article kinds into the "replaceable" basket with a tag `["replaces","eventid"]`
specifically, if a kind 1 or 30023
hold on, articles are already in the replaceable number range
so, already kind 0 is replaceable, so is kind 3 (follows), it's just a matter of a tag i think? maybe even just use `d` like the rest?