I don't understand this perspective. Edits are clearly shown as edits, you can always see original, and it provides a compact yet expressive way for us to acknowledge and clarify our mistakes rather than appearing not to care.
Spamming is just spam. nostr:nprofile1qqsrhuxx8l9ex335q7he0f09aej04zpazpl0ne2cgukyawd24mayt8gprfmhxue69uhhq7tjv9kkjepwve5kzar2v9nzucm0d5hszxmhwden5te0wfjkccte9emk2um5v4exucn5vvhxxmmd9uq3xamnwvaz7tmhda6zuat50phjummwv5hsx7c9z9 may have been the inventor or co-inventor or founder or whatever of #Nostr, but he is not immune to spamming.
I don't honestly see the issue, I follow him, I click the edited button to see his original message, I move on.
If it is the size of his posts, I'll say it again. Spam is spam.
That would be cool if you can edit and still see the original post like an unhide tab or something
The issue is not the usage from a user perspective; the issue is that it creates a fork, between clients that support this and clients that don’t. A client that shows edits will show an entirely different thing than a client that doesn’t.
Keeping kind 1 simple is crucial which is also why we don’t support markdown, html, and all kinds of bells and whistles.
If you increase the cost of running a node few people will.
If you increase the cost of creating a client few people will.
Welcome to the Fediverse circa 2021…
But tools like Nostr Development Kits will raise the bar from the other side.
You can’t depend on SDKs to abstract complexity; that’s the death of protocols because then the SDK becomes a choke point and developers using the SDK become captive, downstream, to the SDK.