Event JSON
{
"id": "5856104663176f0cd63d58b26436c56330bed35349abe303bf9e8ef75e1f441c",
"pubkey": "fd78ea493e466e5403543ba50475e8acc79157ea3bab423b53f780a89c92423e",
"created_at": 1732056431,
"kind": 1,
"tags": [
[
"p",
"8ceaf2ff15695cfd1b80e0c76b5ebb5b45857538a6dfe5dad856b9e0abf803ea",
"wss://relay.mostr.pub"
],
[
"p",
"967c6f3bb809d3ae791381503ec70d0da6a7ec7366f83b7c046e72d0a0748e98",
"wss://relay.mostr.pub"
],
[
"e",
"b4070d955a5959516704896461de8b3a449fa89925be91a1603e0976f0892ad4",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://infosec.exchange/users/tychotithonus/statuses/113512050290413170",
"activitypub"
]
],
"content": "nostr:nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpq3n409lc4d9w06xuqurrkkh4mtdzc2afc5m07tkkc26u7p2lcq04q2kq5wq Oof - but where's the Ancestry tie-in specifically? (Article mentions related incidents, but doesn't list Ancestry as a customer of this company?)",
"sig": "2285280339fdc8e3af163f2161d158debcf3a5d8b45b7ee07e902e554c6483258b03840909cc1f04125180f31f38f931b71588fd9d3ab8ee945f09ba8af22264"
}