TZUTC: 1100   
   MSGID: 50274.dove-syncdisc@12:1/2 2bcf579e   
   REPLY: 53325.sync@1:103/705 2bcf2dab   
   PID: Synchronet 3.20a-Linux master/4bb08eded Dec 23 2024 GCC 10.2.1   
   TID: SBBSecho 3.23-Linux master/a4f032b82 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 Mon Dec 23 2024 01:03 am   
      
   Howdy,   
      
    > 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).   
      
   I answered this in another message - I'm using save_msg() with hdr.date =   
   rfc822 date (it works, even with the timezone). That must not be using your   
   new format for when_written_time yet.   
      
   I figured out why the strftime was messing up (when I first started using   
   hdr.date to save messages that triggered this timezone discussion) - I had   
   logging on and noticed it changed after 1pm - I was using %I instead of %H   
   (which is what I always use, dont know where %I came from or why I used it).   
      
    > I'm confused about your time zone settings and systems, so I'm not really   
    > following.   
      
   OK, I'm sorry for messing you around, and thanks for looking at it. Looks like   
   I sent you on a red herring.   
      
   I run sbbs in docker, and I have 2 containers running sharing the same config   
   and dirs (one sees a different login.js/logon.js that launches my ansitex   
   shell on connection).   
      
   While I thought I had shutdown one container while posting these messages   
   about the date/times - I just discovered I hadnt - and it's OS was still   
   configured with UTC+11:00 (which explains where the aus date strings must have   
   coming from). Probably would have discovered it quicker if I had change scfg   
   -> System -> Local Time Zone to Auto after updating ;)   
      
   My other container (which is likely I wasnt connected to) was configured to   
   PST, and I was logging the console, so I saw the terminal server recycle when   
   playing with scfg (setting PST) and the logs when binkit was triggered sending   
   messages.   
      
   So, I killed everything, and started just the PST container, posted messages   
   and they are infact the correct time string - for both the when*time values.   
   When using save_msg() with hdr.date, it doesnt use your new when_written_time   
   encoding though.   
      
   When I changed the OS back to AEDT (and I'm now using the Auto Time zone -   
   winner :), the rendering of the message showed the wall clock time that you   
   were after, and rendered the correct "minutes ago" age message.   
      
   Sorry for the run around - On the upside, I understand sync's internals better   
   )   
      
      
   ...ëîåï   
      
   ---   
    þ 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