MSGID: 2:221/1.58@fidonet 286d4048   
   REPLY: 2:280/464.113 6967d63f   
   PID: OpenXP/5.0.64 (Win32)   
   CHRS: ASCII 1   
   TZUTC: -0500   
   Hello Maurice Kinal!   
      
    >> That may mean that gcc developers are getting sloppy,   
      
    MK> No it doesn't.  Without overthinking this, it means that   
    MK> the binkd source isn't quite up to speed as far as c   
    MK> standards are concerned and that gcc provides backwards   
    MK> compatibilty via the -std switch.   
      
   Ah..  just a binkd thing.  OK.   
      
    > :read !date --rfc-3339=ns   
    MK> 2026-01-14 18:04:01.153826413+00:00   
      
    MK> Overkill for sure but the nanosecond part could be used to ensure   
    MK> uniqueness in a multiuser enviroment.   
      
   Yeah..  you love those nano seconds.   
      
   But wrt binkd does it matter? I mean.. isn't binkd the     
   connection component over the internet, and not for the FTN     
   messages?  Why would connection time need such granularity at     
   the time of the "call"?   
      
   --    
     ../|ug   
      
   --- OpenXP 5.0.64   
    * Origin:  (2:221/1.58)   
   SEEN-BY: 10/0 1 103/705 105/81 106/201 124/5016 128/187 129/14 153/757   
   SEEN-BY: 153/7715 154/10 30 110 203/0 214/22 218/0 1 601 700 840 860   
   SEEN-BY: 218/880 221/1 6 226/30 227/114 229/110 112 134 206 300 317   
   SEEN-BY: 229/400 426 428 470 664 700 705 240/1120 5832 263/1 266/512   
   SEEN-BY: 280/464 5003 291/111 292/8125 301/1 310/31 320/219 322/757   
   SEEN-BY: 341/66 234 342/200 396/45 423/81 460/58 633/280 712/848 770/1   
   SEEN-BY: 902/26 5020/400 5075/35   
   PATH: 221/1 280/464 103/705 218/700 229/426