nip37: editable short notes by means of referencing a different addressable kind instead

[fiatjaf]

This is another alternative to #1090, #1091 and #1556

I don't know if this is a good idea ultimately, but I think it is directionally correct because it doesn't harm non-implementing clients and the openness of kind 1, while giving more complex clients the ability to do full-blown edits with no more work than other proposals would require.

text: https://github.com/nostr-protocol/nips/blob/nh-editable/37.md

[vitorpamplona]

Tested on #1087

Issues we found:

1. The entire event is editable, not only the content. So, a reply can move from thread A to thread B, which would break all replies under it. So, users can be taken to separate threads by the previous reply owner. The separate thread might mean the opposite of the current thread. Replies can also "steal" replies for themselves, in separate posts, helping build their WoT.
2. It's not clear how to interact with kind1. Can kind 1 be a reply to a kind 31000? Lots of issues arise when you mix both of them.
3. There is no edit history. Which is really important for users.

[arthurfranca]

This is a creative proposal though the most significant downside is that it requires kind:1 clients to understand a quote to a new event kind. It is demanding these clients to add code, which breaks backwards compatibility.