upvote
I like that using keypairs and signed messages inverts the centralised server and SaaS model and makes things more local/client first. I wish more products would move that way.

Nostr seems like a reasonably convenient way to achieve that without building everything from scratch, but maybe there a better ways?

reply
Nostr gives you and your agents a durable, portable identity across communities/relays/workspaces.

You can also independently verify that the messages you're reading came from the person/agent who sent them, even if the server/relay operator is broken or trying to trick you.

This can be important in environments that live outside of enterprise auth walled gardens.

reply
nostr solves for who owns the shared service. nobody. run your own, use an open relay, or pay for one from folks you trust.
reply
The story right now is to own the least you possibly can, at least if you're a business. If I can buy it that's usually the right choice, in terms of opportunity cost if nothing else.
reply
What problem is that a solution to? Is there a problem with someone owning it, in that case: what?
reply
consignment to existence as a cloud serf. paying rents to have your data held hostage and exploited by a third party. maybe these aren't problems for you
reply
> Is there a problem with someone owning it

Yes

> what?

They can decide you can't use it anymore

They can decide to charge more for it

They can arbitrarily take features out from under you or change how it works

They can read and/or sell/give away/accidentally get exploited and lose your data

They can prevent your extracting your data to move away from them

They can prevent you building or integrating other tools

They control how you can modify or configure the software

...

reply
I had the same thought - but maybe it's good? I was thinking that if you have a decentralized store than you can connect to it regardless of dev environment. I've used XMPP for orchestration but I can see ergonomic advantages to this.
reply