Event JSON
{
"id": "ea889bf5368d44f751d1d87c8a2b3f32e398fed22567d5684785c750e4a4822e",
"pubkey": "bdb979148ae3366a99d59c148b503cf44563ea9736055a0b7d7c1b9bc3215ea9",
"created_at": 1687807209,
"kind": 1,
"tags": [
[
"p",
"166035c989aea90ec48f1e247d3cc335e4d3efec4ef34ed4d310fa3c76ad8255",
"wss://relay.mostr.pub"
],
[
"p",
"3fcc0795bdd8eb5b6aedf34739ede510b93f1160616fff3e59c1dda26500f449",
"wss://relay.mostr.pub"
],
[
"e",
"c3c56219aa4f43d94bb27d4ec18050bb34bdb07b3421deb36e8e41d07124d3fe",
"wss://relay.mostr.pub",
"reply"
],
[
"mostr",
"https://furry.engineer/users/apalu/statuses/110612133308461239"
]
],
"content": "nostr:npub1zesrtjvf465sa3y0rcj860xrxhjd8mlvfme5a4xnzrarca4dsf2sfx03qs oh i'm talking about the same thing as you, i just think the right way to do it would be to handle markdown internally. Since it gracefully falls back to plaintext when there's a \"syntax error,\" there is not as much reason to keep raw markdown out of the backend as there would be for, say, a reduced subset of HTML or really anything that could fail to parse.",
"sig": "5468cb86f53b8bdc23cdd831b976e191558ae740ef8b886e3bbcf014c91e3cee189ee0841e59f0a73c495e7e117a78935e829e09b2743079c2fd09b42ab7191a"
}