Event JSON
{
"id": "43e85ee757ccfb1a4a50526b6b4d88a1f498f5dc09812130caa5a5e82d2456e4",
"pubkey": "bd385aa0b579765c6883c5b0eb17e8ae350c988c659510be1e8453557ee38784",
"created_at": 1723494919,
"kind": 1,
"tags": [
[
"p",
"36f14c95a0ffa04e97c8abeacb24fbf0cdf84e6df0ff042be7501566da73e0c4",
"wss://relay.mostr.pub"
],
[
"p",
"4faf0628f38dfb9f151478a8f48ca9c34f9a9e5377f9be98d624c4f4e31fdfe2",
"wss://relay.mostr.pub"
],
[
"e",
"7b825d0bfd7268ec10660d4c32197a39d0c2fddd1f4044457a27b9eec3e2c16c",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://mastodon.social/users/glyph/statuses/112950963019960522",
"activitypub"
]
],
"content": "nostr:npub1xmc5e9dql7sya97g404vkf8m7rxlsnnd7rlsg2l82q2kdknnurzquqpjd8 oh I guess I was thinking of the OS-level “in use” error from fopen itself present on Windows and not UNIX, not just the general idea of locking concurrent access :)",
"sig": "acc8d7ba75bb1158c6ee1175d9eaf1f76c752fdd70ed42ead1ab8f00d5075ce1dc58c0c9c2074b1d3d1290a5affda1caade52fe412c6fa278076627010321314"
}
