Silberengel @Silberengel - 4h
Has anyone built a Nostr client, where the DMs are a #SimpleX client? So that it's one client, with two protocols, and you just invite someone to your SimpleX chat, with a Nostr DM containing the SimpleX code? Or something, like that? Is that a dumb idea?
Skhron @Skhron - 4h
Sounds like super app, which I don't like
Well, events are signed with keys, but you could send some person an event using Simplex and their local relay could load it onto Nostr, and make it relayable. Like a private Tor.
SLCW @SLCW - 4h
I don't know that would work. Nostr is inherently based on user identities, and SimpleX is inherently based on not having user identities of any kind. I don't know how you'd handle associating an npub with the SimpleX message queue system. And if you did, it would automatically defeat SimpleX's core identity-free functionality.
No they're not. One-time connection keys are exchanged off-band. Not the message queues themselves. The message queue is dynamically created when one person's key is connected with another person's key. It sounds like you're talking about have one app that's actually two apps with no integration. And if that's the case what's the point?
Yo, I can send you an event over email or an API, or just write it down on a piece of paper. Events are just signed json snippets. They're data capsules.
Silberengel @Silberengel - 3h
Only need to download one app, open one app, get notifications from one app. 😂 Like, do you know how many apps I have? The app could just have DMs over Nostr, allow for a "move this convo to SimpleX handshake", if you have the plug-in, and then the plugin handles future convos and displays them in the same feed with Nostr convos, with a little icon on the npub profile, to show that chat as using SimpleX. Done.
SLCW @SLCW - 3h
I just don't see a meaningful integration. There's too much incongruity. The keys are ephemeral and exist only in the user's client, so there's no central mechanism to obtain and exchange keys. Nostr's key system with nsec and npub wouldn't have any relevance in the SimpleX key exchange or chat process. Because again, nostr keys are permanent user identities, and SimpleX exclusively uses ephemeral, local keys. It would be like trying to connect your Blu-ray player to a ham sandwich.
I suggest you go to the SimpleX github and read the SimpleX MQ whitepaper that details the messaging system. I know it sounds easy to you, but that's just not how it works. There's no reasonable way to integrate the two systems because they are fundamentally based on two mutually exclusive philosophies and design architectures. But it's all open source so you're certainly free to try!
You're the only one talking about integrating the protocols. I'm talking about display options in a client. If I have an Outlook app, that sends email, HTTP, and OATH, they don't have the mesh the three protocols together. Protocols can work in parallel. That is the standard way software is developed: multiprotocol. I am not a Nostr dev. I am a dev. I develop products for customers.
I don't know why you're getting defensive. I am also a dev and I've spent a lot of time studying SimpleX and communicating with the lead SxC dev. I'm not saying it's impossible because that would be ridiculous. But what you're talking about is not even close to as easy as you're making it out to be. And understanding the underlying protocol and methodology is essential to understanding what you can do and how you'd have to do it. Knock yourself out.
I mean, you could probably include some links to some of SimpleX's basic functionality in a nostr client without too much difficulty provided you're proficient in Haskell. But it wouldn't be an actual integration with Nostr. It would basically just be shortcuts to a seperately installed SimpleX client within the Nostr client. Personally, I wouldn't find value in that, but maybe some people would. I certainly encourage you to give it a shot. Frankenstein coding can lead to some amazing results!
One thing that makes it difficult is the fact that virtually all of SimpleX is original coding. It hardly borrows from any other projects, or uses anything standard. Add that to the fact that it's 100% Haskell and it's easy to see why it's a very difficult codebase to work with.
I took one look at the code and I immediately wanted to hang myself.
