Event JSON
{
"id": "59cc106f38557bce4281720f6fd81213a3840710bec5ee13bb244cd07bdd2f51",
"pubkey": "419d8b951b40848f7e4098aeb24c436bb44df3713e58fd912ff06a159dcc5186",
"created_at": 1708783882,
"kind": 1,
"tags": [
[
"p",
"bb7c12f4baf4bb229123deaa1db296872a6f242578580ab345a66ced4483c389",
"wss://relay.mostr.pub"
],
[
"p",
"2b32eaaa9da9082c8d989e1129d543bbe9b4383be28e77cce2bd6ee7e86979aa",
"wss://relay.mostr.pub"
],
[
"e",
"ce7689e8e6a315860991841663397f65ca9e7cd31eb44f88cd96f5f247450115",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://social.harter.us/users/ryan/statuses/111986860515199731",
"activitypub"
]
],
"content": "nostr:npub1hd7p9a967jaj9yfrm64pmv5ksu4x7fp90pvq4v695ekw63yrcwysfhspxx I love the concept, but IMHO it's a dangerous suggestion without an important caveat: you need to also write good APIs that direct callers to do the right thing. I've worked with several engineers who preach this advice, but also write bad APIs that don't guide users in any way, crashing when callers make the wrong assumptions. Those crashes are simply called \"traps\".",
"sig": "fb48c3d9921b26ab2a7c3c773c799995f489df731e68c3676af730001cad1d5e46cb8a5cb806d69a57ffb4e56a1399fb93f550d8eebb5b20afd895a4ba7c464d"
}
