Event JSON
{
"id": "63fca58f9c2d4af1a9ac6cee7364cf865c346b86e8e0648893aa172fa18918d6",
"pubkey": "21a6865f238f3867dfcef74b82d389f4b5bbddd7fafdb6d8443ecc9d151fc9c9",
"created_at": 1707545059,
"kind": 1,
"tags": [
[
"p",
"3f770d65d3a764a9c5cb503ae123e62ec7598ad035d836e2a810f3877a745b24",
"",
"mention"
],
[
"p",
"fa984bd7dbb282f07e16e7ae87b26a2a7b9b90b7246a44771f0cf5ae58018f52",
"",
"mention"
],
[
"p",
"460c25e682fda7832b52d1f22d3d22b3176d972f60dcdc3212ed8c92ef85065c",
"",
"mention"
],
[
"t",
"asknostr"
],
[
"t",
"asknostr"
],
[
"t",
"nostr"
],
[
"t",
"nostr"
],
[
"r",
"https://i.nostrimg.com/1df094eb9a809f98b1efbb9ed2077e45b19cbd084bd76eeb589dd808bec9f42e/file.jpg"
]
],
"content": "#asknostr #nostr\nDid you know that any client will let you login with someone else's public key as a read-only user, but you can still view all their notifications and messages? The message itself is encrypted but the sender isn't. \n\nhttps://i.nostrimg.com/1df094eb9a809f98b1efbb9ed2077e45b19cbd084bd76eeb589dd808bec9f42e/file.jpg\n\nSeriously, why does it even let you login without a private key? What's the purpose of read-only accounts? Am I the only one who thinks this a huge design flaw? Not to mention creepy, wrong and kind of violates any argument for privacy?\n\nnostr:npub18ams6ewn5aj2n3wt2qawzglx9mr4nzksxhvrdc4gzrecw7n5tvjqctp424 nostr:npub1l2vyh47mk2p0qlsku7hg0vn29faehy9hy34ygaclpn66ukqp3afqutajft nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z and if y'all can boost this to other people involved in either ecosystem or protocol development, would be awesome. Or maybe it's just me 🤔",
"sig": "2946c548596c6e73129bb19771413c0ed4b87ecb122d7d3d98d8c4fc1c8bd4c04ea305ed6d6e0002705a98324bee2c2b908c1b5d08ec7d69836614eaeebf404a"
}
