Yeah, it's deeply annoying that the behavior has to be inconsistent between comms and personal journals, but timestamps/chronological display is actually one of those computing problems that look deceptively easy when you first think about it and then turns out to actually be a vast, incomprehensible eldritch horror lurking in the depths to devour programmers' sanity when you dig into it a bit more. (If you want to read up on 'why' a little bit, the best explanation that gets into just the basics in an accessible way is "UTC Is Enough For Everyone, Right?" and spoiler alert: the answer is 'no, no it is not'. And that's just the overview.) There is a very, very good reason why we don't try to translate the timestamps of posts into the viewer's time zone, let's just say. (Timestamps on comments we can kind of do. Timestamps on posts: absolutely not, and I cry just thinking about it.)

Like I said, you can at least change the date/time on community entries so they sort properly in the archives! But yeah, the fact community posts can come from anywhere in the world in a rapid back-and-forth means that we have to treat them differently, timestamp-and-sorting wise, than we do entries in personal journals.

Accurately displaying "when a thing happened" is one of the hardest problems in computer science by far and it's not even close. It's not even much of a technical issue so much as the way we try to shoehorn the passing of linear time into a coherent description/identification system really is that messed up.