TZUTC: -0800   
   MSGID: 53325.sync@1:103/705 2bcf2dab   
   REPLY: 50269.dove-syncdisc@12:1/2 2bcf1548   
   PID: Synchronet 3.20a-Linux master/8888c0ff7 Dec 22 2024 GCC 12.2.0   
   TID: SBBSecho 3.23-Linux master/8888c0ff7 Dec 22 2024 GCC 12.2.0   
   COLS: 80   
   BBSID: VERT   
   CHRS: CP437 2   
   NOTE: FSEditor.js v1.105   
     Re: Commit f9ad15e8 might need more work :)   
     By: deon to Digital Man on Mon Dec 23 2024 07:10 pm   
      
    >   Re: Commit f9ad15e8 might need more work :)   
    >   By: deon to Digital Man on Mon Dec 23 2024 05:11 pm   
    >   
    > Howdy,   
    >   
    >  >  > 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.   
    >   
    > Oh boy... So I just had another look at this:   
    >   
    > My test system (which is PST for OS and Sync):   
    >   
    > But to be sure, I just posted another message:   
    >   
    > X-FTN-PID        Synchronet 3.20a-Linux master/4bb08eded Dec 23 2024 GCC   
    > 10.2.1 when_written     6764CF1E FE20 Fri Dec 20 12:57:50 2024 UTC-8:00   
    > when_imported    6769155F 41E0 Mon Dec 23 18:46:39 2024 PST   
      
   How are you posting that message? When I post messages using the terminal   
   server or using smbutil to import a message, I'm seeing the bit-encoded date   
   values in hex (with the '0' initial nibble).   
      
    > A few things here:   
    >   
    > a) when_written   
    > The file that the date is based off of:   
    >   
    > root@ansitex-dev# stat -c '%x' text/extra/100219b   
    > 2024-12-19 17:57:50.286025007 -0800   
    >   
    > To confirm:   
    > root@ansitex-dev# jsexec -n tools/test-strftime   
    > File Date: 1734659870   
    > Thu, 19 Dec 2024 17:57:50 -0800   
    >   
    > And the contents of test-strftime.js   
    >   
    > var f = new File('text/extra/100219b');   
    > var fdate = f.date;   
    > writeln('File Date: '+fdate);   
    > writeln(strftime("%a, %d %b %Y %H:%M:%S %z",fdate));   
      
   time_t values don't have a time zone, so printing '%z' there isn't really   
   useful. It's just always going to print your system/OS time zone.   
      
    > So how is it getting when_written_time Fri Dec 20 12:57:50 2024?   
      
   I'm confused about your time zone settings and systems, so I'm not really   
   following.   
      
    > b) when_imported_time   
    > I dont set this value, so it is automatically calculated right?   
      
   Yes.   
      
    > root@ansitex-dev# date   
    > Sun Dec 22 23:48:39 PST 2024   
    >   
    > root@ansitex-dev# ls -al /etc/localtime   
    > lrwxrwxrwx 1 root root 39 Dec 22 18:06 /etc/localtime ->   
    > /usr/share/zoneinfo/America/Los_Angeles   
    >   
    > Startup:   
    > synchronet: term Compiled master/4bb08eded Dec 23 2024 10:39 with GCC 10.2.1   
    > synchronet: web  Synchronet Web Server Version 3.20a   
    > synchronet: web  Compiled master/4bb08eded Dec 23 2024 10:39 with GCC 10.2.1   
    > synchronet: term Initializing on Sun Dec 22 23:34:25 2024 with options: 2c02   
    > synchronet: web  Initializing on Sun Dec 22 23:34:25 2024 with options: 810   
    >   
    > Where is it getting Mon Dec 23 18:46:39 from ? (Which coincidently, the AU   
    > local time right now.)   
      
   Doesn't sound like a coincidence.   
      
   I'm going to play with jsexec posting of messages and see if I can reproduce   
   the time_t when_written storage like you're showing.   
   --    
                                               digital man (rob)   
      
   Sling Blade quote #10:   
   Morris: I stand on the hill, not for thrill, but for the breath of a fresh kill   
   Norco, CA WX: 52.3øF, 79.0% humidity, 1 mph ENE wind, 0.00 inches rain/24hrs   
   --- SBBSecho 3.23-Linux   
    * 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