bug: Prevent read recipts from going backwards #741

Closed
opened 2025-04-14 20:30:57 +00:00 by nex · 5 comments
Owner
No description provided.
Owner

According to tulir, read receipts are strictly meant to go forward. Receipts on the same or prev event IDs should be ignored. This seems to cause endlessly-unread messages in some bridges, and when appservice edus + double puppeting is enabled results in an infinite loop in the discord bridge

According to tulir, read receipts are strictly meant to go forward. Receipts on the same or prev event IDs should be ignored. This seems to cause endlessly-unread messages in some bridges, and when appservice edus + double puppeting is enabled results in an infinite loop in the discord bridge
Author
Owner

@Jade I remember a commit related to this at some point - is this issue resolved?

@Jade I remember a commit related to this at some point - is this issue resolved?
Owner

Not yet, got halfway through doing it but read receipts are more complicated than first glance because of threads. Aiming to do it in the next ~week though.

Not yet, got halfway through doing it but read receipts are more complicated than first glance because of threads. Aiming to do it in the next ~week though.
Jade added reference jade/read-receipts 2025-04-30 16:35:53 +00:00
Member

Did this get done?

Did this get done?
Owner

No

No
Jade closed this issue 2026-11-10 20:02:47 +00:00
Sign in to join this conversation.
No milestone
No assignees
3 participants
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
continuwuation/continuwuity#741
No description provided.