🚀 go-pugleaf

Jim Bean wrote:
> "Mike Easter"
>> snuhwolf wrote:
>> Date: Fri, 20 Mar 2009 16:16:47 -0700
>> NNTP-Posting-Date: Fri, 20 Mar 2009 22:17:01 +0000 (UTC)

>> Or, said a simpler way;  it appears that your clock is set an hour into
>> the future due to a wrong timezone offset -- perhaps due to something
>> misconfigured about the daylight time condition.

> Farkin idiot! Snuhwolf is posting from North America, so he's adjusted
> his clock for daylight savings time correctly. But based on the abuse
> address of "datemas.de", it's a safe assumption to say his newsserver
> is located in Germany. The thing you don't seem to grasp is that ONLY
> NORTH AMERICA HAS SET THEIR CLOCKS FORWARD FOR DAYLIGHT SAVINGS TIME,
> the entire rest of the world won't set their clocks ahead until next
> weekend .... so his newsservers time is ALSO correct.

You don't get it.  It doesn't matter whether a particular place on earth
is or is not observing daylight time in their localtime.  The entire
southern hemisphere handles daylight time completely differently than the
northern hemisphere, but that doesn't put the southern hemisphere in a
'timewarp' which causes them to be in some other time/space than the rest
of the world.

The fact is that we are all experiencing the same time at the same time,
and we can express that same time in UTC to resolve the confusion of what
time it is localtime or daylight time or not daylight time.

There is no problem with snuhwolf being in a different timezone than his
newsprovider, and there is no problem with snuhwolf being someplace in
North America that doesn't observe daylight time while surrounded by
others who do, but then the timezone offset should be configured
accordingly.

Or, said another way, if your timezone offset is -0700, then your clock
should be set to the appropriate localtime for the -0700 offset.  If your
timezone offset is something else, like -0600, then your clock should be
set to the appropriate localtime for the -0600 offset



-- 
Mike Easter