I think the lack of key rotation is the biggest obstacle to these things you mentioned. 🤔

Personally I think it's not a huge deal for users. But businesses will want control, and they'll see the key system as a huge vulnerability and oversight. It's optimized for user freedom, which in a business would enable stupidity in uncontrollable ways.

Reply to this note

Please Login to reply.

Discussion

I've drafted a heretical centralized approach that let's the user still be sovereign over their root key

nostr:naddr1qqgrxwfj89nrvepkxq6njc3sxf3n2qg4waehxw309aex2mrp0yhxgctdw4eju6t09upzqvr92hlwgse4s2ej7m2x7ydkgndr8zt9j5qk3y7hmgvvwh7hlhcjqvzqqqr4gu3jp7lg

Ignore Frost in the title, I took that bit out (looking forward to playing with my Frostsnap when it arrives.... soon!)

Business have full control. They control the relays. What's a key without read/write access to the business's internal relays?

Keep in mind this is BYOID, the bring your own aspect being something businesses actually want (often for legal reasons), they just want it to work better. For other forms of BYOID, such as a frontline worker using their own Google account to login to the company's slack, the company does not have control over that user's Google account and that's fine, it's the application or infra layer where control resides.

The real question is not why nostr keys for comapnies but why redundant websocket relays for companies