End-to-end encryption is about protecting data at rest on the vendor's servers. TLS only secures data in transit.
replyThe article's argument is a bit like saying TLS protects plain-text passwords in transit, so there is no need to store them in hashed form in the database.
Sure, the article makes good arguments about the trust that is still implicit in E2EE, but it goes too far in its dismissal of it.
having E2E encryption is a marketing feature, you need it if you want to be competitive in the market, so this is another incentive to add it
replyI never believed that the messages were truly E2E encrypted and I know for sure when WhatsApp retroactively censored a message I sent to a friend a while back, I found that super sus.
replyCan you be sure WhatsApp retroactively censored a message? Implying someone else but the direct recipient could read and delete/change it? (I believe group chats are different, forgot the details.) I don’t want to be dismissive but.. well i dont believe this is the best explanation given just these observations.
replyIt said the message was removed for violating some rule or something. The message was a link to a website meta does not approve of but it was removed like a day later.
replyWow, that is honestly a bit freaky - first I’ve heard of anything like that. I will assume it was a client side action, but still horribly invasive if that’s how it went. I’ll try to find more about this possibility.
reply