Oddbean new post about login | logout Why are you not using 0xchat yet? https://0xchat.com
Because it essentially doesn't work for me. It's way too laggy and slow.
I recommend you try one more time 🤣🤣 https://github.com/0xchat-app/0xchat-app-main/releases/tag/v1.3.0-beta.2
I'd agree on this. I've not really had issues with much and nostr:nprofile1qqs84k6jpsav0jmdeqjn2zxlpnsajaw6f8l0m2d4e9t8gjsyn53s4nspzemhxue69uhhyetvv9ujuvrcvd5xzapwvdhk6qgdwaehxw309aukzcn49ekk2qghwaehxw309aex2mrp0yh8x6tpd4ehgu3wvdhk6pw0r8j gets those fixed pretty quick when they do show up.
honestly have not yet had a use case
Because nostr:nprofile1qqsvnx99ww0sfall7gpv2jtz4ftc9v6wevgdd7g4hh7awkpfvwlezugpg3mhxw309um8semndee8wdnrwvmk2atdw9arwct6xa6hj6mv0fhkzuncd34x6arxddckkctk094k7urkv33x2atpd36hzctc09jzummwd9hkutc2rde3l is the way
https://media.tenor.com/8mddYUccA9cAAAAM/wrong-drumpf.gif 🤣🤣🤣 In all seriousness why would you rather use nostr:nprofile1qqsvnx99ww0sfall7gpv2jtz4ftc9v6wevgdd7g4hh7awkpfvwlezugpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhs38wxc9 over nostr:nprofile1qqs9ajjs5p904ml92evlkayppdpx2n3zdrq6ejnw2wqphxrzmd62swspzemhxue69uhkummnw3ezumt0w46x7m3wv3jhvqgkwaehxw309aex2mrp0yhxummnw3ezucnpdejqzrthwden5te0dehhxtnvdakqhm2uug?
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.
Nostr isn’t designed to be private
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.
https://github.com/simplex-chat/simplex-chat/issues/2859
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: https://github.com/retrnull/garnet/issues/8
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: https://simplex.chat/blog/20240314-simplex-chat-v5-6-quantum-resistance-signal-double-ratchet-algorithm.html
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.
Excellent post!
