Well maybe I will propose something but I wouldn't hold my breath if I were you
Not saying it's impossible but it's uncommon and would be met with heavy resistance
Breaking changes are extremely difficult to introduce to standards
the spec specifies json so that would have to be changed, breaking every client and relay in the process
JSON is not space efficient or particularly efficient to parse so there are more stability issues compared to other formats. Since it's a text-only format there is also no efficient way to include binary data which makes it problematic to allow file attachments or anything in notes
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
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.
ease of development, scalability, potential features
nostr would be a lot better if it didnt use json
that still ultimately requires putting your nsec in an untrusted website which is a bad idea. I think the most "normie" friendly way to do things would be to ultimately be to have a way for people to delegate key management to "identity providers" that people register for with using a regular email that then handles their keys and signs messages over https (and does nip-05). This of course requires trusting the identity provider but provides account recovery and still provides the advantage of not being tied to a single relay.
That’s the trade off for not being tied to a specific instance
Yes, though not sure there’s a good solution yet
?resize=480:*up to 12 cents thanks to the generous #lightning #community
might be a fun diversion sometime. I'll think about it