1. Forum
  2. Fidonet
  3. MYSTIC

  • echomail with future date due to timezone differences

    From Christian Sacks@2:250/5 to g00r00 on Mon Jan 23 17:47:13 2023
    Hey g00r00,

    Am I being dense here, or has there always been an issue with posts that have a future date due to being sent from someone on a bbs with a future timezone being unable to set as read until the date of the message is older than the current date in the bbses timezone I'm reading it on?

    Example;
    There's a post in here sent from a BBS in Australia (+11 hours from me) and the date of the message is 24th Jan 2023 09:47am
    Even though I've read it, it still shows as unread in the message list because my current date/time is 23rd Jan 2023 08:47pm.
    Once my local timezone says the date is 24th Jan 2023 09:48am, if I read the message again, now it will be marked as read.

    Has this always been an issue and I've just never paid it any attention, or is this something new?
    Would love to know either way just to settle my own peace of mind as to whether I've gone a bit broken in my mind or not.


    Cheers =)

    --- Mystic BBS v1.12 A48 2022/07/15 (Linux/64)
    * Origin: thE qUAntUm wOrmhOlE, rAmsgAtE, uK. bbs.erb.pw (2:250/5)
  • From g00r00@1:129/215 to Christian Sacks on Mon Jan 23 14:36:50 2023
    Am I being dense here, or has there always been an issue with posts that have a future date due to being sent from someone on a bbs with a future timezone being unable to set as read until the date of the message is older than the current date in the bbses timezone I'm reading it on?

    Is this in a message base or your mailbox?

    I think mailboxes list whatever is in it, regardless of if its read or not (by default anyway) but if its a public message base I'll set up a test and see if I can reproduce what you're saying.

    ... Isn’t it a bit unnerving that doctors call what they do "practice"?

    --- Mystic BBS v1.12 A49 2023/01/17 (Windows/64)
    * Origin: Sector 7 * Mystic WHQ (1:129/215)
  • From Christian Sacks@2:250/5 to g00r00 on Mon Jan 23 21:54:27 2023
    On 23 Jan 2023, g00r00 said the following...

    Am I being dense here, or has there always been an issue with posts t have a future date due to being sent from someone on a bbs with a fut timezone being unable to set as read until the date of the message is older than the current date in the bbses timezone I'm reading it on?

    Is this in a message base or your mailbox?

    I think mailboxes list whatever is in it, regardless of if its read or
    not (by default anyway) but if its a public message base I'll set up a test and see if I can reproduce what you're saying.


    It's in a public message base, however the message I was looking at earlier that exhibited this behaviour in, seems to now be read and I'm still in the 23rd Jan local time, so I wonder if it is less related to timezones now.

    I'll keep an eye on it and do some testing of my own and see if I can produce reliable results and let you know how I reproduce it. Starting to feel like it's just me being dense now :P

    --- Mystic BBS v1.12 A48 2022/07/15 (Linux/64)
    * Origin: thE qUAntUm wOrmhOlE, rAmsgAtE, uK. bbs.erb.pw (2:250/5)
  • From Paul Hayton@3:770/100 to Christian Sacks on Tue Jan 24 20:45:36 2023
    On 23 Jan 2023 at 05:47p, Christian Sacks pondered and said...

    Am I being dense here, or has there always been an issue with posts that have a future date due to being sent from someone on a bbs with a future timezone being unable to set as read until the date of the message is older than the current date in the bbses timezone I'm reading it on?

    the future says Hi :)

    Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

    --- Mystic BBS v1.12 A48 (Linux/64)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (3:770/100)