Event JSON
{
"id": "164710478adfccab362589ae45a2308783865a8c006cd89c04f0576bfd54f07b",
"pubkey": "8078b2e54466503ee8694ce5e7be1251c22e1aca9d8f66e4fbc1776c2bdeb45c",
"created_at": 1735319691,
"kind": 1,
"tags": [
[
"p",
"c62faae4d26181b569c0115478d3f48d86c72ac5df2303bebba6de39df624983",
"wss://nostr.sprovoost.nl"
],
[
"p",
"56a700dfdd558b86eacd1d7097838aa86f4e33df22a8d3c0890cd9638e144578",
"wss://nostr.sprovoost.nl"
],
[
"p",
"20930bb37c402b36d6577333ebddc01318bf20a854617e8c544d1cd623541954",
"wss://nostr.sprovoost.nl"
],
[
"p",
"ef64a13c28f3b747b81b2bf7811aad358f037982647c69be4a0f191f4816e7d0",
"wss://nostr.sprovoost.nl"
],
[
"e",
"0fafb4b9ab792e2e376535abc5da3284f546c8cf7b1e132bbba88b0941627e83",
"wss://nostr.sprovoost.nl",
"reply"
],
[
"proxy",
"https://comp.lain.la/objects/0e9133e3-b497-414e-9eb9-49494f8a210c",
"activitypub"
]
],
"content": "nostr:npub1cch64exjvxqm26wqz92835l53krvw2k9mu3s804m5m0rnhmzfxpsjwf8nu nostr:npub126nsph7a2k9cd6kdr4cf0qu24ph5uv7ly25d8syfpnvk8rs5g4uqu5fq05 OK, but you DO know who you are talking to in your example. You are talking to a registered domain with an TLS compliant web server secured by a valid cert. None of the technology aspects here have failed. It is not the problem of TLS that this happens to be an impersonating website, in that it's not email's fault there's so many phishing attacks, and it is not LE's job to play internet police. If it was, we'd have a much more significant problem.",
"sig": "84767f033b82d5d278222194335accaeeb67c5172ac0160fcd7f127f967bc400425db0b85522082975cfc31492245e4e86371c4392310f6787db4f2bc0505b88"
}
