signal VS facebook

On-device bridging works like this https://blog.beeper.com/p/how-beeper-mini-works. We'll put together a full technical deep dive for the real launch, this is just an open beta. Our signal bridge code is open source: https://github.com/mautrix/signal

You don't have to use our hosted bridges, we've made it ridiculously easy to self host: https://github.com/beeper/bridge-manager

Exactly yeah, I used this bridge with this playbook

I personally recommend going with a Matrix client and building a bridge to your Signal account.

OWS has historically been hostile to third party implementations outside of their clients. There are multiple unofficial options but the only one I've been looking at is the bridge with matrix, though setting up a matrix server just for this is likely overkill.

However, looking at the Matrix docs for the mautrix-signal bridge, it seems to be open-source and end-to-end encrypted. You'll have to look through the source code to figure out how they did that, I guess, because I couldn't find any details.

Once you have the home server set up and configured (not covered here because it's a process), clone the bridge repo (for instance mautrix-signal and follow the instructions.

the signal matrix bridge currently listed on matrix.org (https://github.com/tulir/mautrix-signal) uses signald

My Facebook bridge constantly locks up my account. [1]

[1] https://github.com/mautrix/facebook/issues/236

Sure, I use this bridge (https://github.com/mautrix/facebook) to bridge synapse server to my facebook account, so I can use facebook messenger through my synapse server. I like it mainly so I don't have to install facebook messenger on my phone.

It's unrelated, except for the fact that I used the reverse engineering of the facebook messenger protocol by the mautrix team. [1]

I may add a "matrix plugin" [2] if I feel like it someday, but probably after I implement group chat support. Then you'll be able to use XMPP<->Matrix<->some-other-thing for extra over-engineering points. ;)

I prefer XMPP because it's lighter on resources, server-wise at least, and it's managed through a democratic process, which has it upsides and downsides. As someone I like said "democracy is boring, dictatorship works faster".

[1] https://github.com/mautrix/facebook

There exists a Matrix-Facebook bridge, but unfortunately it requires a home server to run it and many people can't afford that.

I've recently set up a synapse instance on my home server using the official docker image, and a mautrix-facebook bridge also using docker. So far it's all working great! However, I've had issues setting up mautrix-whatsapp: when I follow the setup instructions on the GitHub I get the following error:

like this?

The bridges can get a little more complicated, here's the facebook setup instructions for python, but if that's too much for you then I'd reconsider beeper (p.s. they said thanks for the feedback on the sign-up form). I don't know anything about their payment options, but I know that you can always just use the Element chat client, available for web, android, ios, desktop in the usual stores.