TZUTC: 1100   
   MSGID: 50268.dove-syncdisc@12:1/2 2bcef974   
   REPLY: 53321.sync@1:103/705 2bcee472   
   PID: Synchronet 3.20a-Linux master/4bb08eded Dec 23 2024 GCC 10.2.1   
   TID: SBBSecho 3.23-Linux master/8888c0ff7 Dec 22 2024 GCC 12.2.0   
   COLS: 80   
   BBSID: ALTERANT   
   CHRS: CP437 2   
   NOTE: FSEditor.js v1.105   
     Re: Commit f9ad15e8 might need more work :)   
     By: Digital Man to deon on Sun Dec 22 2024 07:51 pm   
      
   Howdy,   
      
    > Weird that you've got 3 different time zones (PST, EST, and AEDT) going on   
    > between 2 systems.   
      
   Yup, it is very weird - but a scenario that a sysop could be in, if the have   
   to set the SBBS time seperately to the OS time.   
      
   So alterant OS is UTC+11:00, and scfg -> system -> local time zone is the same.   
      
   My test environment has the OS as PST (utc -8:00) and I had scfg -> system ->   
   local time zone EST (utc -5:00) - but, the "wall clock" is way off...   
      
   Anyway, when I set the test environment back to scfg -> system -> local time   
   zone back to PST (OS unchanged), then the displayed time string is OK.   
      
   TEST (UTC -8:00)   
   X-FTN-PID        Synchronet 3.20a-Linux master/4bb08eded Dec 23 2024 GCC 10.2.1   
   when_written     6764CE34 FE20 Fri Dec 20 12:53:56 2024 UTC-8:00   
   when_imported    6768E8E2 41E0 Mon Dec 23 15:36:50 2024 PST   
      
   ALTERANT (UTC +11:00)   
   X-FTN-TID        SBBSecho 3.23-Linux master/4bb08eded Dec 23 2024 GCC 10.2.1   
   when_written     0328CD78 FE20 Fri Dec 20 12:53:56 2024 UTC-8:00   
   when_imported    6768E8F8 9258 Mon Dec 23 15:37:12 2024 AEDT   
      
    > I'm not sure how you posted that message, but the hex value there (for   
    > when_written.time) is a time_t not the bit-field-endoded date that's used in   
    > commit 4bb08eded. So something's amiss.   
      
   I wasnt worried about the hex value for when_written_time being off (since I   
   dont trust it to be utc anymore), but rather the text of the date, it was off   
   by more than 3hrs (the difference between utc/pst). Interestingly it looks   
   like it is out by 19hrs which is the OS timezone difference between the two   
   systems.   
      
   (This timezone stuff is messy - but I get I'm probably a unique case, if I'm   
   the only one that ends up bringing it up. I'm sure most folks will end of up   
   with OS timezone = Sync timezone)   
      
   I posted that message with save_msg(), but I used   
   hdr.date = strftime("%a, %d %b %Y %H:%M:%S %z",this.__properties__.date)   
      
   (and __properties__.date is the File().date of a file where the contents are   
   in the message body (1734659870)).   
      
   > stat -c '%X' text/extra/100219b   
   1734659870   
      
      
   ...ëîåï   
      
   ---   
    þ Synchronet þ AnsiTEX bringing back videotex but with ANSI   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 103/705 105/81 106/201 124/5016 128/187 153/757 7715 154/10   
   SEEN-BY: 154/30 203/0 218/700 221/0 226/30 227/114 229/110 114 206   
   SEEN-BY: 229/317 400 426 428 470 550 700 705 240/1120 5832 266/512   
   SEEN-BY: 280/464 5003 5006 282/1038 291/111 292/8125 301/1 310/31   
   SEEN-BY: 320/219 322/757 341/66 234 342/200 396/45 423/120 460/58   
   SEEN-BY: 460/256 1124 467/888 633/280 712/848 770/1 902/26 5020/400   
   SEEN-BY: 5054/30 5075/35   
   PATH: 103/705 280/464 460/58 229/426