Cease and desist from Signal incoming, from their legal terms:
> "Signal", Signal logos, and other trademarks are trademarks or registered trademarks of Signal Technology Foundation in the United States and other countries (more info here).
My SaaS is sending monitoring notifications using signal-cli, and I regularly run into rate limits (enforced by Signal servers, not signal-cli), especially when sending to new numbers/usernames.
To the author--do you have any plans on how to work around that?
GP is presumably asking what their plans are once the service gets popular, runs into the ratelinit, and cannot send any notifications at all (or with significant delays) to the clients.
Does it matter? It's a SaaS anyways, so if they wanted to go rogue and use it to eavesdrop on your chats open source wouldn't really prevent that. They even specifically recommend using a dedicated group chat for notification purposes. For self-hosted deployments there's already a multitude of projects that expose an API to send signal messages.
Seems interesting but it looks like some cli with web server running on someone else's machine, so basically no security, no encryption. Also probably this bot have an access to your entire chat history.
The bot has access to any sent messages to yourself, plus any chatter in group chats if you have enabled that. So don't use it for sensitive stuff, and use a dedicated group. It was developed to relay sensor data and such, not war plans.
I understand the reference and I appreciate that.
Though the whole point of using signal is to have privacy.
If you need outside person to send you some messages than that privacy is non existent.
Now, I do not plan wars with Yemen but still want to keep my private conversations with my wife about my furniture, well... private. For solving notifications I can just do what I do now: selfhost matrix and apprise.
So the whole solution seems interesting, though I fail to see point of using it whatsoever.
If you could self host it yourself too? Yes but like that? No.
Nice! I was considering setting up telegram/slack/discord for personal push notifications of events in personal IT infrastructure, since Signal is fairly undercooked in this department, but this might be a good solution for me.
Better docs would be appreciated! Can you guide us to use it? I’m not a slack guy because it’s too distracting, but easy secure chat integrations could be big … keep it up!
If you don't know what "API" or "webhooks" are, then you're probably not the target audience. That's fine. Your aunt probably doesn't know what an "enterprise workload engine"[1] is, but that doesn't mean vmware needs to provide a dumbed down description so everyone can understand.
"Receive messages on Signal via a simple API. Perfect for notifications and alerts." is not "how it works" but "how you use it".
This is "hacker news". A hacker is typically interested in how something works (under the hood).
If a hacker asks "how does this mobile phone work?" then they are not looking for "well here you press a button and then here you speak" but something about radio waves and cell towers and mobile operating systems.
You built this? Would you like to comment what your future plans are?
Your self-description is "entrepreneur love for automation". Is it fair to assume that if this takes off then you are planning to introduce paid plans (perhaps with some revenue sharing with the signal folks to lift rate limits for you)?
I built this for fun and my own notifications. I don't think there's much commercial value here since there's zero moat. But it would be nice if we could raise funds for Signal.