The Epochalypse: It’s Y2K, But 38 Years Later https://hackaday.com/2025/07/22/the-epochalypse-y2k-but-38-years-later/ #HackadayColumns #year2038problem #computerhacks #2038problem #epochtime #timestamp #unixtime #epoch #unix

The Epochalypse: It’s Y2K, But 38 Years Later - Picture this: it’s January 19th, 2038, at exactly 03:14:07 UTC. Somewhere in a dat... - https://hackaday.com/2025/07/22/the-epochalypse-y2k-but-38-years-later/ #hackadaycolumns #year2038problem #computerhacks #2038problem #epochtime #timestamp #unixtime #epoch #unix

This morning I spent some time debugging an app which logs as if it's AD 57203, to wit

{"level":20,"time":1742987150412,"pid":1, ...

$ date -r 1742987150412
Fri Jan 24 10:20:12 CET 57203

but it turns out the other instance (the one that works, as in the user is able to download files from there) has roughly the same time internally, so *that* was not its main problem.

Mind boggled, debugging to continue until *something* improves.

Learn handy commands to help you understand epoch time in #Linux https://www.admin-magazine.com/News/Understanding-Epoch-Time-in-Linux #Unix #CommandLine #EpochTime #EpochFormat #OpenSource

better safe than sorry
#epochtime #remindme15years

ISO 8601: Ending the Date Wars and Confusing Everyone Equally - There’s a document I had to sign to wrap up a community responsibility in rural Ox... - https://hackaday.com/2021/04/21/iso-8601-ending-the-date-wars-and-confusing-everyone-equally/ #originalart #decimaltime #clockhacks #epochtime #featured #interest #iso-8601 #rants