You still don't get it do you? It doesn't matter what the repo says. The repo can only document what exists to avoid duplications of fields that do the same thing with different names. That's all it can do.
Login to reply
Replies (3)
this naming problem is just a subset of how to name anything within nostr
You keep telling me that it doesn't matter what the repo says, but you are constantly editing the repo content.
If you thought it didn't matter, you would ignore it.
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.