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
I did read the article, and I fail to see how this is different than other implementations.
“In a call with Beeper’s Eric Migicovsky, that’s exactly what I wanted to find out, and it seems the answer comes down to trust. Beeper as it stands today, where everything is running on Mac Minis, is being done “in the open.” The backend is largely open-source, and the company has aimed to be straightforward and transparent with every update along the way. Migicovsky adds that, soon, Beeper will be doing a full in-public security review.”
So the difference is “you can trust us”. Sounds like BS to me, you’re still routing your messages through an endpoint that is someone else’s Mac mini.
You may have read the article, but you obviously didn't understand it. Read the third paragraph once more. Your quote refers to the previous implementation that Beeper used.
You're not routing any messages through anyone's mac mini.
Here is the source that Beeper's implementation builds on: https://github.com/JJTech0130/pypush
You can run this completely platform independent, without a Mac or IOS device. Try it yourself. DYOR and attempt to verify before you vehemently spout more misinformation.
Where is the beeper mini source code? Does Beeper mini send any data to beeper? Does it only talk to Apple servers from your phone?
Unless the code, for the app is open source, that we can build ourselves, and maybe even stick on f Droid, I'm not going to trust them not to be man in the middleing.
From what I've researched, Beeper's servers are only used when you use their push-notification service as it's not possible to use Apple's own push notifications(obviously). Everything else is done locally (encryption and what not). You don't even need an Apple ID, just a phone number.
The backend code is already open source, however their app isn't, so there is a bit of trust involved. Also, the app isn't free so that sucks. There are plans to open source it though.
You can also try iMessage using the link I sent previously, all trustless and independent from Beeper.
If Beeper decides not to open-source their app, someone capable could definitely step up as once again, the underlying tech is open source.
I advise you to DYOR if you'd like to verify any suspicions, i'm not the best at explaining things.