3 ms·
There's never a single right solution, but if traffic analysis was the issue, endpoints could introduce latency, use Tor, sync/mix traffic with other endpoints
by nxzero 11y ago
There's never a single right solution, but if traffic analysis was the issue, endpoints could introduce latency, use Tor, sync/mix traffic with other endpoints via P2P, inject fake traffic, etc. - though if the core system leaks metadata, this would be pointless.
- 21 11y agoMessaging apps are often used outside, with limited bandwidth, and are highly interactive. I would be annoyed to wait more than 0.5 sec until my message is delivered. Maybe an "ultra-secure" mode could be created, and if you enable that for a chat, traffic could be routed through tor. And you would have a separate list of "ultra-secure" contacts, which are not based on phone-numbers.
- maxerickson 11y agoSpecial routing for the ultrasecure messages highlights that they were requested to be ultrasecure and makes correlation easier (by reducing the candidate pool).
- 21 11y agoRight, but it would be like the ISP knowing that you use Tor. Useful, but not that much if you do it constantly. This ultra-secure mode for example could send a 1 KB packet every 15 minutes, weather you are talking with someone or not. Something would also need to be done to incoming packets, so that they won't stand out. I'm sure there is a suitable protocol out there. This would increase latency and reduce capacity, but this is why it's called ultrasecure, some inconveniences are expected.