Event JSON
{
"id": "ff9f04280decbc803d00d4f8a45c942c37701b4925eb1d147c53d9eeadec8f0c",
"pubkey": "c6255f96b8978d71f6d0ddc931fd3e7e23f7c7cc4b92d77285c1934480175149",
"created_at": 1735684158,
"kind": 1,
"tags": [
[
"p",
"8f7b8e8340cd01e21d0a5a8235b20bd3ddf526b911310ffd0b4e4744b68bd6ce",
"wss://relay.mostr.pub"
],
[
"p",
"e7d3ba19c4508bbdc75e164a5f1f5dbaa9acb1dc0368e603c269656647049373",
"wss://relay.mostr.pub"
],
[
"e",
"7d7791802b09cbf79d4c84f9319a3c6bae2975a31c56870ea97c83b99451115d",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://m.unix.house/users/jmc/statuses/113749797024326243",
"activitypub"
]
],
"content": "nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq3aacaq6qe5q7y8g2t2prtvst60wl2f4ezycsllgtfer5fd5t6m8qcsrdje I will say that I have redone quite a lot of shell programs as Rust programs with a similar amount of forking children to do things, but in those instances I'm the one writing the Rust it's not a framework per se. Also it's nice to be able to do the HTTP stuff from a library with a more expressive error handling plane than the curl CLI.\n\nThat said, the CI system I wrote at Oxide literally just runs bash programs so you can kick off whatever you want with it!",
"sig": "3c384779f2dd5dbd876147b2b45bfdb410509daff4812326ee20781ee6cd7b4153055ad21a8fe03d63e75cc4d924ecee798cb6e9c391f9c45a8e359c8e20caa6"
}