Event JSON
{
"id": "a661b9d4fcdc276065c9e3037767713396fd1d82cf9b31b6ced2cce6aef3a21d",
"pubkey": "385dcf054723039de641f3a7da5da6b39389900c7e1ec1e1071e5e9c305c92d3",
"created_at": 1721427858,
"kind": 1,
"tags": [
[
"e",
"54b0aa96f47cf6116e982997c6d783edde8a849fcaad32ac6fc437a0795a5a0c",
"",
"root"
],
[
"proxy",
"https://social.librem.one/@dos/112815496142531580",
"web"
],
[
"e",
"68913009b1d94f17b6264a1665a24f88cfc191b4efe699128b6d42c9cb2d769a",
"",
"reply"
],
[
"p",
"ea77f5584eeec06087f47a9fe82692723f1feb889eaf3e3b885997ec2e776aec"
],
[
"proxy",
"https://social.librem.one/users/dos/statuses/112815496142531580",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://social.librem.one/users/dos/statuses/112815496142531580",
"pink.momostr"
],
[
"-"
]
],
"content": "From what I've gathered so far from the ever reliable Social Media Feeds™ it appears that it wasn't a driver update, but rather a update data file that then caused the unchanged driver to crash when it tried to parse and apply it, which would effectively bypass the signing requirement.",
"sig": "964d57ea6eb323b31f6b10e5609a9e310329b5e4360cd6a176db648d127df35b108a7670013a228cb632da21ee54eb778b5fd725011f1fd1db775c4670d6213a"
}