Sketchy Idea Proposal #00: Legacy nevents

Let's call the pre-existing protocol's nevents "legacy nevents" because they'll be sticking around - there's no way all devs, relay operators, etc will agree to migrate to SIP-01

-------

Sketchy Idea Proposal #01: New nevents

Let's have new nevents which are just legacy nevents reformatted in accordance with the following criteria:

1. No English or other natural language in the code for nevents anymore; be more efficient, computers don't need extra binary bits for all the unicode characters to turn field IDs into words. Metadata fields, for example, can be referenced with more efficient binary than repeating their names every time they're used in the backend. The frontend doesn't need the names of metadata fields repeated in the backend for the user to see them. Fix all that stuff for each type of legacy nevent reformatted to a new one.

2. Make sure a language field is included in the metadata for kind 1 nevents.

3. Make sure a version letter is included in the metadata for kind 1 nevents. This is Latin-alphabet-centric but is a convenient and efficient way to provide for tracking up to 25 edits.

-------

Seeking feedback

All zaps forwarded to fiatjaf as a token of respect

#nostr