@tripplehelix I've been using it for almost 3 years, and my experience has been: multiple client rewrites, different features per platform, unsustainable architecture and reliability problems. 3 years in you still can't delete a chat 🤷
I no longer use it for anything critical, because there were just too many times that messages I need to send (or receive) were just stuck in limbo.
But as long as the messages you're sending aren't critical, it's very nice to have all the chats in one place.
@tripplehelix the way the "bridges" currently work is a VM spins up for each bridge, per user, and all incoming network messages are decrypted in the bridge before being re-encrypted to send to your client, so "end-to-end" is not an accurate description. (But they are working on moving more of the bridges to working the way their iMessage (and soon Signal) solution works, where stuff is actually e2e encrypted.)
This means that, for the bulk of services you'd connect to, messages can absolutely be read by Beeper staff, and the massive pile of VMs that enable it often need attention on their end.
~115,000 users, averaging like 4 connected networks means there are 460,000 virtual machines running. Now that it's open to all, the number of VMs will be increasingly unmanageable.
@tripplehelix
It's been great so far! Though they were recently acquired by Automattic. So, like with all acquisitions, we've yet to see if it stays that way.
Add comment