Event JSON
{
"id": "533d4cb4707ddb954219628df0345e9c4ea14b6d24c7c0b0db1216d9822024f0",
"pubkey": "468cd334b9541b551189215c4c31b0af3e2e45a24eae6d6977e0726dbb3cd455",
"created_at": 1703013700,
"kind": 1,
"tags": [
[
"p",
"25909bc3f5e5964671db1111aafac25f4f2432f36c9fb64330eea81ac16b6ded",
"wss://relay.mostr.pub"
],
[
"p",
"db6c47ce5071184d6606b9755e84c5ceb7b72cfddd5dc05a2d85035313bd629a",
"wss://relay.mostr.pub"
],
[
"p",
"bf62a0ea6de8d2591e8dcc35618a232a6ef57d27c55176f1a161be81df421968",
"wss://relay.mostr.pub"
],
[
"p",
"faaf81ec8b66e5875dcb43e3b02a509ff4a36869da2ba49ed4bab1a1c5b0b328",
"wss://relay.mostr.pub"
],
[
"e",
"f9cb432c84e958141f86837173ac7f465fb0d83869550bfb4a84ca919519d24f",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://social.shadowfacts.net/objects/83bdc89f-c1cf-4e49-aa42-07e602ecf74d",
"activitypub"
]
],
"content": "nostr:npub1ykgfhsl4uktyvuwmzyg647kzta8jgvhndj0mvsesa65p4sttdhks3sg4jv nostr:npub1mdky0njswyvy6esxh964apx9e6mmwt8am4wuqk3ds5p4xyaav2dqvlaptk I don't think that's the case? an Announce activity can in principle embed the object being announced, but afaik every major implementation references it by url. so the receiver of the Announce (Threads) would have to dereference the announced object, which would fail if Sue's instance enforces signed fetch",
"sig": "1cc7e362c28ba452949c0c8433b0314233cdd1a0478f6c28c311f9e3c9dc21a9304a96ce8474f45a6c38acc32097a634b759ce378783f4a46e8251928baf4163"
}