Oddbean new post about | logout
▲ ▼
Vitor Pamplona | 1 months ago (raw) | root | parent | reply | flag 
 Nothing completely solves the problem since any app will always have to ask the relay or a server for messages that match a given query. That query is the public identifier of the user and can be simply traced over time and mapped out with IP and other actions in the protocol.
▲ ▼
keychat | 1 months ago (raw) | root | parent | reply | flag 
 You are mixing up issues from different layers.
▲ ▼
Vitor Pamplona | 1 months ago (raw) | root | parent | reply | flag 
 Yep, because the reality includes all these layers. And they break each other constantly. You can't truly claim any privacy without considering all these layers combined.
▲ ▼
keychat | 1 months ago (raw) | root | parent | reply | flag 
 If we can solve an issue on a specific layer, such as the metadata privacy of recipients and senders at the application layer, that is definitely progress. 

IP issue is a network layer issue and needs to be resolved at the network layer. 

Moreover, the solution to the recipient's metadata privacy issue is the same as the solution for the sender's metadata privacy issue: both are addressed by continuously updating addresses.
▲ ▼
Vitor Pamplona | 1 months ago (raw) | root | parent | reply | flag +1 
 Sure, it's progress. But if you have progress in one, but doesn't solve the other layer, you can't claim being better. Sorry. I have seen too much of these BS with "private" comms in the last 20 years. people love to fool users into more complicated stacks and then leaving IP all there to be fully traced by servers.