Recently discovered this. Molly supports link with existing device just like on signal desktop. It even has benefit of getting entire chat history unlike signal desktop. Just restore the signal backup file during setup and then click link with existing device. Then scan with you primary phone. Beauty of open source. Molly: https://molly.im/
Element as a client with a Matrix server bridged to Signal works great, too. Centralizes your history on your own secure server, too.
More complex, though.
Also worth noting that communication between signal and matrix through most bridges requires the message to be decrypted and reencrypted, thereby breaking E2EE which kinda defeats the point.
Unless you’re running a bridge on a locked down home server on your own network, not sure it’s the most secure.
Very good point. For me its a private server and I run both the bridge and the matrix server inside the same docker network.
Oh nice! I just like to warn people because I saw bridges get popular with Beeper and people don’t always catch that security-for-ease compromise
I’m not trying rip on Beeper, by the way. I don’t use them and never have. They could be totally legitimate and good-faith actors, but the reencryption issue with bridges sets my tinfoil hat off!
Oh yea, I won’t use Beeper. Self-hosted for me!
This is the solution I’m considering. Does it make sense if you have no actual contacts on Matrix? Do you think it would work on localhost instead of remote server? My use case is to get a single conversation view that includes Signal and Telegram contacts, but I don’t need it on multiples devices, one desktop box is fine.
I use it unfederated. Its on my local network server, running in docker with bridges to Signal, IRC, and Discord, no Matrix contacts. Works great for me.