Currently looking at the idea of trying to bridge everything to Matrix in a way that gives me both a single app to worry about, and backups of all my messages in perpetuity
Most of my messages these days are on (most to least):
Telegram
Discord
MMS
Email
All of these are in principle bridgible. It's the last two I am skeptical about
Will I end up doing this?
Close date updated to 2023-03-31 3:52 am
Related questions
🏅 Top traders
| # | Name | Total profit |
|---|---|---|
| 1 | Ṁ30 | |
| 2 | Ṁ25 | |
| 3 | Ṁ11 | |
| 4 | Ṁ0 |
I've run a homeserver for a few years now and almost* completely switched to beeper. I agree it's nice to have everything consolidated but a lot of the more functional bridges (especially mx-puppet-*) are just bad and others are a pain to get working (SMS). Beeper makes SMS/MMS bridging one-click as part of the app and they're rewriting the entire mx-puppet suite in go for better reliability. Plus they're doing a lot of work circumventing some of Synapse's inherent weaknesses with their own Hungryserv bridge handler. On the whole I'm confident you could get Telegram and Discord working pretty easily in puppet mode but you may be less than thrilled with reliability. I'm less bullish on SMS, especially in a usable form. Postmoogle looks like it might work for email but I haven't ever touched it.
* The only thing left running on my homeserver is IRC via Heisenbridge, but Beeper just hired the lead dev so I'm hoping it gets added as an official bridge in the future.
@wasabipesto (no pressure) I wonder what you think what are the biggest issues with Beeper - e.g. what could prevent it from succeeding at having >10M users.
@o Right now the biggest issue is the gradual onboarding (just a few users per week), but once they get their new infrastructure up that'll be a lot better. Long-term there will be individual features from each bridged service that won't be available (iMessage location sharing, Discord threads, etc) and new services that people want bridged, they'll have to figure out what to prioritize and try to get each feature/bridge rolled out quickly enough that people don't just go back to their regular apps.
@o Definitely self-host. I already run a webserver, so it isn't a huge deal to add one more service. I've been meaning to rebuild the thing anyways, at some point