Event JSON
{
"id": "f7705779870376cab2786429f0fcde3e0abff2ae958bbe7babfe042bbcd8df4b",
"pubkey": "9a64dd44256e6741e56390a24c93311b2f8fe69dd81379b18b58fb9fec304a83",
"created_at": 1697643586,
"kind": 1,
"tags": [
[
"p",
"54814b2fe4532ebababaf5bbffeb2f7707ce45a922b7bafa280121f24cdde453",
"wss://relay.mostr.pub"
],
[
"p",
"2464a99bb3a2cface2d500032721fbdb4f036b4c92624d2039a11cc2d6a744a4",
"wss://relay.mostr.pub"
],
[
"e",
"5c39653981fb9e6701fe09d2b74d33d37dd94e0b2346bdaf8a7644ac991b292a",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://fosstodon.org/users/djspiewak/statuses/111256770087486656",
"activitypub"
]
],
"content": "nostr:npub12jq5ktly2vht4w467kall6e0wuruu3dfy2mm473gqyslynxau3fsakhq6m The even deeper point Arman is making is that some I/O is just fundamentally blocking because that's just how the hardware itself functions. No syntactic magic can paper over that fact. Btw it's not just Loom that falls into the trap of trying to massage this. io_uring perpetrates the same falsehood.",
"sig": "01dddedbc86867379e1ce1e89f6c74cee4335c84d3c85b3cba14b04977dbc580408c6836717deef35c77c98784339f6a10d5402eb75600112a46b72f8c0fbbc7"
}
