Event JSON
{
"id": "c34dadb21c00086a98de06f7bf6fb9f8f1c25ffa331a2bb2d31fce75e2aaa773",
"pubkey": "da48c5d0523a83ddf35f5fd7b4916857ccac6c1b16853fa301641ed117991b11",
"created_at": 1721937997,
"kind": 1,
"tags": [
[
"t",
"Intel"
],
[
"proxy",
"https://mstdn.social/@osnews/112848928613882536",
"web"
],
[
"proxy",
"https://mstdn.social/users/osnews/statuses/112848928613882536",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://mstdn.social/users/osnews/statuses/112848928613882536",
"pink.momostr"
],
[
"-"
]
],
"content": "Intel: Raptor Lake faults excessive voltage from microcode, fix coming in August\n\nIn what started last year as a handful of reports about instability with Intel's Raptor Lake desktop chips has, over the last several months, grown into a much larger saga. Facing their biggest client chip instability impediment in decades, Intel has been under increasing pressure\n\nhttps://www.osnews.com/story/140327/intel-raptor-lake-faults-excessive-voltage-from-microcode-fix-coming-in-august/\n\n#Intel",
"sig": "d2626a151eda91cd5d933429d35790584a63358c83d03365f77f502fee663fc680c50c2315e9860e6e8f2467bbc2b16b42154f1c6a77f03a95c994f833241ef3"
}