client: avoid confusion from unordered timestamps

[xaur]

When I start a chat session and receive messages for me I see:

21:09 conversation started: <nick> <fingerprint>
19:17 first message received on <date>
19:17 <nick> <message>

I see the logic here: first a system message tells what happened at system time (convo started), then past messages with their original timestamps are printed.

But it feels weird because this is the first UI I see that shows not ascending timestamps.

How about:

21:09 (system time) conversation started: <nick> <fingerprint>

or

21:09 conversation started: <nick> <fingerprint>, below are original message times

or something like that.

[marcopeereboom]

I am inclined to close this because this should only be an issue if clocks are drifting. Is that not the case?

[xaur]

No, this is not about drifting clocks. It is normal operation but confusing UI.

In the example above, someone sent me two messages at 19:17, and I logged in on 21:09. The first line has a timestamp when "conversation started", i.e. when I opened the window at 21:09 and received the messages from the server. 2nd and 3rd lines contain timestamps of when the message was sent, at 19:17.