Skip to content

Conversation

@Hocuri
Copy link
Collaborator

@Hocuri Hocuri commented Nov 14, 2025

Fix #7435

The messages were already added in the way @adbenitez had proposed, but timestamps weren't calculated properly.

Not sure about the approach here - probably we should use calc_sort_timestamp() instead.

--------------------------------------------------------------------------------
Msg#2004: info (Contact#Contact#Info): Establishing guaranteed end-to-end encryption, please wait… [NOTICED][INFO]
Msg#2003: info (Contact#Contact#Info): Messages are end-to-end encrypted. [NOTICED][INFO]
Msg#2004: info (Contact#Contact#Info): Establishing guaranteed end-to-end encryption, please wait… [NOTICED][INFO]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this may regarded as weird.

first saying "Messages are e2ee" and then "establishing e2ee".

maybe the second one should read smth as "Establishing connection, please wait…" this also shorter

Copy link
Collaborator Author

@Hocuri Hocuri Nov 14, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree - and also, we don't really talk about "guaranteed end-to-end encryption" anymore, because all end-to-end encryption is guaranteed to last forever now

Edit: Actually, the wording in the UI previously was "Establishing end-to-end encryption, please wait...". Still, I think that "Establishing connection, please wait…" is better; one message talking about e2ee is enough

@Hocuri
Copy link
Collaborator Author

Hocuri commented Nov 14, 2025

Closing in favor of #7444

@Hocuri Hocuri closed this Nov 14, 2025
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.

odd order in initial system messages when secure-join is in progress

3 participants