[GH-ISSUE #224] Remove permanent notification when all notifications are paused #179

Closed
opened 2026-05-07 00:21:07 +02:00 by BreizhHardware · 9 comments

Originally created by @shadow00 on GitHub (Apr 26, 2022).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/224

Would it be possible to disable the permanent notification when all topic subscriptions have their notifications paused? Either globally or individually (ie. notifications are not globally paused, but all subscribed topics have been individually paused). This would help reduce notification clutter when ntfy is effectively not doing anything.

Originally created by @shadow00 on GitHub (Apr 26, 2022). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/224 Would it be possible to disable the permanent notification when all topic subscriptions have their notifications paused? Either globally or individually (ie. notifications are not globally paused, but all subscribed topics have been individually paused). This would help reduce notification clutter when ntfy is effectively not doing anything.
BreizhHardware 2026-05-07 00:21:07 +02:00
Author
Owner

@binwiederhier commented on GitHub (Apr 26, 2022):

You can manually hide the sticky notification. There are instructions here: https://ntfy.sh/docs/subscribe/phone/#instant-delivery

When you pause a subscription, ntfy will still listen for incoming notifications. It'll just not display them. So ntfy is definitely not idle. That's a misunderstanding on your part.

I hope this helps.

<!-- gh-comment-id:1109792813 --> @binwiederhier commented on GitHub (Apr 26, 2022): You can manually hide the sticky notification. There are instructions here: https://ntfy.sh/docs/subscribe/phone/#instant-delivery When you pause a subscription, ntfy will still listen for incoming notifications. It'll just not display them. So ntfy is definitely not idle. That's a misunderstanding on your part. I hope this helps.
Author
Owner

@shadow00 commented on GitHub (Apr 26, 2022):

Oh, I did not expect the app to keep listening for notifications on paused topics...

What if the app only listened in the background for non-paused topics, and fetched notifications for paused topics only when the user manually opens the app (or maybe even the actual topic)?
That way, you don't even need to start the background service if all topics are paused (in the spirit of "don't do something unless the user explicitly asks for it"), and the app's behaviour matches the user's (or maybe just mine? 😄 ) expectation of "paused" (ie. "stop listening to this topic").

(Just thinking out loud - perhaps going this far isn't really worth the effort?)

<!-- gh-comment-id:1109818251 --> @shadow00 commented on GitHub (Apr 26, 2022): Oh, I did not expect the app to keep listening for notifications on paused topics... What if the app only listened in the background for non-paused topics, and fetched notifications for paused topics only when the user manually opens the app (or maybe even the actual topic)? That way, you don't even need to start the background service if all topics are paused (in the spirit of "don't do something unless the user explicitly asks for it"), and the app's behaviour matches the user's (or maybe just mine? 😄 ) expectation of "paused" (ie. "stop listening to this topic"). (Just thinking out loud - perhaps going this far isn't really worth the effort?)
Author
Owner

@binwiederhier commented on GitHub (Apr 26, 2022):

Let me ask you this: What is your actual concern? Spell it out for me :-D Is it battery life? Or the foreground notification?

  • If it's battery life: It's usually 1% for the entire day for me, so that shouldn't really be an issue anymore
  • If it's the foreground notification, then I linked already how to disable it.

Pausing notifications doesn't mean pausing delivery. Some people (including me) have notifications paused for some topics, because they use it as a log. It was never meant as a means to stop delivery. There was a ticket in which we discussed making the delivery time configurable (instant, every 1min, 5min, 15min, ...), but it was deemed not really necessary (idk what the ticket was, maybe https://github.com/binwiederhier/ntfy/issues/76).

I don't want 100,000 options in the settings screen. It's already a lot. Right now, I don't really feel like I want to make this configurable.

<!-- gh-comment-id:1109958502 --> @binwiederhier commented on GitHub (Apr 26, 2022): Let me ask you this: What is your actual concern? Spell it out for me :-D Is it battery life? Or the foreground notification? - If it's battery life: It's usually 1% for the entire day for me, so that shouldn't really be an issue anymore - If it's the foreground notification, then I linked already how to disable it. Pausing notifications doesn't mean pausing delivery. Some people (including me) have notifications paused for some topics, because they use it as a log. It was never meant as a means to stop delivery. There was a ticket in which we discussed making the delivery time configurable (instant, every 1min, 5min, 15min, ...), but it was deemed not really necessary (idk what the ticket was, maybe https://github.com/binwiederhier/ntfy/issues/76). I don't want 100,000 options in the settings screen. It's already a lot. Right now, I don't really feel like I want to make this configurable.
Author
Owner

@shadow00 commented on GitHub (Apr 26, 2022):

In part it was the foregroud notification (which I've now disabled - thanks! I though that disabling it would also disable the foreground service), and part of it is the fact that I don't like to keep stuff running in the background unless necessary - so when I tell an app to pause something, I expect it to actually stop, rather than keep going silently in the background.

I don't really feel like I want to make this configurable

Me neither, it was a question on what the behaviour of "pause" should be. There's currently no way to stop the app from fetching a topic without actually unsubscribing from it, and going through the nuisance of manually setting it up again or restoring it from a backup (along with any other topics that may have been included in said backup).

I think it would be nice to have that ability: pausing a topic = stop asking for new data about it until re-enabled (and not just pausing notifications for it). Having the app stop fetching updates for a paused topic should not break your use case: you could still do quiet logging by setting the log priority to lowest and displaying only notifications with priority low or higher.

<!-- gh-comment-id:1110004432 --> @shadow00 commented on GitHub (Apr 26, 2022): In part it was the foregroud notification (which I've now disabled - thanks! I though that disabling it would also disable the foreground service), and part of it is the fact that I don't like to keep stuff running in the background unless necessary - so when I tell an app to pause something, I expect it to actually stop, rather than keep going silently in the background. > I don't really feel like I want to make this configurable Me neither, it was a question on what the behaviour of "pause" should be. There's currently no way to stop the app from fetching a topic without actually unsubscribing from it, and going through the nuisance of manually setting it up again or restoring it from a backup (along with any other topics that may have been included in said backup). I think it would be nice to have that ability: pausing a topic = stop asking for new data about it until re-enabled (and not just pausing notifications for it). Having the app stop fetching updates for a paused topic should not break your use case: you could still do quiet logging by setting the log priority to lowest and displaying only notifications with priority low or higher.
Author
Owner

@binwiederhier commented on GitHub (Apr 26, 2022):

I think this is a wording problem then. We actually talked about calling it "mute" instead of "pause" in the Discord channel in the context of translations. Maybe "mute" is a better word.

<!-- gh-comment-id:1110009486 --> @binwiederhier commented on GitHub (Apr 26, 2022): I think this is a wording problem then. We actually talked about calling it "mute" instead of "pause" in the Discord channel in the context of translations. Maybe "mute" is a better word.
Author
Owner

@shadow00 commented on GitHub (Apr 26, 2022):

I agree, "mute" would be an accurate description of the current behaviour.

<!-- gh-comment-id:1110153701 --> @shadow00 commented on GitHub (Apr 26, 2022): I agree, "mute" would be an accurate description of the current behaviour.
Author
Owner

@binwiederhier commented on GitHub (Apr 26, 2022):

github.com/binwiederhier/ntfy-android@0a446545dd
github.com/binwiederhier/ntfy-android@835ace34cd

I'm closing this for now. Thank you for reporting!

<!-- gh-comment-id:1110344353 --> @binwiederhier commented on GitHub (Apr 26, 2022): https://github.com/binwiederhier/ntfy-android/commit/0a446545dd436d9bf8743b8a193fe2cb4162979e https://github.com/binwiederhier/ntfy-android/commit/835ace34cd94463f243b51a04349f178ef9ba07d I'm closing this for now. Thank you for reporting!
Author
Owner

@Elu43 commented on GitHub (Jan 2, 2023):

You can manually hide the sticky notification. There are instructions here: https://ntfy.sh/docs/subscribe/phone/#instant-delivery

@binwiederhier Hi. It's probably a stupid question, but if you do that, will the notifications still be in "Instant delivery" mode ?

Thank you for your amazing software.

<!-- gh-comment-id:1369229199 --> @Elu43 commented on GitHub (Jan 2, 2023): > You can manually hide the sticky notification. There are instructions here: https://ntfy.sh/docs/subscribe/phone/#instant-delivery @binwiederhier Hi. It's probably a stupid question, but if you do that, will the notifications still be in "Instant delivery" mode ? Thank you for your amazing software.
Author
Owner

@binwiederhier commented on GitHub (Feb 1, 2023):

@binwiederhier Hi. It's probably a stupid question, but if you do that, will the notifications still be in "Instant delivery" mode ?

Notifications will still be instant yes. It just hides the sticky notification. Sorry for the super late reply.

<!-- gh-comment-id:1412685731 --> @binwiederhier commented on GitHub (Feb 1, 2023): > @binwiederhier Hi. It's probably a stupid question, but if you do that, will the notifications still be in "Instant delivery" mode ? Notifications will still be instant yes. It just hides the sticky notification. Sorry for the super late reply.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ntfy#179
No description provided.