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.
They’re trying to run a business aimed at people who don’t care about open source, and want the same closed source experience they get from their other chat apps but with inter connectivity between third party services.
If you want the latter without any closed source code, you can just go and do that. They’ve released all the important parts.
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 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.
They’re trying to run a business aimed at people who don’t care about open source, and want the same closed source experience they get from their other chat apps but with inter connectivity between third party services.
If you want the latter without any closed source code, you can just go and do that. They’ve released all the important parts.
Edit: Here’s a guide to self hosting beeper.
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.