Event JSON
{
"id": "0717537ffb2b0a2abd54087e7ef6ae1203331939996c3550e0b8700ec333d11c",
"pubkey": "1d95c32d9a9d95a54f98eb2eaa156f3d3a71dc49eca2c960b2b89962758f1cc0",
"created_at": 1733738571,
"kind": 1,
"tags": [
[
"p",
"b722fd86f0d1d688bf15949ed3bd1a29c7983399f3ef71b27d7198d4f4150bf9",
"wss://relay.mostr.pub"
],
[
"p",
"ffc65ee9353067ef6edc6a9bba182b5051329c03324824fcb5da0fe829c2bc07",
"wss://relay.mostr.pub"
],
[
"e",
"acc44f7468ee28ae4991fd445086281cf60a34bd76a07cf51f541bc0280457ec",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://mastodon.social/users/pid_eins/statuses/113622291042219126",
"activitypub"
]
],
"content": "nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqku30mphs68tg30c4jj0d80g698resvue70hhrvnawxvdfaq4p0uspv3dhj also note that unless some service asks for a reboot there is no reboot. Hence, everything logind brings to the table here is that it now provides a centralized mechanism to configure the reboot time, if tools ask for it, it does not introduce any automatic reboots that wouldn't be there anyway. If anything it *reduces* the number of forced reboots, since it defines clear colaescing of reboot requests rules.",
"sig": "188ef1e0af4a8f8bbaaa17873c8e02d78a91afe5a3c3c56554e614ed3f878888db2feeb3beac7abd70ca293baba99b41cb66500f6bb375ce606899f03d77ebde"
}