Hey Nancy!   
      
   I am taking the liberty of replying to this msg with all the others combined.    
   This way we can filter out the bottles of beer ... until September 24th and   
   later of course.  Then again maybe we need a new countdown for 2019-01-01?   
      
    NB> Seems to have worked fine   
      
   Yes.  Prior to the fix it claimed "2018-01-01 is    1 days from now and falls   
   on a Monday."  Dropping the 's' from '1 days' looks and sounds better methinks.   
      
    NB> I can't tell any difference   
      
   The difference was local.  On the first one the fix was applied after I saved   
   the msg whereas on the followup it was applied at creation so I saw '1 day'   
   instead of '1 days' even though both ended up saying '1 day' which is why you   
   couldn't tell the difference.  This Dec. 31, 2018 it should say '1 day' on   
   both the local and distributed msg.  Something good came out of my boredom.   
      
    NB> I see you kept the clock set for GMT   
      
   Yes except let us call it Zulu Time instead.  My localtime claims UTC which   
   according to https://www.timeanddate.com/time/zones/z, "Zulu Time Zone (Z) has   
   no offset from Coordinated Universal Time (UTC)", so there is verification to   
   support the claim that my system clock is indeed deploying Zulu Time.   
      
    NB> But the countdown worked nicely   
      
   And continues to as shown in the tagline below and is down 1 day from your msg   
   that I am currently replying to.  Also it automagically adjusted itself from   
   2017 to 2018 and changed from 'falls on a Monday' to 'falls on a Tuesday'   
   which is accurate for both msg's when they were created.   
      
    NB> it came in my 31Dec packet   
      
   Which was correct since it still was December 31st in Rochester which is   
   behind 5 hours of Zulu Time.   
      
    NB> And I note that this message is also dated in GMT   
      
   You of course meant to say Zulu Time.  ;-)  It will always be Zulu Time in the   
   headers.  I did use Rochester time in the body of the cybertoast msg.   
      
    MK>> -={ Mon Jan  1 21:00:00 EST 2018 }=-   
      
   As advertised!  Right down to the second too, including the Zulu Time in the   
   header which would have said, "Tue Jan  1 02:00:00 UTC 2019" if it used the   
   same format.  However Fidonet continues to use the obsolete datetime stamp   
   despite the obvious shortcomings which were well known long before it   
   officially became obsoleted.  That was almost two decades ago.  :::sigh:::   
      
    NB> It's pretty chilly here   
      
   It is major news on this side of the fence.  Ye olde Polar Vortex strikes   
   again!  I hear it will be hanging around for at least one more week according   
   to the weather people.  We're on the cold side here but nowhere near what   
   youse out east are getting.  They did get an ice storm in the Fraser Valley   
   and some have been without power for four days now.  That one fell as straight   
   rain and some snow so we got lucky and dodged that particular bullet.    
   :::knock on wood:::   
      
   Life is good,   
   Maurice   
      
   ... Future cybertoasts of note:   
       2019-01-01 is  363 days from now and falls on a Tuesday.   
       2024-11-05 is 2498 days from now and falls on a Tuesday.   
   --- GNU bash, version 4.4.12(1)-release (x86_64-silvermont-linux-gnu)   
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)