this post was submitted on 09 Apr 2024
88 points (100.0% liked)
Technology
37754 readers
328 users here now
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
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.