-
-
Notifications
You must be signed in to change notification settings - Fork 390
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
Do not show notifications if already seen #3625
Comments
Technical analysis from Nik from the chat: looking at NotificationFetcher.fetchNotifications(), that uses the marker from the API (/api/v1/markers), and account.lastNotificationId. account.lastNotificationId will be the ID of the top-most notification the user could see when NotificationsFragment pauses (see NotificationsFragment.onPause(), and the code in the view model that handles the SaveVisiblelId action. But the marker is never updated to reflect the ID of the most recent notification (i.e., using https://docs.joinmastodon.org/methods/markers/#create). I think there's three bugs in NotificationFetcher.fetchNotifications().
Note that using the marker API like this means that if the user uses two clients that use the marker API then the user seeing a notification in one client will mean it won't show up as an Android notification in Tusky (it will still show up on the Notifications tab). |
One could argue that this should also be done for status shown in any other timeline. Especially replies are actually "seen" there and do not need to be reported again as system notifications. |
Notifications that were already seen in the notifications tab should not be shown as system notifications again.
Tusky Version: this should be older than v22
I searched or browsed the repo’s other issues to ensure this is not a duplicate.
Maybe related / same to Duplicate push notifications in Tusky 22 beta #3616
The text was updated successfully, but these errors were encountered: