Replies (19)
If white noise avoids it, why not use it?
Here's what chatgpt summarised for me after a bit of back and forth.
If I understood correctly, the service is still able to see what (other) groups you're in (but cannot read contents)
Which doesn't make much sense since all MLS communication on WhiteNoise is wrapped and encrypted again. But maybe I am wrong.
I have ZERO understanding of the topic, it's just my conclusion from footnote (3) 😅
from ip address? idk
MLS is garbage made by retarded academics that have lost their touch with the real world long ago
large groups should be assumed to be public anyway, MLS is much worse than the signal protocol
exactly
—the lack of participation privacy
If you understand that in Keychat ID are decoupled from sending/receiving addresses and addresses are continuously rotated, you’ll realize it’s almost impossible for a message relay to identify the participants in a group.
Because sending addresses are decoupled from IDs and constantly change, a message relay cannot reliably infer who is in the group.
If a Nostr relay requires AUTH—as based on a paid subscription—it would be one way a pubkey/npub could be associated with a group ID (the only metadata available, afaik). The other would be based on an IP, but that is similar to Signal et al (and mitigated with VPNs and etc). E-cash 'blind signatures' seem to be the best solution for relay 'subscriptions' without knowledge of a pubkey. It was designed for this scenario, even if from 1981.
White Noise and ANY application using nostr for identities can completely ignore this article. It simply doesn't apply, since nostr IS the "Authentication Service" mentioned here.
Unrelated, but your client hasn’t published the event to my inbox relays.
We don't have an "Authentication service" that issues and verifies a user's identity. We use nostr pubkeys for identity.
I also think that we avoid the "participation privacy" issue that he mentions in the article but want to clarify what he means with him before claiming anything. 😉
Keychat’s receiving address is updated using the Signal double ratchet, and so far rotating the receiving address has had almost no impact on the stability of message reception.
You've established yourself as the secure chat. No refute there.
But you're not usable.
-Notifications are shit.
-No cross device support.
-A sea of technical settings.
-Backups are a disaster.
-Delivery is iffy.
Put the SIMPLE back in SimpleX, and make it as easy to use as Session.
Pre-set all settings, clean the UX, make notifs work, add multi-device support, make backups easy and use a seed phrase to unlock them. Then you will be my go to. Till then, it's Session for me.
MLS uses ratcheting trees, it's different from Double Ratchet.
