20 ms·
I would probably just use Slack and Slack-bots for a low-code approach to this. Are there major downsides? I don't believe you would need to pay for Slack to us
by babyshake 5y ago
I would probably just use Slack and Slack-bots for a low-code approach to this. Are there major downsides? I don't believe you would need to pay for Slack to use primarily for up to a few dozen Slackbot messages per day.
- binwiederhier 5y agoAs I've said in another comment [1], if you're happy with what you have then by all means stick to it. I think the major upside of ntfy (aside from the bagillion features of course) is that it's so FREAKING EASY, and that it doesn't have auth. You probably don't remember your Slack auth token by heart. With ntfy, you can do: ./backup-server.sh; curl -d "backup done" ntfy.sh/shake_backups [1] https://news.ycombinator.com/item?id=29719738 https://news.ycombinator.com/item?id=29719738
- patleeman 5y agoI found that telegram works pretty well to get notifications from my personal server. Its pretty easy to set up a channel and bot.
- fragmede 5y agoThe major downside I see is you have to use Slack for that. If you're already in that ecosystem it's fine, though their notifications preferences could use a bit more configurability.