-
Notifications
You must be signed in to change notification settings - Fork 357
feat(ui): Add the new latest_event room list sorter, and update the recency sorter
#5617
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
6f3f42f
feat(ui): Add the new `latest_event` sorter for the room list.
Hywan b4c63ee
feat(base): Implement `LatestEventValue::timestamp`.
Hywan d31db30
feat(ui): Update the `recency` sorter to include the `LatestEventValue`.
Hywan 124eaff
doc(ui): Fix a typo.
Hywan 76e776e
feat(ui): Use the new `latest_event` sorter in the room list.
Hywan c6f21fc
feat(base): Introduce the `RoomRecencyStamp` type.
Hywan 65ece3a
doc(base): Fix documentation of `recency_stamp`.
Hywan bfdcead
refactor(ui): Rename `*Matcher` to `*Sorter` in `room_list_service::s…
Hywan cffce01
chore(ui): Introduce the notion of _rank_ in the `recency` sorter.
Hywan 5a2c89f
refactor(ui): Remove intermediate structs.
Hywan d9db53e
refactor(ui): Remove intermediate structs.
Hywan File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We discussed this in chat but the discussion died down, so I'll repeat here.
To avoid malicious homeservers and users manipulating our room ordering using the
origin_server_tscan't we record a local timestamp whenever we create a newLatestEventValue?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah. I've been thinking about that.
When we receive an event via the sync, we can record the
now()as the local timestamp. However, it means that all events from all rooms for a particular sync will have the same local timestamp, and thus, we can't use that to sort the rooms (because all “recorded timestamps” will be equal).I think we have to keep
origin_server_tsfor the moment. We can warn it's a known limitations. It's also used to display the event's time in the timeline for example. If we can't trust this value, it's a protocol issue I suppose. I don't see how to solve that for the moment.