this post was submitted on 27 Jul 2023
133 points (100.0% liked)
Technology
37746 readers
522 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
Beeper's server set up is actually a lot more complicated than just standard Synapse at this point. When they say you can "self host Beeper" that's really not accurate at this point at all. All of their 3rd party chat bridges are dynamically spun up on a per user basis with hungryserv and those servers operate in parallel with a synapse server for Matrix interoperability all behind a roomserv server. Here's a presentation that one of their lead developers created regarding their new architecture.
Most of that extra stuff is there to handle user contact privacy and security with the bridges, which is fair. I don't have any interest in self hosting beepers full setup, I want to get the functionality of multiple messaging services in one client - which I have, with my self-hosted matrix instance and the bridges they help develop and maintain.
I wish all of it was open source, but I did feel it necessary to head off comments that imply that the entire thing is closed source. Their implementation around dynamic servers and isolated containers spinning up isn't really the bit that seems relevant regarding user privacy with regards to data scraping or anything. There are a lot of comments in here implying it's fully proprietary, but there's a lot more nuance to it than that, as you point out.
Personally, I think it'd be nice if you could self-host just the bridge instances and connect them with beeper yourself, so that the part that isn't e2e encrypted is running on software you can validate and hardware you control.
I 100% agree this would be a great solution. That's what I thought this page was going to be at first until I kept reading and realized it's just a config guide for the Matrix Ansible setup. I wish they didn't say "self host Beeper" on that page at all because self hosting Matrix has absolutely nothing to do with the Beeper service other than their devs built the bridges that they're showing you how to set up with Matrix.
A bit off topic, but is this dev unironically using thin, light gray text on a white background?
It looks like they're slides from a powerpoint style presentation.. in the following frames, the light grey text is legible. Still, not a good way to present that data, heh. Stuff like that irks me so bad