Sometimes a notification cannot be dismissed

feld commented

2020-08-20 14:09:15 +00:00

Owner

I've run into this a few times, cannot figure out why a notification will not get dismissed.

I've run into this a few times, cannot figure out why a notification will not get dismissed. ![notification](/attachments/ee823d06-a34b-445d-bd14-0d0539f3e89a)

notification.mp4

521 KiB

patcoll commented

2020-08-24 20:39:41 +00:00

Member

@feld Does this notification reference a direct status?

@feld Does this notification reference a `direct` status?

eugenijm commented

2020-08-24 23:19:22 +00:00

Member

Looks like the author has deleted that status after FE has already received and stored the corresponding notification (because of the typo I guess, since their next status is the corrected version of it). Since the notification no longer exists (BE deletes it along with the status), the FE most likely gets the 4xx error when calling POST /api/v1/pleroma/notifications/read.

E.g., steps to reproduce:

mention the user while their FE is opened but the window is unfocused (so that the notification is not read automatically, as soon as it appears)
wait a few seconds for the notification to be created and added to FE
delete the status
as the receiving user, open the notification page, FE tries to read it but gets the 400 response since it no longer exists on BE

Looks like the author has deleted that status after FE has already received and stored the corresponding notification (because of the typo I guess, since their next status is the corrected version of it). Since the notification no longer exists (BE deletes it along with the status), the FE most likely gets the 4xx error when calling `POST /api/v1/pleroma/notifications/read`. E.g., steps to reproduce: 1) mention the user while their FE is opened but the window is unfocused (so that the notification is not read automatically, as soon as it appears) 2) wait a few seconds for the notification to be created and added to FE 3) delete the status 4) as the receiving user, open the notification page, FE tries to read it but gets the 400 response since it no longer exists on BE

patcoll commented

2020-08-28 15:55:58 +00:00

Member

Should the back-end handle this gracefully too?

eugenijm commented

2020-08-28 16:51:00 +00:00

Member

I think it sort of already does, it broadcasts the status delete event (https://docs.joinmastodon.org/methods/timelines/streaming/#websocket-a-idwebsocketa) which FE can use to remove the corresponding notification as soon as the status is deleted (before the user navigates to the notification feed and tries to mark it as read)

root added the

Doing

label

2026-02-06 06:33:01 +00:00

Rows
Columns

Sometimes a notification cannot be dismissed #49