Yesterday, while adding support for #ntfy, I introduced a small bug that causes duplicate notifications on #snac2. My fault 🙂 I've already sent the PR with the fix to the developer.
@dziq@stesnac There are two ways: you can self-host a ntfy server (more complex) or, to test, just create a random topic name (I use something like "openssl rand -hex 10" - output is something like 06b333b62ed2d644d4d7) and set it both on snac2 (as server address, https://ntfy.sh/06b333b62ed2d644d4d7 ) and on your local ntfy app. Notifications will be auto-magically delivered to your app/apps/web browser/etc.
@dziq You can continue to use this snac server as it'll be marked as "stable" as soon as I'll have finished with some things. You can set your own ntfy address (and token, if present) from ths BSD Cafe snac server as well
@dziq I'd suggest to increase the num_threads - the default is 4, but I found it to be too low to send out things in a short time. Of course, it depends on your hardware.
Otherwise, snac2 is great by default, so I'd just suggest you to try. Please, let me know about your impressions and experience!
Add comment