signal VS signal-cli

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

Not official but this works darn well: https://github.com/AsamK/signal-cli

If you want one for just personal use; this works well: https://github.com/AsamK/signal-cli

Just sign up with a Twilio number (using voice call) and you can make your own bot.

Here is my docker compose, maybe it is helpful: signal: #registerung tutorial # signal-cli --username +12345678 register --voice --captcha censored # https://github.com/AsamK/signal-cli/wiki/Registration-with-captcha # https://signalcaptchas.org/registration/generate.html IN CHROME # signal-cli -u +12345678 verify 123456 # signal-cli -u +1234567 send -m "This is a message" +12345678 #curl -X POST -H "Content-Type: application/json" -d '{"message": "bliblob", "number": "+41824174983", "recipients": ["+21412430"]}' 'http://signal:8080/v2/send' #external testing image: bbernhard/signal-cli-rest-api:latest container_name: signal restart: unless-stopped hostname: signal networks: - monitoring volumes: - /docker/prometheus/signal/client:/root/.local/share/signal-cli - /docker/prometheus/signal/client:/home/.local/share/signal-cli labels: - com.centurylinklabs.watchtower.enable=true environment: - USE_NATIVE=0 signalweb: # curl -X POST localhost:9100/api/v2/alertmanager -d '{"alerts": [{"status": "firing","labels": {"alertname": "test"},"annotations": {"message": "Test alert."}}]}' image: registry.gitlab.com/schlauerlauer/alertmanager-webhook-signal:latest container_name: signalweb restart: unless-stopped hostname: signalweb networks: - monitoring volumes: - /docker/prometheus/signal/web/config.yml:/root/config.yaml labels: - com.centurylinklabs.watchtower.enable=true

Yes, using the signal-cli program. It has a built in JSON RPC API that can be used to develop application integrations

Last commit was 2 days ago so it should still work: https://github.com/AsamK/signal-cli

Sorry to hear. Then the cheap backup may be a Signal CLI forwarded over to mqtt CLI

build, install and configure/register signal-cli. The code snippet below assumes you are running it in multi-account mode, but I'll leave a comment where it matters

No official API that is public from what I can tell, but appears this works https://github.com/AsamK/signal-cli