Event JSON
{
"id": "240440b06c61be0d3ce39231d7bdcdb87dd132a75d7a74d0c89c80403ded1d33",
"pubkey": "672a2127d3808517a2154b787bf257a228167abacca53b5a48e16f7744f9accf",
"created_at": 1720501848,
"kind": 1,
"tags": [
[
"p",
"058a6d106c5e6719008ce4db3f64c846caf49925227a39533d12a846fbab21ee"
],
[
"e",
"daa45331d1b274113c244ddd78c87d7e1676335ef3e70a7d41aab4023e085681",
"",
"root"
],
[
"e",
"c416bc6b13026ce7f32d547c07e7a22f80e9e3242708cf49fc246620a9b06ee3",
"",
"reply"
],
[
"p",
"b2af1162c86c3edbbbd2f762418956671e9e825e8011dcbb6573758b4167845f"
],
[
"proxy",
"https://better.boston/@vathpela/112754809125381331",
"web"
],
[
"p",
"672a2127d3808517a2154b787bf257a228167abacca53b5a48e16f7744f9accf"
],
[
"proxy",
"https://better.boston/users/vathpela/statuses/112754809125381331",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://better.boston/users/vathpela/statuses/112754809125381331",
"pink.momostr"
],
[
"expiration",
"1723099580"
]
],
"content": "okay, so DT lets us write to the boot options? If so we probably don't need uboot (might be a useful intermediate, might not). We already have the userspace signal, so that will be a useful thing to hook up. (It sounds like you're implying it's pretty straightforward?) The real question is how hard it is to do a one-time boot option and can we have multiple boot options and change the order atomically. The former we can fake with counters and reboot, the latter...",
"sig": "e6d48ba887f9c9350de892b3574b45b2266cb688e30739d4a8a5bc933bf71137e9b04c744a586c8f99f6b6481381cd29ae97b057a21ed768d768bcccd89e7e40"
}