Although we didn’t make it into the final article, we appreciate being referenced in the sources. The article of @murielvalin on #Y2k38 is well worth reading:
https://www.epsiloon.com/tous-les-numeros/n57/le_bug_de_l_an_2038/
#Y2038 #y2038bug #DasJahr2038Problem #ScienceNews #journalismus
New utime32_t and utimeval32 types have been defined in the system headers in #OracleSolaris 11.4.90 for places where binary compatibility forces a 32-bit time value, but unsigned values can be used to represent times from 1970-2106 instead of the traditional signed 32-bit range of 1901-2038.
The bufmod(4m) interface was modified to use these, allowing snoop(8) to become #Y2038 safe (though still destined to fail in 2106). snoop also became a 64-bit program in this release.
Our recommendation for #fosdem
https://fosdem.org/2026/schedule/event/KTFEWJ-2038-rollover-open-source/
☝️"Pulling 32-bit time_t Asbestos out of the Open Source Ecosystem"
Say hello to @treyka if you’re there.
Attached: 1 image better safe than sorry #epochtime #remindme15years
RE: https://infosec.space/@CppGuy/115916876587154471
Indeed the #Y2038 problem was with us in 2008 in the case of 30-year mortgages.
In the early days of message boards and dial-up, a stranger showed up claiming to be a soldier from 2036—on a mission to retrieve an IBM 5100 “portable” computer. He didn’t just drop a prophecy and vanish. He argued, explained, posted technical details… and built one of the internet’s most enduring modern legends.
Alte Technik verschwindet nicht. Sie wird exportiert. Warum Y2K38 für Afrika schneller näher rückt – und was digitale Ungleichheit damit zu tun hat. #Y2K38 #Y2038 #DasJahr2038Problem
https://y2k38.ch/digitale-ungleichheit-y2k38-technologieexporte
BEOZ
Alan Coopersmith
Doktor Overcomma 
ѕенааѕ
Arthur David Olson
DACBARBOS Brand
Unofficial LowEndBox Bot