Subj : JS Object save_msg()
To   : Digital Man
From : deon
Date : Wed Dec 18 2024 12:26:14

  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)

.