It's not even about me anymore. Edits have been a huge success in term of usage with over 50,000 edits in the first months (before fiatjaf started spamming it). It's literally what everybody wants, regardless of what devs think about it.
Less is often more. You heard the arguments over and over again since you introduced edits and I assume you like it as is, so I knew I wouldn't convince you but I'm also square in the no-edits camp. More details in this note nostr:nevent1qvzqqqqqqypzq3huhccxt6h34eupz3jeynjgjgek8lel2f4adaea0svyk94a3njdqy88wumn8ghj7mn0wvhxcmmv9uq3uamnwvaz7tmwdaehgu3dwp6kytnhv4kxcmmjv3jhytnwv46z7qpqp363kxquth9fsmrvxr37cvezwwwk9xtmrug8hukf8e5een6qvrjq678wk0
What is "everything else that Amethyst implements and others dont"? If you support kinds that others don't, I don't think the same applies as users don't treat the same events differently like in the kind-1 case where Amethyst users react/zap/reply to something else than others once the note was edited.
Discussion
When Twitter first started, people also wanted edits and longer messages, yet arguably it took off because of limitations not despite of them.
If Amethyst ends up being the preferred client of 5% of all users and fails to convince others to adopt editing, those users will assume they can edit as in fact they do, yet 95% of their followers only ever see the unedited version. This causes confusion and I think if other devs remain reluctant to adopt editing notes, retiring this feature should be an option.
Like I said before, I don't think this "confusion" is a valid argument. That is always going to be the case with nostr. Heck.. people are confused that different kind 1 clients show different feeds. If they post in one, it's not guaranteed that it will show on the others. So, to me this argument doesn't make much sense. Clients will never show the same thing. We must embrace this "confusion" of feature differences between clients. That's what makes Nostr, nostr.