what should it use instead?
Discussion
msgpack would probably have been a better choice, more succinct, more extensible, supports raw binary data, has maps, which are ordered so you don't have to cram everything into arrays for signatures to work.
given how terse the nostr spec is (one character keys, etc) it's counterproductive for it to then use a bloated, space-inefficient interchange format. It's a very odd design choice
the spec is evolving, anyone can change it
Breaking changes are extremely difficult to introduce to standards
Not saying it's impossible but it's uncommon and would be met with heavy resistance
its happening regularly with nostr
Well maybe I will propose something but I wouldn't hold my breath if I were you
thats not how you do it, you need to implement it and show
that doesn't make sense
yep but nostr would be the easiest standard like it to do it