dikaios1517 on Nostr: This is quite interesting. I agree with NOT using markdown in kind 1, and I also ...
This is quite interesting. I agree with NOT using markdown in kind 1, and I also agree that all clients are doing some amount of parsing and rendering in kind 1 notes already. It would therefore be nice to have some guidance on what should and should not be rendered in kind 1.
With NIP-10 calling kind 1 notes "plain text," it implies that no rendering of what has been typed is expected, yet clients are pretty consistent about rendering certain things, rather than just displaying the text. Nostr links with the "nostr:" prefix are almost always rendered, for instance. However, URLs with the "https://"; prefix are less consistent from client to client, though image links are almost universally rendered as the image itself. Some render a card preview of website URLs, others just make the URL clickable.
There's probably room for some of these inconsistencies, too.
With NIP-10 calling kind 1 notes "plain text," it implies that no rendering of what has been typed is expected, yet clients are pretty consistent about rendering certain things, rather than just displaying the text. Nostr links with the "nostr:" prefix are almost always rendered, for instance. However, URLs with the "https://"; prefix are less consistent from client to client, though image links are almost universally rendered as the image itself. Some render a card preview of website URLs, others just make the URL clickable.
There's probably room for some of these inconsistencies, too.