@doesnm@doesnm.p.psf.lt What do you think of when you say “decentralized”?

In nostr/simplex you did not bounded account to server because its just a relay. In matrix, xmpp and salty.im you store account data on broker and when broker is down you will no longer to communicate

@doesnm@doesnm.p.psf.lt Agree. salty.im should allow the user to post multiple brokers on their webfinger so the client can find a working path.

@xuu@txt.sour.is How would that work?

@prologic@twtxt.net currently? it wouldnt :D.

we would need to come up with a way of registering with multiple brokers that can i guess forward to a reader broker. something that will retry if needed. need to read into how simplex handles multi brokers

@xuu I guess the way SimpleX does its routing is quote clever and ingineious really. – However we never designed Salty.im that way. That wasn’t an attack vector we were really concerned with right? I’ve been using SimpleX with you for the last day or so now and reading up on it, and whilst there are some overlapping and similar ideas I feel that SimpleX has slightly different design goals right?

I mean Salty.im is more designed to be self-hosted, with good crypto but we never tried to set out to build a complex multi-broker, relay network-type protocol right? Do we need to? Probably not I think. Hmmm 🧐