@FediTips Ah, I just did expect/assume out-of-order given the federated nature.

For bigger delays, yes, it can be in such situations (and that may have been the case several times with @njsg@social.sdf.org), but I'll make a note to double-check if there's any reordering or not in this (web) client, I just want to be sure I'm not missing anything if some interface shows it by timestamp order

(To further explain, personally I'd really prefer if Mastodon, instead of endless scroll, had a concept of read and unread posts (the two aren't directly related but probably came in hand in the UI design choices?). More like a netnews client, less like Twitter; in lieu of that, I just assume (as in hope) newly received posts go at the top.

But I guess we're still fighting the 500 char limit from upstream... (not an issue on this instance, thankfully!))

@FediTips Do you know if there is any place where it's shown (or at least stored/served in the API) in order of arrival, as opposed to chronological order of post/boost timestamps? Or will e.g. Mastodon's web UI always reorder posts to keep timestamps in order?