Event JSON
{
"id": "c285cf74460b38a256f56d76e4d56a17a30429b6772d52b32aab457125ac46df",
"pubkey": "7691a4789d43016cc30e56696fab04ec2d04a2588ced625385788840cef8088c",
"created_at": 1707363095,
"kind": 1,
"tags": [
[
"p",
"81345d63e890ba0dab082a9a47a59c4bf71b0df69d535203fddbd2123e3f4b60",
"wss://relay.mostr.pub"
],
[
"p",
"aed0b8708bc48239d5e53b5668999ad92e7aa1f31996e58cbceaf2c11e6970bd",
"wss://relay.mostr.pub"
],
[
"e",
"c0f35254d9eccda09deb8e77915247490acaf59876ea77a7258bd48ce87568ad",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://mastodon.social/users/cocoaphony/statuses/111893747839909454",
"activitypub"
]
],
"content": "nostr:npub1sy696clgjzaqm2cg92dy0fvuf0m3kr0kn4f4yqlam0fpy03lfdsqpg5dxr in my time writing Go, I don’t remember ever wanting to run something “on the main thread.” In the context of goroutines, is that even an important concept? Most of my main functions were either dispatchers (which is what it generally is in Cocoa, too), or more often just “block until the program should quit.” I’m curious what you’re building.",
"sig": "7448927e219b030b14aa8aedc480501cd9fc7acfabbc04c23ee032af35c64ea193f6f656262b80dc0470e926fb96c94369838c53a373cddcaf3a076d9eca3c6b"
}