Skip to content

fix: do not sort received messages below the last seen one#8031

Draft
link2xt wants to merge 3 commits intomainfrom
link2xt/no-sort-below-last-seen
Draft

fix: do not sort received messages below the last seen one#8031
link2xt wants to merge 3 commits intomainfrom
link2xt/no-sort-below-last-seen

Conversation

@link2xt
Copy link
Collaborator

@link2xt link2xt commented Mar 25, 2026

  • There is a problem with "Messages are end-to-end encrypted." message. It has current timestamp, but incoming message from contact requests is from the past, so contact request chats start with the incoming message followed by "Messages are end-to-end encrypted.". Need to set the timestamp for the info message to the timestamp of incoming message or fix it the other way.

Fixes #8030

@link2xt link2xt force-pushed the link2xt/no-sort-below-last-seen branch from 61fde0e to eb93663 Compare March 25, 2026 05:10
@link2xt link2xt force-pushed the link2xt/no-sort-below-last-seen branch 2 times, most recently from 5e13d10 to c2b81ac Compare March 25, 2026 07:09
link2xt added 3 commits March 26, 2026 06:08
We know which message was added from the return value
of receive_imf(). It may be that the first chat
in the chatlist is not the one where the message was received
if there is a pinned chat or if
just received message is old.
@link2xt link2xt force-pushed the link2xt/no-sort-below-last-seen branch from c2b81ac to 7180af5 Compare March 26, 2026 05:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Message reordering with multi-relay

1 participant