home bbs files messages ]

Just a sample of the Echomail archive

Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.

   SYNCHRONET      Rob Swindell fetishistic worship forum      43,341 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 40,848 of 43,341   
   deon to Digital Man   
   JS Object save_msg()   
   18 Dec 24 12:26:14   
   
   TZUTC: 1100   
   MSGID: 50202.dove-syncdisc@12:1/2 2bc81ed0   
   REPLY: 53250.sync@1:103/705 2bc7daae   
   PID: Synchronet 3.20a-Linux master/7b932f63e Dec  9 2023 GCC 10.2.1   
   TID: SBBSecho 3.23-Linux master/bbf9d5eac Dec 14 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 Tue Dec 17 2024 11:44 am   
      
   Howdy,   
      
    > The JS strftime() function is just a wrapper for the C run-time library   
    > function of the same name. So depending on your OS, you can either run "man   
    > strftime" or see   
    > https://learn.microsoft.com/en-us/cpp/c-runtime-library/refere   
    > nce/strftime-wcsftime-strftime-l-wcsftime-l to read more up on how   
    > strftime() works for your platform.   
      
   Yeah, i know strftime().   
      
   OK, I'm convinced there is something messed up with time recording. So I'll   
   start with one piece at a time.   
      
   I'm storing messages with save_msg(), and I am *not* setting date,   
   when_imported* or when_written*.   
      
   According to the OS, the time is:   
   > root@ansitex-dev:/opt/sbbs/mods/ansitex# date   
   > Wed Dec 18 12:08:51 AEDT 2024   
      
   The message saved is record with this:   
   when_written     6762209C 0000 Wed Dec 18 12:08:44 2024 UTC   
   when_imported    6762209C 0000 Wed Dec 18 12:08:44 2024 UTC   
      
   This is not correct. The time was recorded as "UTC" when it should have been   
   converted to UTC or recorded as +11:00. And if it cant figure out the   
   timezone, then it shouldnt imply UTC.   
      
   This results Sync showing the message as "11 hrs from now".   
      
   Why isnt timezone information being used when storing the current time? (It   
   would seem apparent that Sync knows the time zone to display the statement   
   "hrs from now")   
      
   I think it would be better to fail the call to save_msg than second guess   
   wrong information.   
      
      
   ...лоеп   
      
   ---   
    ю Synchronet ю AnsiTEX bringing back videotex but with ANSI   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 10/0 1 102/401 103/1 17 705 105/81 106/201 124/5016 128/187   
   SEEN-BY: 153/7715 218/0 1 215 601 700 840 860 880 226/30 227/114 229/110   
   SEEN-BY: 229/114 206 317 400 426 428 550 700 705 266/512 280/464 282/1038   
   SEEN-BY: 291/111 301/1 320/219 322/757 342/200 396/45 460/58 633/280   
   SEEN-BY: 712/848 902/26 5075/35   
   PATH: 103/705 218/700 229/426   
      

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca