Andrea Maria Piana c9994b5d0f Dont override last-clock-value on messages ... The denormalized-clock-value was erroneously set to the one of the last message received. This meant that on chats were the clock-value raced ahead of the timestamp (#status), a message from the mailserver or a message from someone with an old clock-value would basically make those messages be sorted in the past. The correct behavior is that last-clock-value for a given chat should be the maximum last clock value ever seen for that chat. Signed-off-by: Andrea Maria Piana <andrea.maria.piana@gmail.com>		2019-02-21 13:41:06 +01:00
..
cljsjs	update react-native and project dependencies	2017-12-15 16:06:13 +01:00
status_im	Dont override last-clock-value on messages	2019-02-21 13:41:06 +01:00