This all looks cool, but it's all diminishing returns. We need something significant to make a 2.0
Discussion
Fair take. I was trying to judge if what we have is already significant.
My nsec is a slut. She's been in every client. I cannot undo that and I can't revoke it and roll a new one without losing a substantial audience. And it's been two years now and all the proposals around this issue have stalled. For me it is too late, but for new people joining nostr I want them to have the ability to have secure keys. Maybe this can be done in nostr still.
Clients authenticating relays could also probably be done in nostr, albeit a lot messier.
When I think about the paths we have to take to solve these things I get overwhelmed.
NIP-07 extensions and NIP-55 signers are pretty good. NIP-46 is less good IMO (too slow). Delegations will never work (IMO). FROST might work, but it is quite complicated (managing keys for each app/device etc)
It is overwhelming indeed. But no protocol is perfect. We shouldn't be trying to solve all of it in one. The goal is to find a set of decisions in each of those buckets that work so well together that can 2-10x Nostr even though we know they are not perfect.
nostr can easily put me into async brainlock "3xception: promise not found"
probably fine 🔥