signal VS libsignal-service-java

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

Clicking on the first link of the read me bring you to the wrapped java API : https://github.com/signalapp/libsignal-service-java Which is archived

It uses signal-cli to deliver the messages. signal-cli is a wrapper around libsignal-service-java.

To all the humans mulling to play with this library, note that the signal-service-java[0] dependency signald relies upon isn't an officially shipped one. It's a fork.

The official implementation[1] hasn't been updated for around 1,5 years.

[0]: https://git.callpipe.com/finn/signald/-/blob/master/build.gr...

[1]: https://github.com/signalapp/libsignal-service-java