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.
Comment on Beeper is now available, no waitlist!
shrugal@lemm.ee 7 months agoWhat is this “closed source experience” you are talking about? How would making the client open source hinder that in any way, when their stated goals 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.
derin@lemmy.beru.co 7 months ago
shrugal@lemm.ee 7 months ago
That’s not the point.
derin@lemmy.beru.co 7 months ago
I disagree. Beeper’s client is meaningless, its 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.
shrugal@lemm.ee 7 months ago
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.
jarfil@beehaw.org 7 months ago
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.
shrugal@lemm.ee 7 months ago
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.
jarfil@beehaw.org 7 months ago
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.
shrugal@lemm.ee 7 months ago
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.