I care because of interoperability. To let others know what we are doing so that they can parse and generate things like we do. It's not about telling them what to do. Because in the end, each dev does whatever they want to do and we also adapt to that (and change the NIP to reflect it). You can't block people from doing what they want in Nostr. You can only hope people want to collaborate in the same payloads.

Replies (2)

It's easier for you to get a new NIP than for any normal dev to even get a small change to an existing NIP. So, changes to NIPs don't seem like a big deal to you, whereas NIPs are basically carved in stone, from the viewpoint of most other devs.
It's not easier for me. I propose so much crazy stuff that people just ignore my NIPs these days... "There comes Vitor again". I found that it's easier if I just convince somebody new to send the NIP than sending it myself. Reviews are softer because everybody welcomes a new person. Less biases. In that way, I can also see if people are liking it because of the idea or just because it's coming from Amethyst and will be implemented anyway. I do appreciate the criticism over the idea itself.