Event JSON
{
"id": "a4e40017180ae3d305b3ea4740f5e4941d2fc416cc284bc44707e334022d28c3",
"pubkey": "5922f413ee9c41db68b99045cad95154121ba49701389582d62057ab7c2ab94c",
"created_at": 1695383035,
"kind": 1,
"tags": [
[
"p",
"5f9bb1a8dcc9c5d340d7228d66cbaf99b493e38721ffeba6d0714e4f7a2d9590",
"wss://relay.mostr.pub"
],
[
"p",
"ae3bf73746446a5edd319cef72033b539598a21ad07c2c2c4a84fbeaf22b835a",
"wss://relay.mostr.pub"
],
[
"e",
"6aa23724467f281d4955fa8ba6c054fbedd597b6af15eacba86cdfc19471558f",
"wss://relay.mostr.pub",
"reply"
],
[
"t",
"systemd"
],
[
"proxy",
"https://floss.social/users/gnutelephony/statuses/111108622631691492",
"activitypub"
]
],
"content": "nostr:npub1t7dmr2xue8zaxsxhy2xkdja0nx6f8cu8y8l7hfksw98y773djkgquzpqpp All I ask is do a device and do it well ;). I have lost redhat and debian systems out in the field using #systemd last decade. Usually it was an unexpected fail to boot fully, or a fail to shutdown properly, and a hang, and in all cases because some complete imbecile thought having logging tied to init and in a binary format was a good idea, there was no logs. I've had linux servers run from the 90's that never had problems before systemd. I cannot accept that kind of risk now.",
"sig": "9d1a64d7f03779b45cd4001c204362989a57864c3ced8cd20691fd182abc710b59fbf86f931b6cadbdfe03299ae8724d0123fc4b1dee00245a5b0dc7ae87f383"
}