Well, SimpleX message queue codes are typically exchanged out of band already.
This would just make it a standard.
I mean, I have DMed SimpleX codes. This would just be a UX change.
Discussion
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?
Your terminology is the correct one, couldn't remember the word. Connection keys.
Yes, literally could be just a "request connection key" function in the Nostr app.
Its not much of a change, I agree, but I'm also keen to reuse whatever works already.
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.
The SimpleX app knows its talking to BillyBob 🐮 in Arkansas. It can just list BillyBob 🐮. The user won't notice a difference. It will just be sending DMs to this BillyBob 🐮 entry. Not everything has to involve Nostr keys, to work. You can just label stuff.
I obviously wouldn't be trying to connect to everything, everywhere, only an npub I agreed to send my SimpleX link to. I know that it's really BillyBob 🐮, as he's the npub I did the handshake with.
I don't disagree, but I would also use the functionality I described.
I mean, its the same workflow some of us are using now, just with fewer manual steps.
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!
Hahaha your last line is gold :D
Its not adding a lot of additional value, I agree 100%, but that's kinda the point. Our Nostr devs reinvent the wheel a lot, and the SimpleX wheel already has iron rims and all-tension sinew spokes.
Adopt it into the tribe already, so we can go conquer Europe.
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.
Yeah, that's the whole point. It's just integrated superficially, in the display. You can make two things look like one thing, by changing the way they're displayed to the end user.
I like using Nostr DMs for quick questions or exchanging SimpleX links, but not for regular convos with my besties. I use SimpleX, for that. I like SimpleX.
Don't know why it's so often treated like a competitor.
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.
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.
And, like, I have an e-mail identical to my NIP-05 and a nostr:nprofile1qqsggm4l0xs23qfjwnkfwf6fqcs66s3lz637gaxhl4nwd2vtle8rnfqprdmhxue69uhhg6r9vehhyetnwshxummnw3erztnrdakj7qfqwaehxw309ahx7um5wghx26tww4hxg7nhv9h856t89eehqctrv5hsz8rhwden5te0w35x2cmfw3skgetv9ehx7um5wgcjucm0d5hsjmvd7t support e-mail. Why do I need an extra client, to look at it? Give me an e-mail plug-in, too. 😂
Like why not?
I've read the whitepaper, BTW.
I am not new to computers.