[nos-bbs] date written to index - should we force it to local time zone ?

[Michael Fox (N6MEF)]

The index file is internal to JNOS and, therefore, I think anyone would say it is developer's discretion.  As long as the date/timezone in the actual message is not changed, I don't see a problem.

My $0.02,
Michael
N6MEF


> -----Original Message-----
> From: nos-bbs [mailto:nos-bbs-bounces at tapr.org] On Behalf Of Maiko
> Langelaar
> Sent: Saturday, November 14, 2015 6:04 PM
> To: TAPR xNOS Mailing List <nos-bbs at tapr.org>
> Subject: [nos-bbs] date written to index - should we force it to local
> time zone ?
> 
> 
> An interesting issue directly related to the issue of BBS forwarded
> messages
> having a different time zone than the local BBS, and causing possible
> expiry
> problems (if expire future is enabled).
> 
> Whenever a message comes in, JNOS updates the 'date' field in the index
> file
> to match the Date field of that message. The time zone unfortunately is
> not
> known in the index, it's a pure numeric field. So if an incoming message
> is
> 7 hours into the future, is there any reason why we need to set the 'date'
> in our local index file to that same 7 hours ? I hope I'm making sense.
> 
> So here is the question :
> 
>    Can anyone give me a reason why we should NOT force the 'date' in the
>    index file to be written using the local timezone of the JNOS system.
> 
> Maiko
> _______________________________________________
> nos-bbs mailing list
> nos-bbs at tapr.org
> http://www.tapr.org/mailman/listinfo/nos-bbs