TZUTC: 1100   
   MSGID: 50263.dove-syncdisc@12:1/2 2bce6ec7   
   REPLY: 53308.sync@1:103/705 2bcd6a9d   
   PID: Synchronet 3.20a-Linux master/7b932f63e Dec  9 2023 GCC 10.2.1   
   TID: SBBSecho 3.23-Linux master/f9ad15e85 Dec 21 2024 GCC 12.2.0   
   COLS: 80   
   BBSID: ALTERANT   
   CHRS: CP437 2   
   NOTE: FSEditor.js v1.105   
     Re: JS Object save_msg()   
     By: Digital Man to deon on Sat Dec 21 2024 04:59 pm   
      
   Howdy,   
      
    > No, it doesn't. The JS when_written_time property is still a time_t   
    > representation - I do the conversion (encoding upon assignemnt, decoding   
    > upon use) to the SMB date storage automatically for you.   
      
   Actually I was refering to the post implementation of your changes to   
   when_written_time - from your commit example:   
      
   Here's an example from smbutil v of a message header posted after this change:   
     when_written     03292595 41E0 Fri Dec 20 18:22:21 2024 PST   
      
   0x03292595 (53028245) is the now new value of when_written_time right? and   
   time() will return a number like 1734898576, which will always be less.   
      
   But I think I get you, when I read a when_written_time, it'll convert back to   
   time_t value like time()?   
      
      
   ...ëîåï   
      
   ---   
    þ 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: 467/888 633/267 280 281 384 410 418 420 2744 712/848 770/1   
   SEEN-BY: 902/26 5020/400 5075/35   
   PATH: 103/705 280/464 633/280 229/426