Event JSON
{
"id": "9f7ec623363094aa2ec4a2ee5fc5c2c94be462ed222fd8487dd9dc4ac27c37df",
"pubkey": "d764d824dca84aac6b536decc82412a77d9e6c9e4dd3bd36d4141dd2a5a7fff7",
"created_at": 1735323950,
"kind": 1,
"tags": [
[
"t",
"grapheneos"
],
[
"t",
"messenger"
],
[
"proxy",
"https://mstdn.social/@DM_Ronin/113726190409887925",
"web"
],
[
"t",
"signal"
],
[
"t",
"android"
],
[
"t",
"privacy"
],
[
"t",
"whatsapp"
],
[
"proxy",
"https://mstdn.social/users/DM_Ronin/statuses/113726190409887925",
"activitypub"
],
[
"L",
"pink.momostr"
],
[
"l",
"pink.momostr.activitypub:https://mstdn.social/users/DM_Ronin/statuses/113726190409887925",
"pink.momostr"
],
[
"-"
]
],
"content": "man how much I love Signal/Molly compared to WhatsApp even from UX (contrary to some people who tell me \"Signal is too difficult\")\n\non GrapheneOS it is possible to set contact scopes (which works similar to media scope), but while adding scope for Signal/Molly doesn't make linked contacts, WA does that, so even if you remove access, that WA duplicate persists as read-only\n\nremoving them requires to reinstall WA \u0026 add scope by number\n\n#Privacy #Signal #WhatsApp #GrapheneOS #Messenger #Android",
"sig": "6334629fa20cd1320dfd0d1b07979eb5331c3738474a80f0ec95e054a78a4c6ad7d8759761fb7f73172f896e42ed381041e310e9465ec2307699367634eca3a0"
}