You can use any Matrix client with Beeper, you don’t have to use theirs.
Regardless, there’s nothing stopping you from recreating the same stack using the available tools.
What makes their service unique are the bridges. Download their sources, compile them, and then pair them with any server client combo you want.
If you insist on using their stack, you can still use an OSS client. They chose not to make their client open source as it is, by design, for their service only.
What is this “closed source experience” you are talking about? How would making the client open source hinder that in any way, especially when their stated goal is to earn money with premium features instead of the app itself?!
Imo being open source is a VERY big deal for an e2e encrypted chat client! I don’t really care whether most of their stack is open if the app I’m actually using to type and encrypt my messages is not. This makes the whole thing look like a trick, pretending to be open when key parts are not.
The thing is, we are talking about the Beeper service here. Yes Matrix is good, yes Beeper bridges are good, but a closed source Beeper app is bad. That’s what the criticism is about, and it doesn’t help if you deflect that by arguing about all the other things they are doing or that no one is forced to install it.
You’re definitely right that people are a bit too doom-and-gloom about it, Beeper did do a lot of good over the last few years!
But I also find it a bit odd that they talk so much about the importance of open source in messaging, and then release a closed source client without at least adressing the topic. Add the fact that they’ve been aquired by another company on the same day, and it starts to smell like another instance of openwashing.
I am worried about that acquisition, to be honest.
I’ve been supporting them via Github sponsors for about a year, now - as I only use their open source software; I’ve no intention of touching the service or closed source client.
As a result, I’d be lying if I didn’t say I was anxious about their new owners basically telling them “hey, why are you releasing all your bridges for free, anyway?”
Really hope that doesn’t happen, as their bridges have been my primary communication channels for a long time, now. I love not having to keep WhatsApp or Discord installed on my phone.
I can answer that: it’s the “I don’t care about security as long as I can send memes and inappropriate messages to most people” experience.
From the looks of it, it’s as secure as having WhatsApp/Signal/Telegram/ProtonMail doing “E2EE” through each app’s servers, and never knowing whether the client did the encryption right, or if it sent the keys to the server for messages to get intercepted… well, except you do know that the bridges are decrypting all messages anyway.
Closed source helps with the second part, the connecting with a majority of people using the same closed source platform (then different people use different platforms, which is where we are now… but the DMA might solve that).
On-device bridges could be nice if they included that in the OpenSource part.
the connecting with a majority of people using the same closed source platform
The platform is open, including the part that connects to other closed source platforms. It’s just Matrix and open source bridges after all. And making the client app closed souce doesn’t help with any of that.
I’m sorry if I’m a bit pedantic about this, but it seems like you’re describing an upside to closed source software that’s just not there.
I was trying to explain that people on closed source platforms, right now, get:
Good network effect
Simple configuration
Enough security theatre to keep them happy
Different extra features
That’s the experience I understand Beeper is trying to compete with… and make money in the process.
Closing the client, could help them differentiate above the competition by better integrating into their own infrastructure, still keeping a simple configuration, and charging for it, while people who buy into the security theatre, woldn’t notice a difference in that respect. Expanding to selling some user metadata, or sniffing the bridges, would be an extra.
You can use any Matrix client with Beeper, you don’t have to use theirs.
Regardless, there’s nothing stopping you from recreating the same stack using the available tools.
What makes their service unique are the bridges. Download their sources, compile them, and then pair them with any server client combo you want.
If you insist on using their stack, you can still use an OSS client. They chose not to make their client open source as it is, by design, for their service only.
It absolutely isn’t “Anti Commercial Ai thingy”.
What is this “closed source experience” you are talking about? How would making the client open source hinder that in any way, especially when their stated goal is to earn money with premium features instead of the app itself?!
Imo being open source is a VERY big deal for an e2e encrypted chat client! I don’t really care whether most of their stack is open if the app I’m actually using to type and encrypt my messages is not. This makes the whole thing look like a trick, pretending to be open when key parts are not.
Just use any open source client. You can literally do that.
And if you don’t trust the company - for any reason - use their code to deploy your own backend.
That’s not the point. An app doesn’t become good because you can just not use it.
I disagree. Beeper’s client is meaningless, it’s the service being offered that has value.
If you don’t mind trusting a third party service with your Matrix instance + bridge hosting, use Beeper.
If you’re into OSS and owning your own tech stack, self host the whole thing.
At no point do you have to use their client for any reason.
The thing is, we are talking about the Beeper service here. Yes Matrix is good, yes Beeper bridges are good, but a closed source Beeper app is bad. That’s what the criticism is about, and it doesn’t help if you deflect that by arguing about all the other things they are doing or that no one is forced to install it.
Fair point, if you’re just against the fact that they wrote a closed source client.
It’s frustrating that closed source software exists, but in this context I’m (personally) okay with it as it funds the development of free software.
You’re definitely right that people are a bit too doom-and-gloom about it, Beeper did do a lot of good over the last few years!
But I also find it a bit odd that they talk so much about the importance of open source in messaging, and then release a closed source client without at least adressing the topic. Add the fact that they’ve been aquired by another company on the same day, and it starts to smell like another instance of openwashing.
Idk, we’ll have to see how it plays out I guess.
I am worried about that acquisition, to be honest.
I’ve been supporting them via Github sponsors for about a year, now - as I only use their open source software; I’ve no intention of touching the service or closed source client.
As a result, I’d be lying if I didn’t say I was anxious about their new owners basically telling them “hey, why are you releasing all your bridges for free, anyway?”
Really hope that doesn’t happen, as their bridges have been my primary communication channels for a long time, now. I love not having to keep WhatsApp or Discord installed on my phone.
I can answer that: it’s the “I don’t care about security as long as I can send memes and inappropriate messages to most people” experience.
From the looks of it, it’s as secure as having WhatsApp/Signal/Telegram/ProtonMail doing “E2EE” through each app’s servers, and never knowing whether the client did the encryption right, or if it sent the keys to the server for messages to get intercepted… well, except you do know that the bridges are decrypting all messages anyway.
Closed source doesn’t help with that though, you don’t have to care about privacy in open source.
They are working on on-device bridges that preserve e2ee, but making the client closed source kind of defeats the purpose here.
Closed source helps with the second part, the connecting with a majority of people using the same closed source platform (then different people use different platforms, which is where we are now… but the DMA might solve that).
On-device bridges could be nice if they included that in the OpenSource part.
The platform is open, including the part that connects to other closed source platforms. It’s just Matrix and open source bridges after all. And making the client app closed souce doesn’t help with any of that.
I’m sorry if I’m a bit pedantic about this, but it seems like you’re describing an upside to closed source software that’s just not there.
Too pedantic 😉
I was trying to explain that people on closed source platforms, right now, get:
That’s the experience I understand Beeper is trying to compete with… and make money in the process.
Closing the client, could help them differentiate above the competition by better integrating into their own infrastructure, still keeping a simple configuration, and charging for it, while people who buy into the security theatre, woldn’t notice a difference in that respect. Expanding to selling some user metadata, or sniffing the bridges, would be an extra.