Oh... I see! We can't read the message, but all the other info is there... No doubt a privacy issue!
This happens because the protocol or clients are implementing it wrong?
Rics / Rics ⚡
npub1cl…zz5ge
2023-02-27 21:55:11
in reply to nevent1q…t62e
Author Public Key
npub1clpxewtk4j3akhmnztx68e6el0lsxpte0wn448u2nluhkaf9hwxsuzz5gePublished at
2023-02-27 21:55:11Event JSON
{
"id": "4f0c25a6f2c9c680ba29facece7cf8b501baa7dc6cd7073d613ee3ebb4b22c10",
"pubkey": "c7c26cb976aca3db5f7312cda3e759fbff0305797ba75a9f8a9ff97b7525bb8d",
"created_at": 1677534911,
"kind": 1,
"tags": [
[
"e",
"6b455584f49cec23b1046b9656632388719f79d884b5896b0a9c065bcd4a65cc",
"",
"root"
],
[
"e",
"e356ba75aebbbea9dd014d2df0ac295ad145d7c8ef2d81ac0bca427e14f230d5",
"",
"reply"
],
[
"p",
"595ca8eaace5899cb6ab7e2542bfc972136376f2eabc09287f1857eb8f167e53"
],
[
"p",
"c7c26cb976aca3db5f7312cda3e759fbff0305797ba75a9f8a9ff97b7525bb8d"
]
],
"content": "Oh... I see! We can't read the message, but all the other info is there... No doubt a privacy issue! \n\nThis happens because the protocol or clients are implementing it wrong?",
"sig": "a3c6dbf7948d972a953357e0e32f412ae63f1878ddcc7e27cf30345aebefeb370a332e21b4f5966d5c75633b2dcbb6a8317301f5cd7dfbe89e591c25d8103ce7"
}