Security concern: Does relay store the IP or details of the sender?

[peppa]

@skamu

I was thinking if maybe it could be something like a p2p approach, where there is no server o relay, but the messages are sent, synced and chronologically ordered only when the devices have both an internet connection available. And users can have multiple devices, so it can give a bit more opportunities that the “send/receive - sync - sorting” process happens… But yes, it could take time before at least one device of sender and one device of the receiver are both online at the same time. So, maybe this goes against the concept of a messaging app…

Well there are messaging apps like Briar, Cwtch, and Ricochet Refresh which work like this (some optionally support servers as well). As you already said, it could take time before at least one device of sender and one device of the receiver are both online at the same time, and these messaging apps maybe don’t have the same feature set or cross platform like DC.

@skamu

Or I was also wonder, if I have multiple relays in my DC account, it can randomise what relays is used for each individual sent/received message. So, that if I have multiple relays (based in multiple countries), it could become at least more difficult and time consuming if a government wants to “solve the puzzle” and puts together the whole conversation. I believe this is already in DC roadmap…??

I don’t know if this is in DC roadmap or not but its a very cool idea and @ethanc8 suggested something similar here before DC supported multiple relays:

@ethanc8

we might be able to randomly select from our pool of secondary accounts which account to send the message with, so that it’s harder for automated traffic analysis to identify social graphs. Additionally, creating more secondary accounts at random times and deleting old secondary accounts could make it even harder for automated traffic analysis.