Android
The new home of /r/Android on Lemmy and the Fediverse!
Android news, reviews, tips, and discussions about rooting, tutorials, and apps.
πUniversal Link: [email protected]
π‘Content Philosophy:
Content which benefits the community (news, rumours, and discussions) is generally allowed and is valued over content which benefits only the individual (technical questions, help buying/selling, rants, self-promotion, etc.) which will be removed if it's in violation of the rules.
Support, technical, or app related questions belong in: [email protected]
For fresh communities, lemmy apps, and instance updates: [email protected]
π¬Matrix Chat
π°Our communities below
Rules
-
Stay on topic: All posts should be related to the Android OS or ecosystem.
-
No support questions, recommendation requests, rants, or bug reports: Posts must benefit the community rather than the individual. Please post to [email protected].
-
Describe images/videos, no memes: Please include a text description when sharing images or videos. Post memes to [email protected].
-
No self-promotion spam: Active community members can post their apps if they answer any questions in the comments. Please do not post links to your own website, YouTube, blog content, or communities.
-
No reposts or rehosted content: Share only the original source of an article, unless it's not available in English or requires logging in (like Twitter). Avoid reposting the same topic from other sources.
-
No editorializing titles: You can add the author or website's name if helpful, but keep article titles unchanged.
-
No piracy or unverified APKs: Do not share links or direct people to pirated content or unverified APKs, which may contain malicious code.
-
No unauthorized polls, bots, or giveaways: Do not create polls, use bots, or organize giveaways without first contacting mods for approval.
-
No offensive or low-effort content: Don't post offensive or unhelpful content. Keep it civil and friendly!
-
No affiliate links: Posting affiliate links is not allowed.
Quick Links
Our Communities
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
- [email protected]
Lemmy App List
Chat and More
view the rest of the comments
No, it's still E2EE. Meta can't read it as far as anyone knows. Meta will know that the other person has you in their contacts (they already know this) and that they are messaging you, that's it.
Meta writes the software that runs on the other end, and it's closed source. Therefore for all we know, the message is end-to-end encrypted, and the moment it is decrypted on the other end Meta can send it back to their servers or use it for advertising. Unless the client at the end is open source and audited, E2E doesn't mean much imo
Well, I think you're the only one who thinks that E2EE doesn't mean much.
No I think you've missed their point. E2EE is end-to-end encryption, as in the message can't be intercepted in the middle but it's unencrypted at the end so you can read it. Because the WhatsApp app is closed-source you don't know that it doesn't immediately read the message and send the content to Facebook. It probably doesn't, but it could! E2EE itself means that some third party can't read your message in transit, though to be fair closed-source again means we just have to trust Facebook when they say WhatsApp uses E2EE.
So, this isn't quite as valid a fear as you seem to think. There will be a lot of very smart people analyzing the shit out of what the app appears to be sending to Facebook servers. True it's closed source but that doesn't mean it's impossible to catch them doing fucked up shit. How do you think we currently know about things they do like this? Do you think Facebook told security experts just to be nice? Or do you think the experts figured this shit out on their own?
Sure, good point. But you do agree that it's harder to trust something that explicitly hides from you what it is doing?
Oh I agree they'll do every bad thing they can get away with. I just think they wouldn't get away with decrypting the message and sending it straight to FB
I did get their point and what I'm saying is that back doors like this are discussed all the time and as of now, there's no proof that they exist. To the contrary, we have information confirming that content of E2E encrypted messages is not available to government agencies. Claiming otherwise without proof is simply spreading disinformation.
If somebody hands me a black box, tells me what's inside, how is the burden of proof on me? I have to trust them blindly until somebody proves that there is something bad in the black box? No, I ask for a transparent box in the first place.
WhatsApp being a black box means we don't know how it's doing things but we can still know a lot about what it's doing and what it's not doing. For example we know it has permissions to access all the contacts and we know when it's accessing device location data. We also know from FBI documents that they can't access content of E2EE messages or how much data it's transmitting and when. It would be hard for Meta to transmit all received messages to their servers without anyone noticing. It's good you prefer OSS but it doesn't mean you can make wild claims about some security flaws like that.
That's not it. It's E2EE but Meta gathers all the metadata from Whatsapp including who you contact, when, where, how large the messages are, what times you're online and for how long, phone numbers, names etc. That's plenty of info to create a profile on users and their connections with each other, as is Facebook's MO.
That's exactly what I said. They will have meta data but will not be able to read chats. What are you disagreeing with?