LionDietLeo on Nostr: #asknostr Why does #nostr not handle user's keys differently? What would be the ...
#asknostr
Why does #nostr not handle user's keys differently?
What would be the drawback of a system such as this:
Relays store nsecs in encrypted form.
Users/clients log on with just a username and a relay returns that user's encrypted nsec.
User/client then decrypts the nsec in whichever way it was encrypted.
The rest happens as usual.
Users could opt to either give their nsecs to the clients they use to connect to the network themselves, or to have the client obtain the nsec from relay(s) and decrypt them with a password/certificate/whatever.
Published at
2024-08-31 10:48:14Event JSON
{
"id": "17c93344a6a33813b410e3361ed8b9f532c941c46413f7021113632ccf9b80fd",
"pubkey": "a687c81a6f5f61c2c1010f58054f7fec697c9d14a11f3a39fcbd306f6d642670",
"created_at": 1725094094,
"kind": 1,
"tags": [
[
"t",
"asknostr"
],
[
"t",
"nostr"
]
],
"content": "#asknostr\n\nWhy does #nostr not handle user's keys differently?\n\nWhat would be the drawback of a system such as this:\n\nRelays store nsecs in encrypted form.\nUsers/clients log on with just a username and a relay returns that user's encrypted nsec.\nUser/client then decrypts the nsec in whichever way it was encrypted.\nThe rest happens as usual.\n\nUsers could opt to either give their nsecs to the clients they use to connect to the network themselves, or to have the client obtain the nsec from relay(s) and decrypt them with a password/certificate/whatever.",
"sig": "aaf1629c8bfeec57a70544a963f99050d3262801554dea0f0f2e277396ac4b3a8be058fe8222198b5e324e77bffc1958d21875f176b36f699817ceb1ad3c8e18"
}
