Yup, I see even the Nostr projects still use all these work apps and pay for them.
Time to build and market for #work.
They have:
- way more frustrations that we can already solve for (especially FOSS projects!)
- way more money to spend
Discussion
Mid term this eats SaaS.
Long term this eats ERPs.
Right now, asking people to manage keys is hard. I haven't figured out the pattern to get started with team members doing SSO or similar.
Again, asking businesses to manage keys for their members lowers the bar.
In a work context, the whole censor-ship resistance thing doesn't even matter.
If you get fired, you're censored and obviously should be.
Ok, so I get it conceptually but how will it actually work do you think?
IT team provisions the keys and gives out... ? Usernames and passwords? Bunker URLs? Java cards?
Ideally in a way that both
- allows use of all the apps in the ecosystem, and
- passes user acceptance test.
Your thoughts?
My noob-idea is having two servers, one controlled by the business, one controlled by a Nostr-service, that provide a working bunker URL together.
I think playing with a set up like that can maybe even get us to *only the user* ever having the full nsec. In a way that has some proper UX for everyone involved.
It's a tricky one.