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.
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.
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.
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.
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.
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.