—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.
📝 ea5a4232…
This has the same problem that was drawing criticism with early design of SimpleX network - while there is no persistent/observable identity on the protocol level, there is a fixed transport identity - relays can see which IP addresses communicate with which IP addresses. So it would require a similar solution to what we did with SimpleX network to mitigate it.
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. 😉
Honestly they should make it where if only one device can carry the chat database, then a desktop or server should be the primary device and then a phone or other devices can link to it. Their current solution of linking a mobile to a desktop doesn't really work (at least on iOS) because mobile devices have issues running background processes.
I've never tried Session, and I don't know many people who use SimpleX. I do like SimpleX's idea of no accounts though (Session has accounts).
As for address rotation, it's currently possible manually, so they are not completely static, and this feature is used a lot, and it will be automatic next year. The challenge with automatic rotation is reduced usability - data backups do not allow restoring connections, so it requires smarter approach to make sure that the solution is usable.
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.