That’s a long post. Trailer goes like this. Start with identity in business systems, Okta, Entra (née Active Directory), Ping Identity, Google Cloud identity, the rest. These don’t work well for frontline workers, vendors, and so on, for many reasons, cost just one among them. And depending on the company frontline workers can far outnumber desked workers.
There’s bring your own identity, which is a thing (sign in with Google, as in your own Google, and so on) but now you’ve brought the worker's personal baggage into the corporate picture. Then you have to think how can nostr identity offer a more baggage-free BYOI? And the there’s OIDC in the background, how can that be bridged with Nostr (OIDC is ED curve but still doable). Sure a lot of work to augment nostr identity for a hybrid business setting, but doable, and could be pretty attractive if you can articulate to these businesses what it solves in BYOI realm (there is a solid pitch there).
Then once you see that there’s a use for nostr identity in the frontline and vendor space it’s about what to build on top of that identity foundation, vibe-coded internal apps that make sense for frontline workers in unique frontline situations. Shakespeare stack could rock that. (None of this touches nostr the existing social network in any way.)
We're rolling out a few things along those lines out in Asia, but never do we say the word nostr when describing what they are and do.
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.
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!)
Thread collapsed
Thread collapsed
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
Thread collapsed
Thread collapsed
I'd be very interested to learn more about what you're doing here too.
Thanks, happy to share. And likewise.
I have to make a new proper nsec, this one is exposed and now garbage. That's my afternoon task!
Thread collapsed
Thread collapsed