Event JSON
{
"id": "adebbc2e7045549ce65857928fe088c136af591eb2246c4849c366e65418cdba",
"pubkey": "9a64dd44256e6741e56390a24c93311b2f8fe69dd81379b18b58fb9fec304a83",
"created_at": 1709663239,
"kind": 1,
"tags": [
[
"p",
"c176a55ed8a5f4240dd6154f81df0176998ba869d48bef575c47e33c9207d4b2",
"wss://relay.mostr.pub"
],
[
"p",
"3422fcbc32f333fb2d3481b2e981258af8a0b571869cbfe93c42962410e232ef",
"wss://relay.mostr.pub"
],
[
"e",
"cc1de1b01df98bc6d564848fc17a662cbacd9ad39cd79100a21ecd923c3fe8df",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://fosstodon.org/users/djspiewak/statuses/112044490031573334",
"activitypub"
]
],
"content": "nostr:npub1c9m22hkc5h6zgrwkz48crhcpw6vch2rf6j97746ugl3neys86jeqyz9xjd It does! It's precisely this, in fact. The way it works is you project a spanning tree over a subgraph and deliver that to the user, who edits it (returning a new tree), and then you reproject that back into the subgraph and splice into the whole. The corner cases involve arbitrary resolution, obviously, but they arise very rarely and are easy to steer around in practice when defining transformations.",
"sig": "949a2ded0f8cb185369102bd652120eb93a2b5ce365e09922eb0c3535293aab274df2b3ee69a4103c45dc0a4ba355a86c91734b322bc890efeff2a4ede455fd3"
}