starred/ntfy

Fork 0

mirror of https://github.com/binwiederhier/ntfy.git synced 2026-05-09 16:35:53 +02:00

cancel notifications #39

New issue

Closed

opened 2026-05-07 00:19:01 +02:00 by BreizhHardware · 7 comments

BreizhHardware commented

2026-05-07 00:19:01 +02:00

Owner

Originally created by @binwiederhier on GitHub (Dec 9, 2021).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/43

Return token on publish

Or set token when publishing

Originally created by @binwiederhier on GitHub (Dec 9, 2021). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/43 Return token on publish Or set token when publishing

BreizhHardware

2026-05-07 00:19:01 +02:00

closed this issue
added the
in-progress 🏃

enhancement
labels

BreizhHardware commented

2026-05-07 00:19:02 +02:00

Author

Owner

@binwiederhier commented on GitHub (Mar 12, 2022):

So I think the token idea is not even necessary because the topic is implied to be either secret or protected anyway.

The difficulty is now how to update the clients. They'd all need to understand that a message with the same ID can get updated.

@binwiederhier commented on GitHub (Mar 12, 2022): So I think the token idea is not even necessary because the topic is implied to be either secret or protected anyway. The difficulty is now how to update the clients. They'd all need to understand that a message with the same ID can get updated.

BreizhHardware commented

2026-05-07 00:19:02 +02:00

Author

Owner

@binwiederhier commented on GitHub (Mar 12, 2022):

id=$(curl -d "Build process starting" ntfy.sh/mytopic | jq .id)
for progress in 10 20 30 40 50 60 70 80 90 100; do 
  curl -X PATCH -d "Build process running, currently ${progress}%" ntfy.sh/mytopic/$id
  sleep 10
done

@binwiederhier commented on GitHub (Mar 12, 2022): ``` id=$(curl -d "Build process starting" ntfy.sh/mytopic | jq .id) for progress in 10 20 30 40 50 60 70 80 90 100; do curl -X PATCH -d "Build process running, currently ${progress}%" ntfy.sh/mytopic/$id sleep 10 done ```

BreizhHardware commented

2026-05-07 00:19:02 +02:00

Author

Owner

@binwiederhier commented on GitHub (Mar 25, 2022):

I have decided to give this up for now. It adds complexity and nobody seems to want this feature. If there is suddenly a huge demand for it, I can revive the two branches: https://github.com/binwiederhier/ntfy/pull/187 + https://github.com/binwiederhier/ntfy-android/pull/19

@binwiederhier commented on GitHub (Mar 25, 2022): I have decided to give this up for now. It adds complexity and nobody seems to want this feature. If there is suddenly a huge demand for it, I can revive the two branches: https://github.com/binwiederhier/ntfy/pull/187 + https://github.com/binwiederhier/ntfy-android/pull/19

BreizhHardware commented

2026-05-07 00:19:02 +02:00

Author

Owner

@TippyLion28 commented on GitHub (Aug 19, 2022):

This would have useful applications in the IoT space, for example if my dehumidifier tank fills up and sends me a notification, there's no need for the notification to remain once I've emptied the tank. So would be useful if my automation could clear it from the android notification shade e.g. By deleting the notification or changing it's priority.

@TippyLion28 commented on GitHub (Aug 19, 2022): This would have useful applications in the IoT space, for example if my dehumidifier tank fills up and sends me a notification, there's no need for the notification to remain once I've emptied the tank. So would be useful if my automation could clear it from the android notification shade e.g. By deleting the notification or changing it's priority.

BreizhHardware commented

2026-05-07 00:19:03 +02:00

Author

Owner

@ser commented on GitHub (Sep 15, 2023):

It is extremely useful in monitoring systems, when for example your host is down and later it's up and previous notification is useless or even misguiding.

@ser commented on GitHub (Sep 15, 2023): It is extremely useful in monitoring systems, when for example your host is down and later it's up and previous notification is useless or even misguiding.

BreizhHardware commented

2026-05-07 00:19:03 +02:00

Author

Owner

@smashah commented on GitHub (Mar 31, 2024):

this feature would take this project to the next level for sure thanks

@smashah commented on GitHub (Mar 31, 2024): this feature would take this project to the next level for sure thanks

BreizhHardware commented

2026-05-07 00:19:03 +02:00

Author

Owner

@reneroth commented on GitHub (Jan 5, 2025):