Reactions to events which kind is not 1

[mattn]

trafficstars

Damus or some of Nostr clients send kind-6 for repost kind-30023 long form content. And the clients for the content author will display a notice for this kind-6. If the client follow the link in the notification, you will see that the ID is not kind-1, but kind-30023. And client would try to display long form content even though kind-6 does not strictly support kind-30023. (At least docs says kind-6 only suppotr kind-1) Now, we have a behavior that depends on the client's behavior. If the client expects only kind-1 for kind-6, it have to restrict itself to kind-1 when getting events reposted by kind-6. If client accept both 1 and 30023, client have to display the content correctly.

@fiatjaf @jb55 Do you think that this is a bug of specification? Or client's behavior?

At least Nostter does not correctly display long form content when kind 6 points to an unexpected kind (30023). (This is intended, author says, and the clients which display 30023 via kind-6 have a problem)

I think we have to add small fix to doc (NIP-18) one of two fixes is applied.

(1) All of clients should not display non kind-1 event reposted via kind 6 (2) All of clients should display the events if the client support the kind.

cc @SnowCait