Landscape was being quiet, so I remarked on how silent it was. The message posted with the right time stamp, and then a whole bunch of messages with earlier time stamps scrolled up.
Just like a dot post issue, I think.
I somewhat think this is because ~dopzod was a little uncommunicative at the time, but unsure. We are still in the throes of Sudden Death.

Still getting the out of sequence thing. Weird.
Huh I thought I commented on this already. Here's a quick rundown of out of order causes:
Perhaps the UI should re-order messages based on their timestamps, but then you get into situations where messages can get inserted way back in scrollback and nobody will ever see them. I feel the current behavior is more or less correct.
We did have the "reorder on client" behavior before and I think it led to
people having messages that "disappeared" becuase they were inserted out of
the scroll window.
A
—
~poldec-tonteg
http://urbit.org
On Fri, Aug 16, 2019 at 1:57 PM Fang notifications@github.com wrote:
Huh I thought I commented on this already. Here's a quick rundown of out
of order causes:
- Timestamps are set by the sender on-compose, so:
- Sender's clock could be ahead/behind
- Sender's message could've taken a while to send
- Sender could've spoofed the timestamp, I guess (^:
- Messages could've actually been delivered out of order, as per
#1482 https://github.com/urbit/urbit/issues/1482Perhaps the UI should re-order messages based on their timestamps, but
then you get into situations where messages can get inserted way back in
scrollback and nobody will ever see them. I feel the current behavior is
more or less correct.—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/urbit/urbit/issues/1410?email_source=notifications&email_token=AAMJBYZ77FI7BEBAGINXQJTQE4ICVA5CNFSM4IISHYY2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4PVYEY#issuecomment-522148883,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAMJBY2EIZCXFKPQFZTQ47DQE4ICVANCNFSM4IISHYYQ
.
Closing this as nu-chat hasn't displayed this behavior so far.