The amount of problems remains stable, as a universal constant . Problems are neither solved nor created, only transformed. By switching from Telegram to Matrix, new problems arose. By switching from Matrix to Session, by switching to Signal, where we are now, fewer problems arose
Records of precisely who you talk to are being kept serverside because of that decision. Maybe that's totally fine for you! Most people have pretty unserious secure messaging threat models (I don't mean that as a value judgement).
The same is likely true of Signal, no? Traffic analysis on AWS' edge would tell you precisely who is talking to who, and user identities are tied to legal identities via phone numbers. Maybe Signal doesn't store this data serverside, but there are entities with both the capability and motivation to obtain it. I bet there are Signal XKEYSCORE selectors.
The amount of problems remains stable, as a universal constant . Problems are neither solved nor created, only transformed. By switching from Telegram to Matrix, new problems arose. By switching from Matrix to Session, by switching to Signal, where we are now, fewer problems arose
Records of precisely who you talk to are being kept serverside because of that decision. Maybe that's totally fine for you! Most people have pretty unserious secure messaging threat models (I don't mean that as a value judgement).
The same is likely true of Signal, no? Traffic analysis on AWS' edge would tell you precisely who is talking to who, and user identities are tied to legal identities via phone numbers. Maybe Signal doesn't store this data serverside, but there are entities with both the capability and motivation to obtain it. I bet there are Signal XKEYSCORE selectors.
No, it's not. Traffic analysis is potent, but it is not a literal SQL database of who has talked to who when.
12 replies →