Ed BottDec 27, 2022
Our mistake was turning them back on.
Show threadNick KrichevskyDec 27, 2022
@edbott had these made up a couple years ago
Show threadSirWumpus 👾🍁Dec 28, 2022

@ollien @edbott
@ed1conf

ugh. What time zone? And none of that EDT EST PST PDT stuff. Offset from GMT or better yet, express it in Z. Date/time/zone rules are pain in the arse for software developers, best use one rule for them all : Zulu (btw cool Michael Caine film)

Show threaded(1) conferenceDec 28, 2022
@sirwumpus @ollien @edbott
A few minutes of 'shopping and here ya go:
Show threadSirWumpus 👾🍁Dec 28, 2022

@ed1conf @ollien @edbott

If I could get a gaming laptop that functions that long, I might actually defy my own death just to keep playing. (Won't pay for the extra warranty though.)

Show threaded(1) conference
@sirwumpus
My oldest still-functioning hardware is a 2001-era laptop (running OpenBSD 7.2), so I don't think I have anything sufficiently vintage to have experienced both time-hiccups.
Dec 28, 2022 at 2:21amWeb
Show threadSirWumpus 👾🍁Dec 28, 2022
@ed1conf I think any CP/M system would have the same issue since it used the same epoch as I recall. Any system from that era probably does- OS/2, AmigaOS, AtariST (TOS/GEM), FreeDOS, etc. In the name of compatible file transfers, archives, databases, etc. Not sure if simply enlarging timestamps from 32 to 64 bit will suffice backwards support.