mirror of
https://github.com/binwiederhier/ntfy.git
synced 2026-05-09 16:35:53 +02:00
[GH-ISSUE #1550] Debounce messages #1092
Labels
No labels
ai-generated
android-app
android-app
android-app
🪲 bug
build
build
dependencies
docs
enhancement
enhancement
🔥 HOT
in-progress 🏃
ios
prio:low
prio:low
pull-request
question
🔒 security
server
server
unified-push
web-app
website
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/ntfy#1092
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @jlaffaye on GitHub (Jan 16, 2026).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1550
💡 Idea
Add a debounce mechanism to prevent flooding messages.
Introduce two new parameters:
debounce_key: this will be used to group messages that should be debounceddebounce_interval: a period (like the currentdelayparameter)Every message with the same
debounce_keywill be dropped if another message was successfully sent (not drropped) in thedebounce_intervalinterval.💻 Target components
ntfy server
@BeeJay28 commented on GitHub (Jan 26, 2026):
Hello, I'd like to implement this issue, if that is ok.
I would maybe just hash the message-content with a quick hash-alg and use that, instead of manually providing the debounce-key. That should be sufficient to detect duplicates, unless there's another good reason for a manual debounce-key
@binwiederhier commented on GitHub (Mar 8, 2026):
Implement a client side debounce here
github.com/binwiederhier/ntfy@109271a930