Event JSON
{
"id": "1677eb3e3695c48555add7ad0058e68397251f1269f9371a9c4824423571e329",
"pubkey": "ad5b9561ddb832a7cb94cca32425960af920d1e10db323ff418e4a65d5568616",
"created_at": 1719632073,
"kind": 1,
"tags": [
[
"e",
"d516aa20fd3deffc08670906c417dbf6fb00b999c3fab387fa5135c8d364057a",
"",
"reply"
],
[
"e",
"f3c4555958034880ac71e36eb604437fa7a5133b7b25e85e8dea39056a66ba7a",
"",
"root"
],
[
"proxy",
"https://tech.lgbt/@sjolsen/112697807576131673",
"web"
],
[
"p",
"ad5b9561ddb832a7cb94cca32425960af920d1e10db323ff418e4a65d5568616"
],
[
"proxy",
"https://tech.lgbt/users/sjolsen/statuses/112697807576131673",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://tech.lgbt/users/sjolsen/statuses/112697807576131673",
"pink.momostr"
],
[
"expiration",
"1722314684"
]
],
"content": "I've written a program that just writes a file, forks, reads back from the child, joins, then reads back from the parent. it's 137 lines long, contains two wrapper functions that should just be in the standard library, references no fewer than five distinct integer types to accommodate different APIs, has numerous opportunities to accidentally invoke undefined behavior by screwing up a varargs call or passing the wrong buffer length or something, and is like 90% screwing around with statuses by weight\n\ncan you imagine if the last fifty years of computing had been built on an operating system and systems language that weren't comically obtuse",
"sig": "66d34d9f41806b86dc733c5a89427fddafeb7581d06f5e410133868a9762454e3dff47ab5c257dab5dbd5c0a994122339db4e2e436294afb403b938e1463f66b"
}