- cross-posted to:
- privacy@programming.dev
- cross-posted to:
- privacy@programming.dev
You must log in or register to comment.
Someone dug out a 2 year old article.
I saw this in hackernews bro😣
Another hit piece on signal? Damn they must be doing something right.
GrapheneOS is being attacked too, by the French government and law enforcement in particular.
Funny coincidence: .ml is a French instance.
EDIT: just to be clear, I DO think it’s a coincidence, especially since other posts in this community are pro-graphene and pro-signal.
deleted by creator
Have fun talking to yourself.
deleted by creator
Does Delta Chat / Arcane Chat suffer from the same vulnerability?
From https://delta.chat/en/help#sealedsender
Does Delta Chat support “Sealed Sender”?
No, not yet.
The Signal messenger introduced “Sealed Sender” in 2018 to keep their server infrastructure ignorant of who is sending a message to a set of recipients. It is particularly important because the Signal server knows the mobile number of each account, which is usually associated with a passport identity.
Even if chatmail relays do not ask for any private data (including no phone numbers), it might still be worthwhile to protect relational metadata between addresses. We don’t foresee bigger problems in using random throw-away addresses for sealed sending but an implementation has not been agreed as a priority yet.
Thanks, that is very clear
