[GH-ISSUE #1103] Acknowledging a notification on the web interface does not extend to the Android app #773

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

Originally created by @wsw70 on GitHub (May 6, 2024).
Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1103

Question

When I acknowledge a notification on the web interface, it is not acknowledged on the Android app (and vice-versa). Is this normal and expected?

  • If this is not normal (= one ack should do it for all devices) → is there a specific thing that needs to be open between the devices (I do not think so, I am asking just in case -- they all ultimately point to the same instance)
  • If this is normal → I will raise a feature idea :)
Originally created by @wsw70 on GitHub (May 6, 2024). Original GitHub issue: https://github.com/binwiederhier/ntfy/issues/1103 <!-- Before you submit, consider asking on Discord/Matrix instead. You'll usually get an answer sooner, and there are more people there to help! - Discord: https://discord.gg/cT7ECsZj9w - Matrix: https://matrix.to/#/#ntfy:matrix.org / https://matrix.to/#/#ntfy-space:matrix.org --> :question: **Question** When I acknowledge a notification on the web interface, it is not acknowledged on the Android app (and vice-versa). Is this normal and expected? - If this is not normal (= one ack should do it for all devices) → is there a specific thing that needs to be open between the devices (I do not think so, I am asking just in case -- they all ultimately point to the same instance) - If this is normal → I will raise a feature idea :)
BreizhHardware 2026-05-07 00:27:21 +02:00
  • closed this issue
  • added the
    question
    label
Author
Owner

@wunter8 commented on GitHub (May 6, 2024):

This is the expected behavior right now. There have been discussions about implementing sync across devices, but it hasn't been implemented yet (and there's no estimated timeline)

<!-- gh-comment-id:2096090181 --> @wunter8 commented on GitHub (May 6, 2024): This is the expected behavior right now. There have been discussions about implementing sync across devices, but it hasn't been implemented yet (and there's no estimated timeline)
Author
Owner

@wsw70 commented on GitHub (May 6, 2024):

Thank you for the answer. I infer that since the acknowledgment is purely local, ntfy is a kind of subpub system without centralized message handling, right? (as opposed to having the clients poll a centralized DB and push their acknowledgments there)

This is purely an "out of curiosity" question.

<!-- gh-comment-id:2096129290 --> @wsw70 commented on GitHub (May 6, 2024): Thank you for the answer. I infer that since the acknowledgment is purely local, ntfy is a kind of subpub system without centralized message handling, right? (as opposed to having the clients poll a centralized DB and push their acknowledgments there) This is purely an "out of curiosity" question.
Author
Owner

@wunter8 commented on GitHub (May 6, 2024):

Haha, yes, "ntfy (pronounced notify) is a simple HTTP-based pub-sub notification service" (from the first line of the website)

Right now, subscribed topics can be synced across instances of the web app (so if you subscribe to a topic on your desktop in the web app, the web app on your laptop will also subscribe to that topic). That is done using a special "sync" topic in the background. I presume message syncing will work similarly

<!-- gh-comment-id:2096164793 --> @wunter8 commented on GitHub (May 6, 2024): Haha, yes, "ntfy (pronounced notify) is a simple HTTP-based [pub-sub](https://en.wikipedia.org/wiki/Publish%E2%80%93subscribe_pattern) notification service" (from the first line of the website) Right now, subscribed topics can be synced across instances of the web app (so if you subscribe to a topic on your desktop in the web app, the web app on your laptop will also subscribe to that topic). That is done using a special "sync" topic in the background. I presume message syncing will work similarly
Author
Owner

@wsw70 commented on GitHub (May 6, 2024):

Haha, yes, "ntfy (pronounced notify) is a simple HTTP-based pub-sub notification service" (from the first line of the website)

I should be more careful reading the web site (I jumped to the docs :))

Thanks a lot - it's all clear now!

<!-- gh-comment-id:2096194658 --> @wsw70 commented on GitHub (May 6, 2024): > Haha, yes, "ntfy (pronounced notify) is a simple HTTP-based [pub-sub](https://en.wikipedia.org/wiki/Publish%E2%80%93subscribe_pattern) notification service" (from the first line of the website) I should be more careful reading the web site (I jumped to the docs :)) Thanks a lot - it's all clear now!
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#773
No description provided.