That is indeed Very Weird on first glance, but I did some quick spot-checking of a few of the entries that are dated 2015, and I think I've figured it out! It turns out that all of the ones I checked are entries that were actually posted to Dreamwidth today. (I'm guessing that the owners manually imported from LJ using copy/paste, instead of using our on-site import tool: entries that are imported through our import tool don't appear on reading pages, to prevent someone from importing a huge journal and flooding your reading page completely.) In each case, the poster manually adjusted the time on the timestamp to be from 2015 while they were writing the entry, so that the entries sorted themselves into the right place in their archives: the contents of a journal show on the recent entries/archive/etc pages based on the user-supplied time, so you can belatedly write that review of the awesome concert you went to in 2001 (and just found your notes for) and it will happily fit itself in along the rest of your entries from 2001.
However! Because timezones are a thing, and trying to convert a user-supplied time into a time that can be manipulated to account for varying timezones is the sort of problem that looks easy and is actually hard enough that it often makes experienced programmers weep wretchedly into their keyboards, and if we did it the other way a misconfigured computer clock could mean nobody would ever see that entry you just posted, the reading page (as opposed to the recent entries/archive/year/month/day/etc pages) is ordered by "what time did our servers receive this post", not "what time did the user put on the timestamp": we completely ignore the timestamp and just go by the actual order in which they got to us. So, if I write that belated review of that Moxy Früvous show I went to in 2001 and forgot to document, it will show in my journal in between the other reviews of the other Moxy Früvous shows I went to in 2001 (I, uh, went to a lot of Moxy Früvous shows in 1999-2001), but you'll see it on your reading page in between things the other people you're subscribed to have posted that are dated 10 April 2017.
Does that explanation make enough sense to you? (I've been awake and working way too long today; I'm losing the ability to tell if I'm writing coherently!) In essence, it is a glitch related to the mass migration and will fix itself, in that people who are manually importing and changing the dates on their entries will get all of everything over here sooner or later.
no subject
However! Because timezones are a thing, and trying to convert a user-supplied time into a time that can be manipulated to account for varying timezones is the sort of problem that looks easy and is actually hard enough that it often makes experienced programmers weep wretchedly into their keyboards, and if we did it the other way a misconfigured computer clock could mean nobody would ever see that entry you just posted, the reading page (as opposed to the recent entries/archive/year/month/day/etc pages) is ordered by "what time did our servers receive this post", not "what time did the user put on the timestamp": we completely ignore the timestamp and just go by the actual order in which they got to us. So, if I write that belated review of that Moxy Früvous show I went to in 2001 and forgot to document, it will show in my journal in between the other reviews of the other Moxy Früvous shows I went to in 2001 (I, uh, went to a lot of Moxy Früvous shows in 1999-2001), but you'll see it on your reading page in between things the other people you're subscribed to have posted that are dated 10 April 2017.
Does that explanation make enough sense to you? (I've been awake and working way too long today; I'm losing the ability to tell if I'm writing coherently!) In essence, it is a glitch related to the mass migration and will fix itself, in that people who are manually importing and changing the dates on their entries will get all of everything over here sooner or later.