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
Is your feature request related to a problem? Please describe.
Right now, scrolling up in a room which heavily uses threads is really slow and feels broken as most /messages results are not for the main timeline and instead are events from threads.
Describe the solution you'd like
/messages filter which lets the client paginate the main timeline where the responses only include events for that timeline
Describe alternatives you've considered
Making the server go faster so this is less painful but it is still quite wasteful of data and worst case could still result in many pages of content which cannot be rendered in that timeline.
The text was updated successfully, but these errors were encountered:
@clokep could you help me understand what work and which team would be needed here? Let's DM!
It looks like there's no open threads on the MSC. ✅
I don't think this MSC received review from any of the SCT yet. ❌
There's a Synapse implementation. ✅
The Synapse implementation seems to still match the MSC. ✅
There's no client implementation. ❌
@daniellekirkwood In summary, I think this is with a client team to implement in order to ensure it fixes a problem. I can enable it on an experimental server if needed.
Is your feature request related to a problem? Please describe.
Right now, scrolling up in a room which heavily uses threads is really slow and feels broken as most /messages results are not for the main timeline and instead are events from threads.
Describe the solution you'd like
/messages filter which lets the client paginate the main timeline where the responses only include events for that timeline
Describe alternatives you've considered
Making the server go faster so this is less painful but it is still quite wasteful of data and worst case could still result in many pages of content which cannot be rendered in that timeline.
The text was updated successfully, but these errors were encountered: