Yes. “Versioned specific” reactions would be nice … but I think (at best) this can only be accomplished on a “kind by kind” basis. If a NIP that specifies an addressable kind ALSO specifies that relays MUST NOT discard older versions of these events (which “as a convention” NIP-01 currently permits) then MAYBE relays will comply. But, also as it is, we currently have MANY ways to propose a NIP (two event kinds and counting, let alone “elsewhere” on the web). I don’t imagine that a single “NIP NIP” will ever be a standard.

Replies (2)

You’re right. I did point out that old versions of addressable events might be discarded. And if so (like it’s not available anywhere) then an “e tagged reaction to an unspecified event will be orphaned and not show up anywhere … let alone be associated with “some older version” of a NIP spec. I’m not sure this can work in a reliable manner. UX is important. Sure “leave it up to users to decide” is always an answer, but not always a good answer.
By two event kinds you mean as a wiki entry or using @Alex Gleason ‘s NIP NIP. For now, the NIP NIP has advantages over the wiki entry method, like a specialized way to list all event kinds used by the NIP. Are the NIPs at the top of NostrHub pulled directly from GitHub or are they wiki events?