Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Filtering: Limit on State Events do not work #1782

Closed
pik opened this issue Jan 8, 2017 · 2 comments
Closed

Filtering: Limit on State Events do not work #1782

pik opened this issue Jan 8, 2017 · 2 comments

Comments

@pik
Copy link
Contributor

pik commented Jan 8, 2017

For example the following filter will correctly apply "limit" : 0 to timeline but not to state.

{ "room": { "timeline" : { "limit" : 0 }, "state": { "limit": 0 }}

Since state is a graph-traversal it's not necessarily obvious how to add this functionality in a neat way (or if it is a sensible parameter to have). This is relevant for allowing low-bandwidth clients to render a Riot-Web interface (atm state event sets are not limited and /sync cannot complete). element-hq/element-web#2737

@ara4n
Copy link
Member

ara4n commented Aug 16, 2018

it's a feature that you can't limit or paginate state currently. i don't think the spec or anywhere else claims that you can.

@ara4n ara4n closed this as completed Aug 16, 2018
@turt2live
Copy link
Member

@ara4n https://matrix.org/docs/spec/client_server/unstable.html#post-matrix-client-r0-user-userid-filter says that state is a RoomEventFilter, which takes an optional limit parameter.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants