home bbs files messages ]

Just a sample of the Echomail archive

Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.

   ASIAN_LINK      Not the kind that loves you long time      8,456 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 6,401 of 8,456   
   Maurice Kinal to Paul Quinn   
   Re TZUTC   
   04 Mar 19 16:52:39   
   
   MSGID: 2:280/464.113 5c7dc857   
   REPLY: 3:640/1384 5c7db1ac   
   TZUTC: -0800   
   RFC-3339: 2019-03-05 00:52:39.319544080+00:00   
   CHRS: UTF-8 4   
   LANG: en_CA.utf8   
   MøøSGID: 2:280/464.113 5c7dc857-130bdb10   
   Hey Paul!   
      
    PQ> Maurice mistakenly refuses to accept that Fidonet can and will   
    PQ> set its own standards   
      
   Wrong.  Maurice refuses to program obvious corrupt standards which is why the   
   TZUTC in this reply deploys the offset which honours the inclusion of the -   
   character for timezones west of prime meridian rather than drop the + from utc   
   (+0000) which the clock here is actually set to.  That way it doesn't cause   
   grief for any of the time based applications used on the system, such as   
   sorting based on datetime stamps.  Also it can be used to compensate for the   
   lame FTN datetime stamp by adding the REAL datetime stamp lovingly called   
   RFC-3339 (in nanoseconds) and can be used in a proper sort whereas your TZUTC   
   will cause a failure as demonstrated below;   
      
   -={ ':read !TZ=UTC date --rfc-3339=ns --date="05 Mar 19  09:13:00 1000"'   
   starts }=-   
   date: invalid date ‘05 Mar 19  09:13:00 1000’   
   -={ ':read !TZ=UTC date --date="05 Mar 19  09:13:00 1000"' ends }=-   
      
   Now had you put in a proper (correct) utc offset string then this will happen;   
      
   -={ ':read !TZ=UTC date --rfc-3339=ns --date="05 Mar 19  09:13:00 +1000"'   
   starts }=-   
   2019-03-04 23:13:00.000000000+00:00   
   -={ ':read !TZ=UTC date --rfc-3339=ns --date="05 Mar 19  09:13:00 +1000"'   
   ends }=-   
      
   The above can be compared to other msg's to determine their proper place in an   
   archive as opposed to the current, obviously lame FTN datetime stamp along   
   with it's corrupted utc offset.   
      
   BTW your FTN datetime stamp looks fudged.  ;-)   
      
   Life is good,   
   Maurice   
      
   ... A Møøse once bit my sister ...   
   --- GNU bash, version 5.0.2(1)-release (x86_64-pc-linux-gnu)   
    * Origin: Little Mikey's EuroPoint - Ladysmith BC, Canada (2:280/464.113)   
   SEEN-BY: 15/2 18/200 123/1970 154/10 203/0 221/0 226/17 229/107 426   
   SEEN-BY: 229/452 1014 240/5832 249/206 317 400 280/464 5003 310/31   
   SEEN-BY: 317/3 322/757 342/200 393/68 396/45 423/120 633/280 770/1   
   PATH: 280/464 229/426   
      

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca