signal-cli

Good to know! Thanks. I notice the README file for signal-cli [1] says registration "may require solving a CAPTCHA challenge", which might involve running proprietary software. I found a forum post that says this also sometimes happens on sign-in [2], which might make it difficult to use Signal without proprietary software. I might try it anyway at some point because it does say "may" :) [1] https://github.com/AsamK/signal-cli [2] https://community.e.foundation/t/signal-and-hcaptcha/83470

WhatSignal, WhatsApp <-> Signal relay, written in Go https://github.com/bikemazzell/whatsignal I'm working on a WhatsApp to Signal relay. I.e.: whenever someone sends a WA message to you, it appears in your Signal. You can reply and it will go back to the original sender. Why? I'm privacy conscious and don't fancy using a Meta product. But some of my friends/associates/family still insist on WhatsApp only. Running this WhatBridge service on my micro server behind a VPN allows me to communicate without having WhatsApp on my mobile. Behind the scenes, it connects WAHA (https://github.com/devlikeapro/waha ) and Signal CLI (https://github.com/AsamK/signal-cli). Still early stages, but getting closer to a workable state.

While that's true even in the general case (through reverse engineering), it's especially true in the case of Signal because it's open source. There are libraries for interacting with Signal services (one from Signal themselves), here is a CLI tool that uses a patched official library: <https://github.com/AsamK/signal-cli>

On Signal it is way easier thanks to signal-cli [1]. [1] https://github.com/AsamK/signal-cli

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

- Idris: https://www.idris-lang.org/ - clip.cpp: https://github.com/monatis/clip.cpp - trurl: https://github.com/curl/trurl - cosmopolitan: https://github.com/jart/cosmopolitan - signalcli: 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.

Started with just the email integration, and added other integration types over time, one by one. A few were contributed as GitHub PRs. The Signal one took by far the most effort to get going. But, for ideological reasons, I really wanted to have it :-) Unlike most other services, Signal doesn't have public HTTP API for sending messages. Instead you have to run your own local Signal client and send messages through it. Healthchecks is using signal-cli: https://github.com/AsamK/signal-cli

I don't know about the moderation tools for large channels, but bots should be possible: https://github.com/AsamK/signal-cli

A good free way to achieve this is to use Signal. This project https://github.com/AsamK/signal-cli enables you to send Signal messages from the command line, including from Raspberry Pis. It obviously needs an internet connection to work, but has the added bonus of being more secure than SMS.

Possibly of interest: https://github.com/AsamK/signal-cli

"After filling the captcha, the site doesn't show the token but redirects to a signalcaptcha:// url that contains the token. [...] To see the URL you can open the browser developer tools (F12) before completing the captcha." https://github.com/AsamK/signal-cli/wiki/Registration-with-c... Using Tor Browser I can see the signalcaptcha:// address in the window title of a detached Developer Tools window.

signal-cli uses a clearly identifiable user agent [0] that could easily be blocked if Signal wanted to. signal-cli could escalate by trying to evade that kind of a block, but as it stands signal-cli has been operating without trouble for several years. I meant they may ask some clients not to use their servers, but they don't have any enforcement mechanism in place beyond asking them to stop on github. [0] https://github.com/AsamK/signal-cli/blob/05abb3f9f6294677d2d...

I said it's not enforced. I cannot speak for moxie or Signal. I can speak for my own experiences, as the maintainer of a fork of signal-cli, and I have never seen any evidence that Signal's servers block signal-cli or my fork. I don't know about signal-cli but my fork clearly identifies itself in the user agent (and another field called the "signal agent") to the server. If they wanted to block me they could. edit: signal-cli also sets a user agent clearly identifies itself: https://github.com/AsamK/signal-cli/blob/05abb3f9f6294677d2d...