Event JSON
{
"id": "c3eae45220c253fc1bc126508cbf5bf3386a32b9529d2ea0000ed94abad25e7d",
"pubkey": "5468bceeb74ce35cb4173dcc9974bddac9e894a74bf3d44f9ca8b7554605c9ed",
"created_at": 1739358861,
"kind": 1,
"tags": [
[
"p",
"bbdbf6944b85afe7a096abbb69c1aad27770c989818568756196fb6ebdf0203a",
"wss://relay.mostr.pub"
],
[
"p",
"4d9f439d835b63b76f68fb2368fcef7ce6c1d031aaf7713c7292ef5802549f52",
"wss://relay.mostr.pub"
],
[
"e",
"16b47eb9dfc1e8c0c318b7548ec145cec6ed5a8dec3cb59efc8479da2ae224f1",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://grapheneos.social/users/GrapheneOS/statuses/113990622326690945",
"activitypub"
]
],
"content": "nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqh0dld9ztskh70gyk4waknsd26fmhpjvfsxzksatpjmaka00syqaqx03nsk We do since we have to reboot for the Linux kernel LTS updates which are generally around that frequent. The uptime was only a couple days before this at most. The service didn't simply crash which would have just resulted in it being automatically restarted. It managed to take out nginx and then eventually OpenSSH too because of the machine locking up from paging in and out from storage, etc. while under huge I/O load.",
"sig": "6483bcd7c8786fb36d181bc7deca418b51a373caa973c6d33e05fc2f740ad6aef85cd72c11de96002b3354e693861c2f8d55f8f82c05f74dfe1b01d82131cb74"
}
