You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.
matrixbot
changed the title
Prune 'left' members of rooms in CS API? (SYN-487)
Prune 'left' members of rooms in CS API? (https://github.com/matrix-org/synapse/issues/1379)
Nov 7, 2016
matrixbot
changed the title
Prune 'left' members of rooms in CS API? (https://github.com/matrix-org/synapse/issues/1379)
Prune 'left' members of rooms in CS API? (SYN-487)
Nov 7, 2016
ara4n
changed the title
Prune 'left' members of rooms in CS API? (SYN-487)
Prune 'left' members of rooms in CS API from initial /sync? (SYN-487)
Dec 30, 2016
@erikjohnston can you remind me why we're not doing this? Is it because /messages may get confused if you try to back-paginate from an initial /sync, and members suddenly pop into life who weren't even mentioned in the initial /sync response?
Clients surely never care about users who are in state 'left' in a room. Can we not just prune them from the state that's passed to the client?
(Imported from https://matrix.org/jira/browse/SYN-487)
(Reported by @ara4n)
The text was updated successfully, but these errors were encountered: