As much as they beg and plead, I have a very suspicious automatic gut reaction to US based companies screaming from the heavens about how they're the one true privacy bastion... They have a lot of frothy-mouthed fans who poke their head out immediately when I bring up any of my concerns about things[0] - or when I state that: one company should not be the only one fighting for private messaging.
The smart play is to have companies in many countries and have them federate traffic across each others infra (like tor) and to have third-party clients with their own ability to implement the E2EE bits...
- or, even better: use something like Matrix amongst friends, you only need a slightly technical friend to set it up for you and now it's really hard for someone to violate your trust, and you're not even a big target for mass surveillance: win-win.
As it stands, Signal can still be compelled to act against their users, especially those not under US jurisdiction, and they're forbidden from talking about it. They're directly under the CLOUD act (if they're not a honeypot designed explicitly to drown out other private messengers, which sounds conspiratorial but its the only thing that makes sense based on how effective their marketing is compared to others- the concerns raised against Signal would kill other messengers).
Hasn't Matrix had a series of cryptographic blunders?
Ah yes, I do remember: https://soatok.blog/2024/08/14/security-issues-in-matrixs-ol...
As for Signal being open source (or your claim in the link that it is not open source as in they don't provide the source for builds; and you only need to look at the client source for the security claims), as of a previous post about Signal on HN I have started verifying the builds on iOS which I can confirm are fully source reproducible:
https://github.com/commandersaki/signal-ios-build-verificati...
Signal already provide instructions on Android reproducible builds and it wouldn't really take much to extend that to fully source reproducible.
It turns out that good privacy tech doesn't rely on jurisdictions.
It's a stupid take that the country matters. If the tech is sound and trustless, it won't matter what country the company is based in.
Similarly "digital sovereignty" is stupid. E2EE is what matters. And SimpleX shows that you can essentially add highly effective client-side metadata encryption.
For content privacy, you're much better off with an E2EE file service hosted in North Korea than non-E2EE file service in Switzerland.
"Moxie Marlinspike" I am not going to trust some jabroni, straight out of central casting, who doesn't even fly by his family name. Seems like yet another usgov+hollywood fabrication. Good on you.
JWZ site, so if you don't want the HN testicle egg, copy paste, don't click:
I have followed digital privacy and nation-level-actor interception stories since the European Parliament's ECHELON report over a quarter-century ago, and to me it is a given that no strong state like the USA would permit a truly secure app being used at a societal scale. I use Signal myself, but am under no illusions.
The developers might be bona-fide idealists and the E2EE encryption might be reliable (if only when compiling the app from source oneself), but it feels obvious that the US authorities would gain access to things like contact metadata or forcing a compromised build on request. The app is leaky in this regard, and Signal rents cloud infrastructure which enables covert shenanigans with the server, like compromising the infamously vulnerable Intel SGX which is the only thing keeping people's contact lists (uploaded by default to the server) private.