Event JSON
{
"id": "df7a6ddfdbe2e44c6139f4b6ab5c5d06669f0a594891eb2bfb8d9d44f3f3b80c",
"pubkey": "e0b1683ecdb59c290da4504cef66ba52d3bc992ed7832af2009fc727e529db9a",
"created_at": 1723640860,
"kind": 1,
"tags": [
[
"p",
"0d68fe859191e5b04b0b8b5a9b7c5c81889b5880088c6a8631e3ca53484c4b9d",
"wss://relay.mostr.pub"
],
[
"p",
"783f5e8607f5b88c53c6c6a334445e79376235013841bc40db7c59eeb7b9e94b",
"wss://relay.mostr.pub"
],
[
"e",
"49d8f60aa9b97df81fe70f178aa0623a39846aed5ad870900701bb5d6132a72c",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://infosec.exchange/users/inetpro/statuses/112960527450600969",
"activitypub"
]
],
"content": "nostr:npub1p450apv3j8jmqjct3ddfklzusxyfkkyqpzxx4p33u099xjzvfwwsw789jz that’s fascinating! Thanks for the interesting explanation. Let’s hope someone at Microsoft sees this and addresses the issue soon.",
"sig": "81b0355896178a0603ebf92ec5eb2ca2e670f5fdc6aa4f855e7474525ef59e84f516c7fc946952434b553c697ea31e4cb1363d7b0a95157e5fd59b984f8e5898"
}
