Event JSON
{
"id": "a0c991271e51df3c2f82f6d2add7e92e569f77257dc9fbcca446416daf3fe725",
"pubkey": "ab8ea413dc11257cecb89a951cce015fa9cfe703535339410ee9bd6ecfe4a7bf",
"created_at": 1731155813,
"kind": 1,
"tags": [
[
"p",
"7e00ff73e9263c457ce3c0ac5847483cb545823bd1ac5e40f71c79dad969df40",
"wss://relay.mostr.pub"
],
[
"p",
"f3eaf89270fc0355ce2a91d69bca71c340a0a38b7c833b8ff837e8aaa0c98e82",
"wss://relay.mostr.pub"
],
[
"e",
"fbdd5381eba2a78111f2194da6f33879b0428e440f501f51bfdbe12114c52d90",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://not.acu.lt/notes/a0dpsbubf9",
"activitypub"
]
],
"content": "nostr:npub10cq07ulfyc7y2l8rczk9s36g8j65tq3m6xk9us8hr3ua4ktfmaqq9a6nm3 Yeah, amdgpu is my main suspect, but it's a pain to track down since it's just a dma structure which will end up being used all over the kernel that is getting leaked.",
"sig": "f1e4af86d31a2cd4be930d4b6fbca9f56e301bd6050948ae2029e76174ad7dd4f3798041977a9111bfe2fdb51acfc7bb06deee3410948abe66c5f5231e5c1cb6"
}
