News for hackers. Stuff that matters.

A comment on SignalBotOne – Notification Webhooks for Signal. Parent comment

Re:SignalBotOne – Notification Webhooks for Signal by gruez on Friday March 28, 2025 @02:57PM (#43508843)
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.
[ Parent | on HN ]
Re:SignalBotOne – Notification Webhooks for Signal by aftbit on Friday March 28, 2025 @03:26PM (#43509087)
Yes - if it were open-source, you could self host it.
[ Parent | on HN ]
Re:SignalBotOne – Notification Webhooks for Signal by zikduruqe on Friday March 28, 2025 @03:31PM (#43509131)
Here ya go. I use this for various notifications for my home network, versus using email.

https://github.com/bbernhard/signal-cli-rest-api

[ Parent | on HN ]
Re:SignalBotOne – Notification Webhooks for Signal by npodbielski on Friday March 28, 2025 @04:20PM (#43509491)
Seems interesting but I have already second app linked to my profile.
[ Parent | on HN ]
Re:SignalBotOne – Notification Webhooks for Signal by ranger_danger on Friday March 28, 2025 @04:23PM (#43509508)
https://ntfy.sh

https://github.com/caronc/apprise

[ Parent | on HN ]
Re:SignalBotOne – Notification Webhooks for Signal by zikduruqe on Friday March 28, 2025 @09:03PM (#43511747)
Apprise is awesome.
[ Parent | on HN ]
Re:SignalBotOne – Notification Webhooks for Signal by npodbielski on Saturday March 29, 2025 @01:24PM (#43517043)
I am using apprise for several years. It works but have few drawbacks:

-no login, almost no security

-sometimes it does not works and there are no logs to see what exactly happens.

-secret storage is very bad

Ntfy I will check thanks.

[ Parent | on HN ]
Re:SignalBotOne – Notification Webhooks for Signal by l2g on Sunday March 30, 2025 @06:31PM (#43528382)
> no login

That's because the goal is to allow you to stick a proper nginx or webserver infront of it if you need this layer.

> Sometimes doesn't work

Please open a ticket and share why since your able to determine this from your logs. Maybe it can be fixed upstream?

> Secret storage is bad

You can create a string (key) that is randomized > 200+ characters. What can be improved to assist you with your concerns?

[ Parent | on HN ]