nostr:npub1jlrs53pkdfjnts29kveljul2sm0actt6n8dxrrzqcersttvcuv3qdjynqn's attempted at defining this in this nip27 PR: https://github.com/nostr-protocol/nips/pull/1800
Discussion
Ooh, good! Thanks.
Then why is not a single app following this?
And why does most devs tell me all the time that kind 1 and 9 *have to be* plain text?
1) because it was never standardsised in the protocol so apps did their own thing.
2) in an attempt to make creating a simple client easier so it doesn't need so much custom rendering.
1) I know of no app that does render any of this in compact renderings (quoted events, one liners, ...)
2) that leads to barely anyone building libraries for the hard stuff, that can make building the beautiful experiences, that people actually want, easier
Much more thought went into ATProto lexicons, have to say.
Most apps do follow this. It's a dafinition based on that "plain text" recommendation, nostr:nprofile1qythwumn8ghj7anfw3hhytnwdaehgu339e3k7mf0qyghwumn8ghj7mn0wd68ytnhd9hx2tcppemhxue69uhkummn9ekx7mp0qywhwumn8ghj7v3nvakhgtnwdaehgu3ww3jkx6rwdakx7eme9uq3samnwvaz7tmxd9k8getj9ehx7um5wgh8w6twv5hsqgzxpsj7dqha57pjk5k37gkn6g4nzakewtmqmnwryyhd3jfwlpgxts07ucgf just didn't want us to use the term plain text, so we made up a new name.
Got ya.
Not easy for me to find this stuff, before I #complainstr about its non-existence, oops.
Agree with most of the list in there.
(But again, there's not one app that has this basis covered for compact text references. That's the one renderer everyone forgets about.)