Oddbean

It was discussed. SimpleX is extremely complicated. It's barely maintained. For example, for JS there is https://github.com/simplex-chat/simplexmq-js - but as per SimpleX founder words, it's abandoned and represents less than 5% of required code. For comparison, full NIP-44 js implementation fits in just ~100 lines. SimpleX is not a solution for nostr. Integrating simplex server functionality into relays is also extremely complicated. If you think you can do this - submit a proposal, and write some code, but it doesn't seem to be worth it.

Don't implement yourself, use the actual SimpleX client and server. "Each relay becomes a SimpleX server" means the relay and server are on the same host, different ports. The server may need some modification to allow for the discovery process I'm proposing. SimpleX seems to be well maintained according to the commit log, just the .js isn't. "We're sacrificing almost all the values we stand for because it's all we could do in 100 lines" isn't a great message.

> We're sacrificing almost all the values we stand for I'm not sure what are you talking about. SimpleX is not a silver bullet. It's trivially decrypt-able by quantum computers. It's also not popular, which means, if/when it becomes popular, only then we'll see how it holds up. Again - if you think simplex would work - go ahead and implement it. If you can convince the community your solution is better, everyone will switch to it. nostr is open for everyone. We're just a bunch of folks who've spent some time on the issue we thought was important. No one paid us for it.