Event JSON
{
"id": "1ac858a3d6581ccd840498bfe4b3020fb339fa82c62437439d13bf783281d9a6",
"pubkey": "5468bceeb74ce35cb4173dcc9974bddac9e894a74bf3d44f9ca8b7554605c9ed",
"created_at": 1737512451,
"kind": 1,
"tags": [
[
"p",
"b3c069b58b7bd38627103cdd8913cb9ace41a4433779919c43bdf10e92727286",
"wss://relay.mostr.pub"
],
[
"p",
"2ad7a1e593da1f9ab0640625e6a9754e3cc42ef2be878a09adb16f96084453ae",
"wss://relay.mostr.pub"
],
[
"e",
"ec4131cf44040872b27ab7fb8ad9e30c7ea0a12fe51e1d765267a7f186c9a7c0",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://grapheneos.social/users/GrapheneOS/statuses/113869616034352093",
"activitypub"
]
],
"content": "nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqk0qxndvt00fcvfcs8nwcjy7tnt8yrfzrxauer8zrhhcsaynjw2rqefttyj https://docs.seon.io/ is one of them. We don't know all of them or which one is directly responsible for specifically banning GrapheneOS but it's a high chance it's that one.",
"sig": "6e4c0ceb754f358580a3c4833929e031c60c2f259bcc9ce2ca93dafd196ed3929726f3b0f98b0a64ad6072705b58668bd198aca7138100f15f8713b23452f1b5"
}
