bug: Prevent read recipts from going backwards #741

Open
opened 2025-04-14 20:30:57 +00:00 by nex · 1 comment
Owner
No description provided.
nex added the
Bug
label 2025-04-14 20:30:57 +00:00
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
Jade added the
old/core-matrix
label 2025-04-14 21:03:37 +00:00
nex added the
Priority
Unknown
label 2025-04-15 00:24:05 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
2 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.