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.

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

Good

It was a pretty bad idea, not only a privacy risk for users but for anyone those users interact with. You no longer get the guarantee that your iMessages are end to end encrypted since anyone using the service puts a man in the middle for everyone they communicate with.

But why even bother? If you’re privacy conscious and still insist on a chromium based browser just use Brave.

Use things that respect your privacy by default. Otherwise you have to be in the habit of actively opting out whenever new updates or features are added and anybody who would be that diligent about it is probably already using Firefox or Brave anyway.

Edge is entirely as privacy violating as chrome