@mysk don't believe for a second WhatsApp ever had E2EE at all.

• Same for Signal, Telegram, Threema, Matrix, etc…

If you can't

• self-host it's servers,reproduceably build servers & clients
  • dev. your own servers and clients w/ feature parity.
• as well as use it without self-doxxing aka. needing a Phone Number,

it's insecure!

Because Phone Numbers are intrinsically insecure, as they can always be linked to a device [Number->SIM->ICCID->IMEI) / client (SIP uses UDP = no Tor!) and thus trivially connected by circumstances to a person!

So go with PGP/MIME ( @delta & @thunderbird and/or XMPP+OMEMO ( @gajim and/or @monocles ) over @torproject!

• VPNs are snitches
  • If nachash wouldn't touch it, why should you?

#WhatsApp #E2EE #Signal #Threema #Telegram #Matrix #SelfHosting #ReproduceableBuilds #Server #Client #OpenSource #OpenStandards #SelfDoxxing #KYC #ID #PhoneNumber #SIM #IMEI #Privacy #UDP #Tor #OpSec #InfoSec #ComSec #ITsec #OMEMO #PGP

@lastdinosaur @nixCraft sorry, did a typo.

Besides that:

#ReproduceableBuilds are a hallmark of good codIng, bespechally with #FLOSS, as to evidence the published code is identical to what the binary releases are build from.

- Trust through transparency…

@ravirockks Needless to say that only #transparency with #ReproduceableBuilds can enshure the #SourceCode is related to the #binary released.

And being able to audit oneself or choose any auditor of choice to do so is also critical to the whole #ITsec aspect of it.

You don't want people to be able to "pull rank" but instead you want critical code to be looked at with as many eyes as possible.