Over the years I've seen various news servers/providers do some strange things
but, after going back and checking the video cap you sent... I'm at a loss as to
what (exactly) your provider is doing in regards to setting "date AND time".
When file propagate from the master server (the one initially uploaded to) to
all the others that are constantly polling Usenet... they're "supposed" to
retain ALL info about the post... not just all the gobbledygook buried deep
inside (ie IP address and so forth) but also the date and time that the master
server received said headers. That date/time info is what "should" then show
on/in your particular news reader.
Here's where this gets interesting:
I begin my daily post/upload at precisely 4:30AM Pacific time. "Precisely"
because my queue is loaded the night before (then thoroughly double checked) and
set on a timer. The upload begins (and I've got a relatively fast pipe) at
4:30AM and runs until the entire queue has been uploaded AND receipt
acknowledged by a standard 240 code. For a post of 4-6 Albums in MP3 format
along with a gracious quantity of PARity files... this usually takes 10-20 min
(longer if large FLAC files are being posted, of course).
At 6:30AM (after making my second pot of coffee) I load/update all the groups
that I contribute to (whether I've posted to them on that day or not) and
immediately check that all my posts (regardless of the code 240) are in the
hands of GigaNews. I've yet to see a problem but my routine of double checking
is undertaken regardless.
As the *new* attached screen caps will show (this time I included the date/time
stamp in them... as I should have with the earlier caps). You'll notice that
said stamps reflect (give or take a minute) the start/finish times I indicated
(above).
However.... although the video cap you sent includes "date", you squished out
the "time".... there is a major (24hour) lag for propagation by your provider.
Each one of those albums that you are questioning were posted a full day apart
yet the date stamp (for a few headers) shown on your cap are way off. Almost as
if your provider dropped them and had to re-poll. But even that makes no sense
since all headers a "supposed" to retain initial/original date and time of
posting.
So... even though your news reader (from what I can see) is, in fact, set to
sort by date/time... the time stamp that your provider (or possibly your reader)
has attached to them causes you to see the headers way out of their "posted
order".
Yeah, I know... this is much to do over nothing but it bugs me when (with as
much time and care as I give to these posts) in this rare instance some server
is [apparently] screwing things up. Anyway... as my caps show... (a) all files
are there and (b) there are no dupes.
I've attached four (4) screen caps. 3 showing the date/time GigaNews received
them and 1 (a cap of your cap) showing the incorrect time stamps.
take care my friend.
|
|