1. Forum
  2. FidoNet
  3. ASIAN LINK

  • life can only be understood backwards; but it must be lived forwards

    From Maurice Kinal@2:280/464.113 to Mark Time on Thu Jan 7 09:55:50 2021
    -={ 2021-01-07 01:55:51.546506030-08:00 }=-

    Hey Mark!

    How compatible is this? Note that I've returned to the system's datetime which is UTC - is there anything else? - and am using the topline to correct for PST8PDT which given the daylight savings time allows for the corruption of msgs. However, since it isn't officially anything, the msg corruption is limited to the two digit year DateTime stamp in the header. If you compare that with the topline DateTime you should be able to verify that the time portion of the faulty FTN DateTime stamp is indeed UTC despite there is no way to tell for sure without something to point out corruptable FTN standards ... or practices if you prefer.

    That being said the two digit year DateTime stamp really needs to die a horrible death.

    Life is good,
    Maurice

    ... Don't cry for me I have vi.
    --- GNU bash, version 5.1.4(1)-release (x86_64-motorshed-linux-gnu)
    * Origin: Little Mikey's EuroPoint - Ladysmith BC, Canada (2:280/464.113)
  • From Maurice Kinal@1:153/7001 to Maurice Kinal on Thu Jan 7 10:14:46 2021
    -={ 2021-01-07 10:14:47.070912539+00:00 }=-

    Hey Maurice!

    Note that I've returned to the system's datetime which is UTC
    - is there anything else?

    No. This node stuck with UTC and continues to do so including the corrected DateTime stamp which for the record is rfc-3339 compliant. The nanoseconds is a nice touch methinks and is definetly both forwards as well as backwards compatible depending on how far back backwards truly is.

    am using the topline to correct for PST8PDT which given the
    daylight savings time allows for the corruption of msgs.

    No such problem when both formats are UTC as demonstrated by this reply, although the FTN two digit year remains as corruptable as it always was and always will be.

    That being said the two digit year DateTime stamp really needs
    to die a horrible death.

    I couldn't have said that better myself.

    Life is good,
    Maurice

    ... Don't cry for me I have vi.
    --- GNU bash, version 5.1.4(1)-release (x86_64-motorshed-linux-gnu)
    * Origin: Little Mikey's Brain - Ladysmith BC, Canada (1:153/7001)
  • From Maurice Kinal@2:280/464.113 to Maurice Kinal on Thu Jan 7 10:44:30 2021
    -={ 2021-01-07 10:44:30.218212215+00:00 }=-

    Hey Maurice!

    daylight savings time allows for the corruption of msgs.

    No such problem when both formats are UTC as demonstrated by
    this reply

    Note that I am now following your lead. As far as I can tell it is the best way to eliminate all sources of potential corruption although as you point out the two digit year issues are still there despite all best intentions to correct the wrong. Near as I can tell it's demise is the only true fix.

    Life is good,
    Maurice

    ... Don't cry for me I have vi.
    --- GNU bash, version 5.1.4(1)-release (x86_64-motorshed-linux-gnu)
    * Origin: Little Mikey's EuroPoint - Ladysmith BC, Canada (2:280/464.113)