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
Originally posted by respektive May 28, 2022
On osu-web the direct messages are order by recent activity (newer DMs are at the top), while in lazer it's seemingly random.
Direct messages order on web:
vs. order in lazer:
This isn't really an issue when you only have a few DMs open like I do in the screenshots, but the more chats you open the harder it gets to keep track of which chats are actually relevant.
The text was updated successfully, but these errors were encountered:
channels are currently sorted differently by type (last message id for pm and alphabetically for the rest) so osu-web just sort them on the frontend when doing the grouping.
yeah, unless we're changing the order to be by last message id for all channel types.
even then it seems still easier to have sorting on frontend as new message comes in. it'd save the need to modify the channel array without it ending up just being a full on sort.
- Public channels (and announcements) are now alphabetically ordered.
- Private message channels are now ordered by most recent activity.
Closesppy#30835.
It should be, on initial load and when new messages come in.
We already have
last_message_id
inosu_chat.channels
, so it may be quite feasible to make this happen without too much stress.Of note, it should also be returned in this order by the API if possible.
Discussed in #18461
Originally posted by respektive May 28, 2022
On osu-web the direct messages are order by recent activity (newer DMs are at the top), while in lazer it's seemingly random.
Direct messages order on web:
vs. order in lazer:
This isn't really an issue when you only have a few DMs open like I do in the screenshots, but the more chats you open the harder it gets to keep track of which chats are actually relevant.
The text was updated successfully, but these errors were encountered: