Elon Musk, who is the head of Twitter and many different companies, made a sound with his statement that “WhatsApp cannot be trusted”. Yesterday, Twitter engineer Foad Dabiri made the following post on his personal account. Dabiri wrote in this post, “WhatsApp has been using the microphone in the background, while I was asleep and since I woke up at 6 AM (and that’s just a part of the timeline!) What’s going on?” and shared the screenshot.
WhatsApp blames Google Pixel!
Seeing this, Elon Musk took this post by Dabiri and moved it to his own account with 139 million followers with the message “WhatsApp cannot be trusted”. So what is really going on here? Is WhatsApp constantly listening to the environment? After being highlighted by Elon Musk, the company immediately clarified the issue which attracted a lot of reaction.
WhatsApp’s Twitter account on the subject, “Over the last 24 hours we’ve been in touch with a Twitter engineer who posted an issue with his Pixel phone and WhatsApp. We believe this is a bug on Android that mis-attributes information in their Privacy Dashboard and have asked Google to investigate and remediate. Users have full control over their mic settings.”
“Once granted permission, WhatsApp only accesses the mic when a user is making a call or recording a voice note or video – and even then, these communications are protected by end-to-end encryption. So, WhatsApp cannot hear them.” was said by WhatsApp. It is reported that this problem or error is not actually the first time it has come to the agenda, and Google has been working for a while on a solution.
Also, according to the statement made by Elon Musk, the long-awaited end-to-end encryption infrastructure for Direct Messages within Twitter is being activated with the “1.0” version as of today. Musk, who said, “I won’t be able to see your DMs even if you put a gun to my head,” is right in this saying. Because thanks to end-to-end encryption, even Twitter engineers will be prevented from seeing Direct Messages on the platform.
{{user}} {{datetime}}
{{text}}