Event JSON
{
"id": "1704c7bfde800eaa2cf7af318e97d58eaf92b1bb43ccd6c2ee181522f77589c2",
"pubkey": "5468bceeb74ce35cb4173dcc9974bddac9e894a74bf3d44f9ca8b7554605c9ed",
"created_at": 1742074768,
"kind": 1,
"tags": [
[
"p",
"125c39d113f951bfabf319edbe8c0d834a4fe7dfa0d8c3d42313d17900f3c8c7",
"wss://relay.mostr.pub"
],
[
"e",
"6bd7827ecac7b1245fa9d90b31c745fef39f5dbf229e8b55bcad4171b59191af",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://grapheneos.social/users/GrapheneOS/statuses/114168612019997419",
"activitypub"
]
],
"content": "nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqzfwrn5gnl9gml2lnr8kmarqdsd9yle7l5rvv84prz0ghjq8nerrszsputu It very likely didn't. That's just a Pixel 9 specific issue with Android 15 QPR2 which comes and goes with reboots. If it doesn't work you can reboot until it does. See here:\n\nhttps://discuss.grapheneos.org/d/20636-workaround-for-android-15-qpr2-fingerprint-firmware-glitch-on-pixel-9-non-pro",
"sig": "77371680b88479cea3a06ac0b8096ac6ec9a2cadb467a976139363f426a6b7399887e3370b66412581dc9988168896151cd2d32b17e55aa5748c56fb7a8f2cc2"
}
