david's avatar
david david@bitcoinpark.com 1 month ago
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.
↑ Parent

Replies (1)

ManiMe's avatar
ManiMe manime@npub.bar 1 month ago
Backwards compatibility is not “what I want”. I hate managing legacy code. But it is necessary in an open and evolving standard. The NIP 73 update I proposed does not restrict, but opens up new possibilities. As far as reactions go, a single kind 17 (or 7) reaction can be EITHER a binary or can be an any emoji. This allows for having BOTH as options (two buttons) in a single UX. Great. NIP-73 is ALSO a way for comments to reference “external content”. Yes. Nostr can comment on anything … including arbitrary NIPs. The NIP-73 update simply adds a standard for ANY event to reference ANY arbitrary NIP. Imagine someone makes an approval flow NIP … for any kind. Instantly, an approval flow can be applied to any NIP proposal ANYWHERE simply by referencing. Imagine three different takes on this idea. Everyone can use this standard to reference “a NIP” and everybody wins.
↑