Bug 187561

Summary: Natural message order in History
Product: [Unmaintained] kopete Reporter: Alexey Chernov <4ernov>
Component: History PluginAssignee: Kopete Developers <kopete-bugs-null>
Status: RESOLVED UNMAINTAINED    
Severity: wishlist    
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Alexey Chernov 2009-03-19 01:36:32 UTC 
Version:            (using KDE 4.2.1)
Compiler:          GCC 4.3.2 Target: x86_64-unknown-linux-gnu Configured with:  ../gcc-4.3.2/configure --prefix=/usr --libexecdir=/usr/lib --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu --enable-languages=c,c++,fortran,objc,treelang --disable-multilib --enable-c99 --enable-long-long Thread model: posix
OS:                Linux
Installed from:    Compiled From Sources

I think it should be better not to sort messages in History by time, because if users have not synchronized clock (very often case) the history become almost unusable, answers go before questions :) It's better to write them in the order they appeared in the chat window, for example, to sort all the messages by the local side's time (now remote answers are obviously have remote side's time).
Comment 1 Christoph Cullmann 2024-09-18 18:28:21 UTC 
Dear user, unfortunately Kopete is no longer maintained.

Please migrate to another solution, e.g. for Jabber a possibility is Kaidan, for Matrix a candidate is NeoChat.