Tetsu on Nostr: If you leak your private key, your DMs will be revealed. What do you think about this ...
If you leak your private key, your DMs will be revealed. What do you think about this idea to make DMs a bit more private… An option in your DMs to generate new pubkey and private key pair for each new “ghost” 🥷 conversation. Both sides would need to generate a new pair of keys to start a such conversation. Your DMs would not automatically store the keys. Probably DMs would need a sort of multiple key manager tool that would store private key only on the device. So if someone got their profile’s private key leaked, a random person trying to use it would still need a private key for each “ghost” conversation to read them. Could that be done?
🤔
jb55 (npub1xts…kk5s) fiatjaf (npub180c…h6w6)Published at
2023-02-26 11:03:57Event JSON
{
"id": "9ba07499f9735b71ad648799e4f95f38af582beeb75d7901c5e8e0562b0bcb78",
"pubkey": "8e432ad14d3955d0863b975778f0c8817ef88c9f119d626da1a3face584bda73",
"created_at": 1677409437,
"kind": 1,
"tags": [
[
"p",
"32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245"
],
[
"p",
"3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d"
]
],
"content": "If you leak your private key, your DMs will be revealed. What do you think about this idea to make DMs a bit more private… An option in your DMs to generate new pubkey and private key pair for each new “ghost” 🥷 conversation. Both sides would need to generate a new pair of keys to start a such conversation. Your DMs would not automatically store the keys. Probably DMs would need a sort of multiple key manager tool that would store private key only on the device. So if someone got their profile’s private key leaked, a random person trying to use it would still need a private key for each “ghost” conversation to read them. Could that be done?\n\n🤔 \n\n#[0] \n#[1]",
"sig": "5286883e72bfa7e089329dd4fabbfed0fdb903d1b717ffd77751f65b2e729c3b509d4a408a22f4fa867b6396361cf99ec370bfa68b7cea4da1e0b63e2e923aa7"
}
