-
Notifications
You must be signed in to change notification settings - Fork 826
Provide a way to permanently dismiss particular server announcements #8274
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This might be a server issue, we do use the actions provided by the server to display the notifications. |
In the current settings we have the option 'Show server notifications'. Does this setting has any effect for you? |
Many thanks for the suggestion! I did not expect web app notifications to be coupled to desktop client notifications like this. Especially given that...
I have quickly checked that dismissing the notifications on the web app does indeed resolve the issue. So this can be a workaround for other people. I will leave you to decide whether points 1 and 2 above + my UX surprise at your idea of coupling web app and desktop app notifications are problems worth fixing, possibly as part of a different issue. |
How to use GitHub
Feature request
Which Nextcloud Version are you currently using: 3.16.4daily (Arch)
Is your feature request related to a problem? Please describe.
The Nextcloud Desktop client shows server announcements every time it is started. However one of the Nextcloud servers that I use professionally, which is not under my control, leaves server announcements around for a very long time (oldest one is from two years ago). Seeing desktop popups on every machine boot about these very old server news that I have already read is annoying and also counterproductive as it induces notification fatigue: if the server adds a new announcement, I am unlikely to see it.
Describe the solution you'd like
I would like to have a way to tell the desktop client that I have read and understood a particular server notification and do not want to hear about it again.
Describe alternatives you've considered
The text was updated successfully, but these errors were encountered: