Notification System 2: The Realerting #151

Merged
parabitdev merged 13 commits from parabit/event-notifications into master 2025-09-15 22:24:49 +00:00
parabitdev commented 2025-09-04 19:41:21 +00:00 (Migrated from github.com)
  • Add notification system that has at least nfty as an output (future should include email/text?)
  • Add block notifications using the new system
  • Remove block notifications and exposed ntfy channel from stratifier code
- [x] Add notification system that has at least nfty as an output (future should include email/text?) - [x] Add block notifications using the new system - [x] Remove block notifications and exposed ntfy channel from stratifier code
parabitdev (Migrated from github.com) reviewed 2025-09-09 18:30:20 +00:00
parabitdev (Migrated from github.com) commented 2025-09-09 18:30:19 +00:00

Excellent callout, will prune

Excellent callout, will prune
parabitdev (Migrated from github.com) reviewed 2025-09-15 21:21:37 +00:00
@ -35,0 +36,4 @@
long,
help = "The channel at ntfy.sh to use for block found notifications"
)]
pub(crate) alerts_ntfy_channel: Option<String>,
parabitdev (Migrated from github.com) commented 2025-09-15 21:21:37 +00:00

I plan to add additional alerts services in the future (email/text/carrier pigeon) and the aim was to reduce the potential future confusion. I am open to instead opening an issue against that plan and dropping the ntfy if you feel that is more natural.

I plan to add additional alerts services in the future (email/text/carrier pigeon) and the aim was to reduce the potential future confusion. I am open to instead opening an issue against that plan and dropping the `ntfy` if you feel that is more natural.
parabitdev commented 2025-09-15 21:24:07 +00:00 (Migrated from github.com)

The second one worked with simulated events, but has not been tested fully end-to-end.

It will actually require one additional para server and that they be linked via sync. I believe this can actually be implemented as a test as we have all the individual parts working now and they have test wrappers.

The second one worked with simulated events, but has not been tested fully end-to-end. It will actually require one additional para server and that they be linked via sync. I believe this can actually be implemented as a test as we have all the individual parts working now and they have test wrappers.
Sign in to join this conversation.
No description provided.