Using something like this compromises e2e encryption for you and anyone that you talk to. It’s actively inviting a man-in-the-middle into all of your chats.
It’s a shitty thing to do to your friends.
Just use Signal if you care about the green bubble stuff.
Or just buy an iPhone if that kind of thing matters to you
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.
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.
Using something like this compromises e2e encryption for you and anyone that you talk to. It’s actively inviting a man-in-the-middle into all of your chats.
It’s a shitty thing to do to your friends.
Just use Signal if you care about the green bubble stuff.
Or just buy an iPhone if that kind of thing matters to you
Read the article. Your assumption is based on previous implementations of I-Message on Android.
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.