Skip to content
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

Automatically remove Android notifications only when read #2528

Closed
Discostu36 opened this issue May 15, 2022 · 4 comments · Fixed by #3312
Closed

Automatically remove Android notifications only when read #2528

Discostu36 opened this issue May 15, 2022 · 4 comments · Fixed by #3312

Comments

@Discostu36
Copy link

At the moment, Android notifications are automatically removed when the Tusky app is open(ed). Instead, they should only be removed, when the corresponding Mastadon notification has been seen.

@charlag
Copy link
Collaborator

charlag commented May 15, 2022

I'm not sure if it should work like that to be honest. Compare to other apps, like messengers, don't they remove notifications as well?
We could however indicate it inside the app

@9Lukas5
Copy link

9Lukas5 commented Oct 31, 2022

I'm fine with the system notification being removed directly on opening the app, but a counter on the bell icon of all unread notifications would be a good thing.

@Lakoja
Copy link
Collaborator

Lakoja commented Feb 5, 2023

Bump.

Was about to open this issue as well.

Maybe a somewhat easier (intermediate) step would be to remove notifcations only once the notification timeline is opened.

@Discostu36
Copy link
Author

Compare to other apps, like messengers, don't they remove notifications as well?

This depends on the messenger. WhatsApp, for examples, removes notifications as soon as the app is opened. Telegram, on the other hand, only dismisses notifications once the specific chat is opened that the notification is for.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants