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.

Its the early hours of the morning here so, quick thought and can flesh out later.

1. I was vibing a docusign using nsec signing. Few lazy afternoon sessions and good progress. Docusign market cap $16.5B. I don't need or want to do another startup, let alone a replacement strategy play but a small team could displace chunks of the b2b stack with new economics. Pipedrive disrupted Salesforce. Can a nostr CRM disrupt Pipedrive because trojaning npubs into business is 🔥. But don't talk about nostr, talk about solutions.

2. nostr:nprofile1qqsphkn7raeed0dz68hejqea4r7jmsmzsyrephumuch4jypchwtufkgpzemhxue69uhkummnw3ex2mrfw3jhxtn0wfnj7qghwaehxw309aex2mrp0yhxummnw3ezucnpdejz7qgewaehxw309aex2mrp0yh8ymmyvf5hx6r0wqhxu7303hr2v8 may want to share what he is doing. Another sector with significant incumbent revenues and less friction.

3. The point being, products (not hobbies) first. Monetization is a deliberate act. Jack can code bitchat without concern for monetisation. But that is a byproduct of silicon valley success and mindset. I've built startups outside SV and you have to be pragmatic about monetization.

4. There was an excellent 30023 about a year ago by somebody who tried to build an app using relays as a data store and how slavish commitment to a protocol may be the wrong formfactor for the solution. Maybe some apps just stand on the shoulders of the protocol but aren't prisoners to its original libertarian ideology. It's a protocol so you need zero permission to use it in the way it serves your customers.

5. Shiny objects. Vibing clutters the landscape with broken projects. We need a badge for apps that have a product person and a malevolent tyrannical committed QA function that demands the product serves customers, not the autist hobbyist creator (I'm talking about me of course)

Back to bed.