matthewbennett on Nostr: Markdown thoughts: if Nostr is text and Markdown is text, you can't stop people using ...
Markdown thoughts: if Nostr is text and Markdown is text, you can't stop people using it. Some people and clients will want it, others not, so it will come down to client and UI/UX support. Even if Client A and User A love it but Client B and User B will hate it, the total flow of notes depending on who everyody follows is going to contain Markdown. Maybe User B uses Client B because they're in the HateMarkdown Tribe but then User B wants to follow User A, etc, etc. Does this not suggest that the solution is a new UI/UX element that allows for changing the display of the note depending on the particular jumble of letters you are trying to look at? (Similar to a translate button)
Published at
2023-02-05 12:47:37Event JSON
{
"id": "f1ece418370302724642efdbfd02b4e91ca2d5b1917034d0d77493bccc3e668b",
"pubkey": "7fa92094e2293f097c7cfef2933ed37a167062c254c540aa7ec26e8019cec726",
"created_at": 1675601257,
"kind": 1,
"tags": [],
"content": "Markdown thoughts: if Nostr is text and Markdown is text, you can't stop people using it. Some people and clients will want it, others not, so it will come down to client and UI/UX support. Even if Client A and User A love it but Client B and User B will hate it, the total flow of notes depending on who everyody follows is going to contain Markdown. Maybe User B uses Client B because they're in the HateMarkdown Tribe but then User B wants to follow User A, etc, etc. Does this not suggest that the solution is a new UI/UX element that allows for changing the display of the note depending on the particular jumble of letters you are trying to look at? (Similar to a translate button)",
"sig": "ce8f614537e6f0254fd46b816f03626103da347af420dfec3f9f6ab193e4a86be6f9ef3f391e39664ed45d28ff5a434690a49d31962f38bce8161138e253f895"
}