b90c3cb71d66 -- 199d I mean it's close enough to impossible to do that you'll give up trying. Think through what clients would have to *actually do* in the case of someone having their nsec taken by an attacker and creating a new one that friends validate. It's like subkeys and Vitor's response here, sounds great in theory but when you think through what clients would have to *actually do* to reconcile the subkeys you realise it's a non starter. There's a different such list for this main key respawn scenario, but it's equally off-putting. https://image.nostr.build/b4c3a4342cc3433866c83717fd0023bfa4d8896805d74abe3cb0071db68f615b.png reply [1 reply]I mean it's close enough to impossible to do that you'll give up trying. Think through what clients would have to *actually do* in the case of someone having their nsec taken by an attacker and creating a new one that friends validate. It's like subkeys and Vitor's response here, sounds great in theory but when you think through what clients would have to *actually do* to reconcile the subkeys you realise it's a non starter. There's a different such list for this main key respawn scenario, but it's equally off-putting. https://image.nostr.build/b4c3a4342cc3433866c83717fd0023bfa4d8896805d74abe3cb0071db68f615b.png
thread · root 8769fdef…159d · depth 8 · · selected bfc48ca1…2b6b
thread
root 8769fdef…159d · depth 8 · · selected bfc48ca1…2b6b
*sigh* I was careless with my security and someone got ahold of the nsec private key for this account. Pleaseunfollow and ignore and don't respond to DMs. I'll make a new one with video proof of identity tomorrow. -AdamSoltys
happened to me too. I still use the garbage nsec cause it's a hassle to start over on nostr.big problem with nostr IMO, but cannot be fixed without a protocol fork.
Disagree. WoT fixes this
How? It's not like Farcaster where you can have your trusted people sign off on a new main key. For nostr therecan only ever be one main key per human. Best you can do is keep it very secure (not easy) and rely on bunkers,signers, etc. we all know the drill .
you precisely can have your most trusted people attest to your new key. exactly what you said.
right but nostr, unlike Farcaster, cannot swallow that. Farcaster your FID belongs to the chain and your mainkey is control over it, so such a thing can work. Nostr the buck stops at your main key, which means you'd beasking clients to do something that clients cannot physically do in terms of stitching old you and new youtogether.
You're right that the tactics are quite different between the two systems, but you're wrong that the generalsolution "impossible" on nostr. It just employs different tactics than Farcaster.Feel free to prefer the blockchain solution if you like.I prefer the tradeoffs on the WoT side.
I mean it's close enough to impossible to do that you'll give up trying. Think through what clients would haveto *actually do* in the case of someone having their nsec taken by an attacker and creating a new one thatfriends validate. It's like subkeys and Vitor's response here, sounds great in theory but when you think throughwhat clients would have to *actually do* to reconcile the subkeys you realise it's a non starter. There's adifferent such list for this main key respawn scenario, but it's equally off-putting.https://image.nostr.build/b4c3a4342cc3433866c83717fd0023bfa4d8896805d74abe3cb0071db68f615b.png
happened to me too. I still use the garbage nsec cause it's a hassle to start over on nostr.
big problem with nostr IMO, but cannot be fixed without a protocol fork.
vinney...axkl -- 200d [parent] | reply [1 reply]Disagree. WoT fixes this
b90c3cb71d66 -- 199d [parent] | reply [1 reply]How? It's not like Farcaster where you can have your trusted people sign off on a new main key. For nostr there can only ever be one main key per human. Best you can do is keep it very secure (not easy) and rely on bunkers, signers, etc. we all know the drill .
vinney...axkl -- 199d [parent] | reply [1 reply]you precisely can have your most trusted people attest to your new key. exactly what you said.
b90c3cb71d66 -- 199d [parent] | reply [1 reply]right but nostr, unlike Farcaster, cannot swallow that. Farcaster your FID belongs to the chain and your main key is control over it, so such a thing can work. Nostr the buck stops at your main key, which means you'd be asking clients to do something that clients cannot physically do in terms of stitching old you and new you together.
vinney...axkl -- 199d [parent] | reply [1 reply]You're right that the tactics are quite different between the two systems, but you're wrong that the general solution "impossible" on nostr. It just employs different tactics than Farcaster. Feel free to prefer the blockchain solution if you like. I prefer the tradeoffs on the WoT side.
Do you think building and properly decentralizing a blockchain for this purpose is more feasible? Be more explicit about what you're proposing as an alternative, if you are doing so.