-=> Quoting Maurice Kinal to Nancy Backus on 03-Jan-2018 02:06 <=-
MK> I am taking the liberty of replying to this msg with all the others
MK> combined. This way we can filter out the bottles of beer ... until
MK> September 24th and later of course.
Sounds good to me...
MK> Then again maybe we need a new countdown for 2019-01-01?
I wouldn't mind a different countdown... like Henri, I don't drink
beer...
NB>> Seems to have worked fine
MK> Yes. Prior to the fix it claimed "2018-01-01 is 1 days from now
MK> and falls on a Monday." Dropping the 's' from '1 days' looks and
MK> sounds better methinks.
Quite agreed... :)
NB>> I can't tell any difference
MK> The difference was local. On the first one the fix was applied after
MK> I saved the msg whereas on the followup it was applied at creation so
MK> I saw '1 day' instead of '1 days' even though both ended up saying '1
MK> day' which is why you couldn't tell the difference.
Ah. At my end it was fixed for both messages, at your end the first
message needed fixing still... :)
MK> This Dec. 31, 2018 it should say '1 day' on both the local and
MK> distributed msg. Something good came out of my boredom.
A refinement to the program... :)
NB>> I see you kept the clock set for GMT
MK> Yes except let us call it Zulu Time instead. My localtime claims UTC
MK> which according to https://www.timeanddate.com/time/zones/z, "Zulu
MK> Time Zone (Z) has no offset from Coordinated Universal Time (UTC)", so
MK> there is verification to support the claim that my system clock is
MK> indeed deploying Zulu Time.
I can try to remember for next time.... ;)
NB>> But the countdown worked nicely
MK> And continues to as shown in the tagline below and is down 1 day from
MK> your msg that I am currently replying to. Also it automagically
MK> adjusted itself from 2017 to 2018 and changed from 'falls on a Monday'
MK> to 'falls on a Tuesday' which is accurate for both msg's when they
MK> were created.
So I noticed.... :) Nice job... :)
NB>> it came in my 31Dec packet
MK> Which was correct since it still was December 31st in Rochester which
MK> is behind 5 hours of Zulu Time.
Yup... I figured that out at arrival... clever to use Zulu time to
test out the correct workings of the program as it came to zero hour and
then went into the next countdown... ;)
MK>> -={ Mon Jan 1 21:00:00 EST 2018 }=-
MK> As advertised! Right down to the second too, including the Zulu Time
MK> in the header which would have said, "Tue Jan 1 02:00:00 UTC 2019" if
MK> it used the same format.
Wouldn't that have still been 2018 in the UTC header...?
MK> However Fidonet continues to use the obsolete datetime stamp despite the
MK> obvious shortcomings which were well known long before it officially
MK> became obsoleted. That was almost two decades ago. :::sigh:::
Offline wouldn't be updated in any case, unless one was using something
just put out.... Nothing wrong with using obsolete formats as long as
they are still understandable... ;)
NB>> It's pretty chilly here
MK> It is major news on this side of the fence. Ye olde Polar Vortex
MK> strikes again! I hear it will be hanging around for at least one more
MK> week according to the weather people. We're on the cold side here but
MK> nowhere near what youse out east are getting.
And it's worse farther east than we are.... and pretty bad at the moment
all along the east coast, down as far as Florida.... The last couple
days and today aren't all that bad, but next couple are going to be down
around 0 degrees F....
MK> They did get an ice storm in the Fraser Valley and some have been
MK> without power for four days now. That one fell as straight rain
MK> and some snow so we got lucky and dodged that particular bullet.
MK> :::knock on wood:::
How far from you is that....? Ice storms are not nice at all... Hope
you continue to dodge that bullet.... Did you get the snow...?
ttyl neb
... I'm just a peripheral visionary.
--- EzyBlueWave V3.00 01FB001F
* Origin: Tiny's BBS - http://www.tinysbbs.com (1:229/452)
|
