Event JSON
{
"id": "6b1f00c876abcf1835dca2d1adc03413669e8dd5ea34ab905caac711897a7dbf",
"pubkey": "5468bceeb74ce35cb4173dcc9974bddac9e894a74bf3d44f9ca8b7554605c9ed",
"created_at": 1729703324,
"kind": 1,
"tags": [
[
"p",
"8aa8d4ed15679bc853e7a237f2b8d970b664b2289d2de51aa93bc96d85d01007",
"wss://relay.mostr.pub"
],
[
"p",
"81339f45601dbd2fa5c5b796752106668c456ce60e0179047bbf3c956bbaef3f",
"wss://relay.mostr.pub"
],
[
"p",
"b0dc384861f8928bb08b0c6a3351de80fe6b900220aac7e64a1e95e26b71396c",
"wss://relay.mostr.pub"
],
[
"e",
"ac0097ae9671280a83c0970766fa798496cc7f528435cc3bdce5a892c8bed3d0",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://grapheneos.social/users/GrapheneOS/statuses/113357837083773124",
"activitypub"
]
],
"content": "nostr:npub1325dfmg4v7dus5l85gml9wxewzmxfv3gn5k72x4f80ykmpwszqrsk6a6ka nostr:npub1syee73tqrk7jlfw9k7t82ggxv6xy2m8xpcqhjprmhu7f26a6aulsdxyqkc We're investigating it and believe there is a specific case involving the migration from permission state to Android 14 to Android 15 where users who disabled the permission at install time could have it reset back to the default. It wouldn't happen if users ever toggled it after installation. It requires a specific set of circumstances for it to have happened. The initially configured value has been kept but isn't used by the new Android 15 permission handling code anymore.",
"sig": "dd9caef282c91f81ac89efde2e1a76f83977b30012c631a940c922974f05c199a2d8f80d81d012c23563a3ea470e524654a8c3b77d4cc7e24e2daf1ec841c995"
}
