Event JSON
{
"id": "5cbc9a6e17e249386c91be58b0f8561eacf92f959fc7f49d556e17c29e2a34ba",
"pubkey": "7a56a0e40e898fdd368d08e1a917b539ae8bbcc7d785fbe874a6ecc7b15b0a7c",
"created_at": 1707494440,
"kind": 1,
"tags": [
[
"p",
"f14ce6b0701d2bfc979d26cf117840c11969d97144639f2fa05a5dd23407b6d3",
"wss://relay.mostr.pub"
],
[
"p",
"a9b947079d89c9e0252ddec4950c44b7c06c6067e6440cbe12d1cd98287b7730",
"wss://relay.mostr.pub"
],
[
"e",
"d35fca05e21644c79a18cc27bdc699ab82c6909fab9048a96397f14571cee866",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://toot.io/users/synlogic/statuses/111902355675735119",
"activitypub"
]
],
"content": "nostr:npub179xwdvrsr54le9uaym83z7zqcyvknkt3g33e7taqtfwaydq8kmfsaysg8u yeah one thing *implied* by Context's docs is the ability/suitability to serialize a Context to pass it acrisd the wire\" to anorher service either in a local process or a process on a remote \u0026 separate host entirely. I suspect its because it gets harder to carry signals across (cancel timeout etc). but common need in a complex distrib arch",
"sig": "562ca14dcf3916530e8ebef37f62584049fb555db506c0c2e85b9798b3ee18eacc4db4367deb9819f37bc8a48a3835dbb59e537ab9fe20ccd34f701f0e0b7bb7"
}
