Dessalines@lemmy.ml to Privacy@lemmy.ml · 2 years agoSignal says 1,900 users’ phone numbers exposed by Twilio breach – TechCrunchtechcrunch.comexternal-linkmessage-square57fedilinkarrow-up1114arrow-down17
arrow-up1107arrow-down1external-linkSignal says 1,900 users’ phone numbers exposed by Twilio breach – TechCrunchtechcrunch.comDessalines@lemmy.ml to Privacy@lemmy.ml · 2 years agomessage-square57fedilink
minus-squareree@lemmy.mllinkfedilinkarrow-up2·2 years agoWhat you wrote is simply wrong. Signal encrypt metadata to the best of their capacity. On the contrary matrix, xmpp, telegram, WhatsApp don’t (unless sth changed since last year) For example on my matrix server I could read the IP, username and time of each message. https://signal.org/blog/sealed-sender/
minus-squareDessalines@lemmy.mlOPlinkfedilinkarrow-up1arrow-down2·2 years agoThis is what they tell you. Since signal isn’t self-hostable or federated, you can’t verify that.
minus-squareree@lemmy.mllinkfedilinkarrow-up2·2 years agoAs far as i understand this is a client side implementation. So it’s verifiable.
What you wrote is simply wrong.
Signal encrypt metadata to the best of their capacity. On the contrary matrix, xmpp, telegram, WhatsApp don’t (unless sth changed since last year)
For example on my matrix server I could read the IP, username and time of each message.
https://signal.org/blog/sealed-sender/
This is what they tell you. Since signal isn’t self-hostable or federated, you can’t verify that.
As far as i understand this is a client side implementation. So it’s verifiable.