I was on the beta testing team and have been using Beeper for a little over two years now.
The convenience of having an application to house all of your chat networks is amazing.
I was on the beta testing team and have been using Beeper for a little over two years now.
The convenience of having an application to house all of your chat networks is amazing.
My worry would be who is funding it and how they plan to keep operating. Venture Capital startups will always betray their users.
And the fact it’s clients are propietary is not making it better.
their clients are proprietary but it’s built on matrix (federated chat kinda like xmpp) and their bridges (things that connect matrix to other protocols) are open source
they say you can use any matrix client, and that you can host your own home server with their bridges
I have my own matrix server that I primarily use like beeper and bridge all my chats together. Even using some of their bridges, it’s been pretty reliable for years.
I know that a few people are hating on the closed source client, but that feels unfair to me. They provide lots of open code in the form of bridges which is really the meat of the offering. Their client just makes using the bridges easier for the lay person. The bridges are super easy to use without it, invite the bridge bot to a chat room, type login and do what it says, then type login-matrix and your pretty much done.
The I suspect that the same people who are displeased about the closed client also like using tailscale which is generally pretty popular but has closed source clients on Windows and Mac as well as the server (though all support the open source headscale server)
yeah… pragmatism beats purity every time: they’re doing some great work, but to do that great work they have to fund it somehow… i think that open sourcing all of the functional components (the bridges) and keeping the shiny UI closed is a pretty good way of doing that!
i guess i get not wanting to used closed source clients too, but it’s shades of grey: people shouldn’t hate on them for keeping 1 part closed source!
Only problem is, the average user gets hooked to the shiny UI, not to the invisible backend.
When Microsoft bought Skype, they switched from a secure P2P network to a server-centered network easy to mitm… and the majority of users said nothing. Later on, they switched a few UI elements, and suddenly there was a user uproar.
If Beeper gains any traction, a shiny privative UI is their out to monetize/enshittify the service.
sure, but an open source UI isn’t going to change that… they’d just close the source!
sure you can fork it, but you can also just copy the UI to an open source clone
imagine if twitter were activitypub: kinda like having an OSS backend with a proprietary front end… i’d bet the move to mastodon would be far quicker… network effects keep people on twitter… same here with OSS backend: we can reimplement the UI and people will have the same experience
Based on the history of how Google Chat used XMPP to federate and basically siphon users into its closed UI, then defederate… I no longer trust anyone with a closed UI that’s planning to offer “extra value” to its users.
If someone closed their open UI, you can always fork the last open version, which at least gives you an even start.
If
Twitter𝕏 were to switch to ActivityPub… I’d actually worry about people flocking back to 𝕏, back to their old networks and recommendation algorithms. Guess it’s no longer possible, since 𝕏 pretty much destroyed the old Twitter environment, but I’d still worry… and with Elon wanting to make 𝕏 a “social network for everything”, that sounds dangerously close to ActivityPub.you’re missing the fact that google chat and XMPP is a totally different situation… they used an open protocol; they didn’t open their backend
I’m glad for their work for the ecosystem. But when user respecting alternative is available, a propietary app should be thrown in a trash bin.
They will be offering a premium subscription offer for more bells and whistles other than the free option…I don’t know anything about user betrayals conducted by Beeper.
Proprietary clients.
I don’t understand the concern here.
You have no way of verifying that the client is only doing what it claims. The Open Source community is highly suspicious of proprietary software, doubly so when it’s based off of Open Source code.
If youre okay with that then no worries, but ofr myself and many others it’s an absolute deal breaker.
To be fair, the client they provide to make bridging more accessible is proprietary, however you can fire up a fresh copy of element and connect it if you want and just use the text interface.
The clients are closed so that they have something to sell and profit. Not everyone can afford to give their time away for free.
you kind of omitted the part where you have to host your own Matrix server in order to benefit from the bridges.
Is there a reason you couldn’t use either use a self hosted or the public hosted copy of element or an Android/iOS app and connect it directly to the beeper synapse/dendrite server?
Their clients are just closed forks of element anyways.
I’ll take the risk knowing what I know about the Beeper people that I’ve been working with for over two years.
“I know these guys, trust me” is not a valid security assessment.
If you know the team, then that’s a pretty good reason to trust them. Only works if you know the team, though.
That’s fine… for you, right now.
But I (and probably most users) don’t know them, over time people come and go, some even change who they are, businesses get sold. Only open source persists.
Thankfully all of the Matrix bridges they created for Beeper are open source.
Ok, ok, I get it… but I’m still wary of a business model based on closed clients. Guess we’ll see how it goes.
Sounds reasonable to me
You cannot see how the app works, cannot change how it works, cannot tell anyone how it works…
Huge deal for something as basic and important as interpersonal communication.
deleted by creator