signald VS signal-cli

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.

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