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.

And our goal is to stop publishing NIPs on a GitHub repo. I know you want backwards compatibility, and your changes to kind 17 allow that, which is fine. There’s going to end up being multiple ways for people to express their thoughts on custom NIPs. You have kind 17, maybe someone does kind 7, we’re going to need one or more methods for people to express more nuanced opinions than a simple binary up or down. GrapeRank can take them all in.