Event JSON
{
"id": "f6520f5bb037a2c641a22db4a1fc76afbf939243cde34ab91f48e85a58f2cd48",
"pubkey": "da073fa5901b3dd43b432019fb80e1af3566d6a1ea63d93d04577371a8db9bde",
"created_at": 1692466758,
"kind": 1,
"tags": [
[
"p",
"06f01dd013e34e1af455ccdc67f4789ba2791880f3c820de5433665677403c2a",
"wss://relay.mostr.pub"
],
[
"p",
"d31cda351e214c6e59cc74acfe58ae2468cae97e6b20152bca4490931ff22c9f",
"wss://relay.mostr.pub"
],
[
"e",
"114a8bcd4c193d624e1a4a03b2a66a12e196b4bc4042dbdb55d7af9fe71642f0",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://mastodon.xyz/users/sgf/statuses/110917501487899038",
"activitypub"
]
],
"content": "nostr:npub1qmcpm5qnud8p4az4enwx0arcnw38jxyq70yzphj5xdn9va6q8s4qryv6gx I think \"Mastodon tries to get this right\" is really interesting, because every non-trivial technical decision I've seen be taken on Mastodon has chosen to do the easy thing over the correct thing!\n\nTo be fair, this pressure happens whenever tech gets big and complicated, so I'm intrigued as to whether the Mastodon design came before things got tricky, or was already in the \"I guess this sounds good enough\" local optimization phase?",
"sig": "8614da923c5565028243a9932f2d02b6966d5bd5dac8813c861a56bd7f2baf82f0d7bb30299d18389a2f10ba43002e8b6aa05638abeb29a1ad2b6a17d70e0a93"
}