Login to reply
Replies (21)
Because it essentially doesn't work for me. It's way too laggy and slow.
Notifications or just general app usage?
I'd agree on this. I've not really had issues with much and @water783 gets those fixed pretty quick when they do show up.
honestly have not yet had a use case
We moved our Bitcoin Meetup's group chat from Matrix bridged to Telegram/Discord to using it as the primary a few months ago and it's worked good so far.
Because @SimpleX Chat is the way
🤣🤣🤣
In all seriousness why would you rather use
DYOR
Fair enough. The only argument I get for SimpleX over nostr based is the lack of metadata associated to your conversations on SimpleX. This is a real issue for some people but would not affect me normally. If there was a situation I needed that metadata split I'd just spin up a nostr identity just for that communication use case. Personally I think the WoT possibilities of nostr far outranks the anonymity of SimpleX for 99% of my interactions.
yea good UI app 😎
Nostr isn’t designed to be private
We love Nostr as a publishing platform that offers unparalleled censorship resistance. But NIP44 does NOT provide most of the important qualities of e2e encryption:
- break-in recovery.
- repudiation (deniability).
- visibility of connection graph to observers.
- fixed message sizes (although it can be provided by the specific app)
- resistance to Shore algorithm (PQ encryption).
It's unclear whether it provides forward secrecy, but the spec implies that it does not - I might be wrong here.
We wrote this post about the qualities of e2e encryption and why they are important: 
SimpleX Chat v5.6 (beta): adding quantum resistance to Signal double ratchet algorithm
NIP-44 is just the encryption. The DM protocol is NIP-17 with NIP-59 and NIP-44. No one uses NIP-44 by itself for messages.
1. NIP-44 has padding for fixed message sizes. 2. NIP-17 DMs is giftwrapped by ephemeral keys in public, so repudiation/deniability is provided as well. Gift wraps can even use random alias keys as receivers.
3. The connection graph is not visible unless the NIP requires it to.
4. Break-in protections exist on the wrap. Breaking individual messages does not reveal the main nsec of the Nostr user. The only way the break-in can work is if the attacker gets the long term key or seed, which is also a problem for other E2E apps.
Also
Let's break down @0xchat a bit
The app has default gift wrapped nip44 DM's with encrypted content and minimizes meta data leak.
The app also offers "Secret Chat" DM which is the gift wrapped DM plus a nip101 key exchange.
°To use the Secret Chat you need to tap on the user profile, then tap secret chat button.
°This opens an option screen to choose a trusted relay, the time interval to exchange keys, and length of request time out.
°Also under 'more' on the user profile you can request auto delete of messages. The other user has to agree.
°The secret chat also has a screen shot notification.
Amber can be used to sign in and protect your nsec. Use a vpn, tor/orbot.
"Home" will show all messages.
"Contacts" shows your saved nostr contacts, groups and channels.
"Discovery" shows your follows nostr feed and is called "moments" and also has "channels" tab.
"Me" is your profile where you can manage settings and ecash wallet plus just see your own "moments"
The app has a lot going on.
Under "Home" you can create a new "Group".
°Groups can be Open, Closed or Private.
° Open groups anyone can join and see
° Closedd groups is invite only
° Private groups are gift wrapped dm to each member
There is also a cashu ecash wallet in app.
View quoted note →
No need to compromise on discoverability or privacy. Nostr can be used as a discorrability layer for SimpleX (or any other messaging app) but this has been turned down twice. There were discussions about interesting SimpleX with Nostr last year but it never went anywhere, someone made a proposal for a contact info field to replace the DM button with but that was declined.
Excellent post!
This.
This is for verifying identity to contacts, not discovery. Nothing needs to be done on SimpleX's end for discovery but Nostr devs declined.
What do you mean they declined? Was there a nip proposed for it? Clients could still do it if it was a good proposal. There is nip 48 proxy tags and nip 39 external identities that could hold simpleX information maybe
There was a NIP proposal for adding general contact info links which includes SimpleX. NIP-48 is for bridging content from other platforms, NIP-39 is for verifying identities of other platforms, which I suppose could be done for SimpleX addresses if there was a way to sign messages with the public keys. I think NIP-24 kind 0's are the most suitable for linking to SimpleX addresses as described here: 
GitHub
[FEATURE] SimpleX Chat links in profile · Issue #8 · retrnull/garnet
Is your feature request related to a problem? Please describe. Nostr DMs are unsafe. Developers keep churning out new flawed DM systems and nobody ...