signald VS signal

Signald : https://gitlab.com/signald/signald/-/issues/259

This is neat.

I looked at the install instructions ("from source") and i while there were instructions, there was no download link for the tarball or even the git repository.

You have to click on the "gitlab" widget that shows the number of stars on the start page to get to the gitlab repository at https://gitlab.com/signald/signald

I've been using Signald for the last few months and then bridging it to Matrix. I think building exactly the same thing based off the Rust client is the most compelling option (and probably something I'd be interested in working on as well!). Given that a double-puppeted Signal account can be used with Matrix today, it'd be a shame to invest in Signal-specific UI. There are multiple "nearly there" Matrix clients that can work on the pinephone and others. You could even bridge libpurple to Matrix if you're into that ecosystem.

As Signal does not have a real API, it uses signald for communication with Signals server, which is also open source: https://gitlab.com/signald/signald

It looks like you just need a client that uses https://gitlab.com/signald/signald, and the matrix-signal bridge /u/anakinfredo posted is one of them.

When I wanted to use Signal on my PinePhone and realized how restrictive Signal was in a lot of ways I started looking at Matrix. Matrix feels a lot more like what chat "should" be, if it weren't for reality - there's an existing Java client (https://gitlab.com/signald/signald) that I've used for a few weeks and been impressed with. Now I bridge my Signal account to Matrix as the first step towards migrating away.

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