Android
DROID DOES
Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Rules
1. All posts must be relevant to Android devices/operating system.
2. Posts cannot be illegal or NSFW material.
3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.
4. Non-whitelisted bots will be banned.
5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.
6. Memes are not allowed to be posts, but are allowed in the comments.
7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.
8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.
Community Resources:
We are Android girls*,
In our Lemmy.world.
The back is plastic,
It's fantastic.
*Well, not just girls: people of all gender identities are welcomed here.
Our Partner Communities:
view the rest of the comments
is it using the iMessage servers again, or is it still talking to iMessage directly?
They claim this one talks to Apple's servers directly without proxy and therefore does E2EE.
See https://blog.beeper.com/p/how-beeper-mini-works
They do claim to use a custom-built proxy for push notifications (Apple's push notifications obviously won't work on Android) but that's a helluvalot less critical than a message content proxy.
Given their previous behaviour, I'll only believe that when an independent security researcher confirms that the app's code actually implements the iMessage protocol with E2EE as they claim.
There was a very recent project that reversed enginered iMessage which I assume they are using as reference.
If you're talking about that one by the high school student, they actually bought that from him.
In terms of helluvalot less critical - is it really though? Remember that the app on your phone is also witten by them, closed source and does whatever they want with your clear-text messages. If the trustworthyness of a messaging vendor is part of the critical-ness question, e2e encryption does not add anything: Either you trust them and could also do so when they process your message on their server, or your don't and they could indeed spy on you on the proprietary client app.
End 2 end encryption is only a real benefit when the ends actually belong to the user, i.e. theres transparency about the ends being clean, which can only be shown for open source ends. If the ends are potentially compromised, there's so security / privacy guarantee.
It's still taking to iMessage directly, but now you need an Apple account, your iMessage account won't be associated with a phone number.
They also have a different app called Beeper Cloud that uses a relay Mac somewhere in a data center.
Not a relay Mac, see the post you linked.