76
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 20 Mar 2024
76 points (100.0% liked)
Technology
37758 readers
646 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
I'd like to have a source for this claim, please.
I don't have a direct source other than the source code of the software they use: https://github.com/mautrix/signal
When using one of their "cloud hosted" bridges, the bridge software (that connects between Matrix/Beeper and other protocols) has to read all message content. Otherwise, it's impossible to bridge to another protocol. E2EE becomes end (other users) to bridge (beeper) encryption.
With "local hosted" bridges, E2EE stays intact, but messages can't be sent/received if the device hosting the bridge is unavailable.
In the future, with MLS (a different E2EE protocol), it could be possible to keep E2EE even when bridging to Matrix on cloud hosted bridges.
I've been using it with Facebook for a long time and I've never had any issues or scary messages. It's the main reason I use it as I don't want Facebook on my phone.
Me too! Just commenting to show it doesn't happen to everyone.
I'm contemplating trying to run the meta bridge locally to get around that issue, it has to do with their server running in I think Finland?