not appropriate?
If Alice writes some piece of content that is a parameterized replaceable event, Bob likes the content, and then Alice updates it, I may want to know whether Bob liked the current version or a previous version.
Suppose Alice turns out to be a bad actor. She vibe coded a good NIP, got some likes, then swapped it out for spam. If Bob endorses spam I’ll be inclined to think maybe he’s a bad actor too, but how do I know whether he liked the spammy version or a previous (non spammy) version?
You’ll point out that the old event will be discarded, so we won’t be able to find the old version, so we won’t know what he liked. If so, we’ll at least know whether Bob liked the current version or some previous (no longer existing) version, information which may be useful even if it doesn’t tell the whole story. And there’s also the possibility that older versions of parameterized content get stored by design for some particular set of use cases, even if that’s not the usual practice.
Login to reply
Replies (1)
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.