The truth is that in Nostr you have to support what everyone else does otherwise the UX is just terrible. This is just one of the 1000s of little things we need to do to support interoperabilty in the protocol.
Discussion
It would make sense to update those other fields only if they were already there in the first place.
But, more importantly, we can't have a protocol where people can do "whatever they want" without running into these little issues.
Sorry, but welcome to the other side of "embrace the chaos".
Personally, I favor tighter specs throughout. Discipline is the paradoxical path to freedom.
Exactly. Perfectly said on both. Most especially the parts about keeping the protocol as simple as possible. I worry that nostr is getting too fat too fast.
I also favor you, as nostr CEO, running rampant through the existing NIPs and sprinkling in a lot more MUST and MUST NOT.