Event JSON
{
"id": "0f2ca59d6dab3315cc483583a4b55ce7a3d3ed7c2833d719be9b6aa98d2fe796",
"pubkey": "b3ba3c5045fbaf99be9cb4daa9f1d7baeedaba0fc5b91596511e2fb7a70dd7f9",
"created_at": 1721402608,
"kind": 1,
"tags": [
[
"e",
"ea030df7417c373492391f421ac335e582a3b8b62763fd8f160cd98eb8b71335",
"",
"root"
],
[
"p",
"b3ba3c5045fbaf99be9cb4daa9f1d7baeedaba0fc5b91596511e2fb7a70dd7f9"
],
[
"p",
"aa3b4d495a4a96556fcce5ffa15183eb33a74102b3bd7254039c030980103598"
],
[
"proxy",
"https://grapheneos.social/@GrapheneOS/112813841341749535",
"web"
],
[
"e",
"16fee2f95f9b9aa70ccf33cc0a724f26ad3a9af956b38a52efcfb8da26a1bd76",
"",
"reply"
],
[
"proxy",
"https://grapheneos.social/users/GrapheneOS/statuses/112813841341749535",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://grapheneos.social/users/GrapheneOS/statuses/112813841341749535",
"pink.momostr"
],
[
"-"
]
],
"content": "An interesting part of it is that the iPhone data classes for keeping data at rest while locked don't work since Cellebrite has an exploit for obtaining the lock method as part of an exploiting an AFU device, which they mark as IPR in the table.\n\nIt's likely they've partially caught up on iOS version support since April 2024. They may be fully caught up. It's strange to present it as if they would have done absolutely nothing through April, May, June and now part of July.",
"sig": "4fd3602b68e62f6874d36fe8bba5999cb6daf97bc7b0e67217caab496e391ae92282646b98c52804a4d5f295b280f330c2a8728cb9748449b9d1af6dd90bb77f"
}