🕒 12 χρόνια απομένουν για το Epochalypse – και τα 32-bit συστήματα είναι η "ωρολογιακή βόμβα" του 2038.

Στις 19 Ιανουαρίου 2038, στις 03:14:07 UTC, τα συστήματα που χρησιμοποιούν signed 32-bit time_t θα υπερχειλίσουν. Το αποτέλεσμα; Ημερομηνίες του 1901, σφάλματα σε πιστοποιητικά, καταρρεύσεις εφαρμογών – και σε κρίσιμες υποδομές, πιθανή κατάρρευση λειτουργιών.

Δείτε πλήρη ανάλυση 👉 https://opensource.uom.gr/index.php/epochalypse-provlima-y2k38/

#Y2K38 #Epochalypse #Year2038 #Linux #CyberSecurity #IoT #DevOps #UnixTime #Tech

Y2K38 kommt. Milliarden Systeme sind betroffen.

Open Source wird kritisiert – dabei entstehen die Lösungen oft genau dort.

Das Problem ist nicht der Code.
Das Problem ist, wie wir damit umgehen.

👉 Wer zahlt am Ende die Rechnung?

https://y2k38.ch/y2k38-open-source-suendenbock

#y2k38 #opensource #year2038 #y2038

@lerxst @david_chisnall

Next thing we know, age verification across time zones to implement Daylight Savings Age and Leap Age, 32 bit age with the #year2038 problem...

@yrrsinn 🎉Only 11.75 more years before we need to get hectic. 🤪🙈

Well, at least nobody has to walk from workstation to workstation with a stack of floppies.... #Year2038 #Y2k

Today it is 12 years till #Year2038 Problem, for all who celebrate #y2k38

So, I've been thinking about this for quite a long time now, and a recently-boosted toot reminded me of it:

What is the #RetroComputing world's plan for #Year2038?

I suppose the simplest approach would be to agree on a translation convention: year 1980 displayed = year 2040 IRL or something similar. Include a note stating the offset. Repeat every 60 years.

There might also be another, more radical option: use binary patching to change the epoch date. Could be feasible for common C libs?

Deep Lore: The Time Traveller Looking for a “Portable Mainframe” Who Freaked Out the Early Internet https://lowendbox.com/blog/john-titor-time-traveler-ibm-5100/ #internetfolklore #Editorial&News #CoasttoCoastAM #retrocomputing #timetravel #JohnTitor #Year2038 #ArtBell #IBM5100 #Y2038
Deep Lore: The Time Traveller Looking for a “Portable Mainframe” Who Freaked Out the Early Internet

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.

LowEndBox

Just run into a real-world example of the Year 2038 Problem - trying to store a Unix timestamp representing 2050-01-01 in an INT column (which is 32 bits).

#Year2038 #MySQL

Are you worried about Y2K38 or the Year 2038 Problem?

#poll #y2k38 #year2038 #year2038problem #software

Yes
0%
There's work to do, but it'll be fine
75%
No
25%
Don't know what that is
0%
Poll ended at .

Kinda annoyed that there wasn't even a spike in traffic on my website yesterday at 2025-04-16T19:07:44+00:00

https://www.epochalypse.today/

Was no one watching the bit flip to 01101000 00000000 00000000 00000000?

Anyway, see you guys at 2029-07-18T05:49:52+00:00 when it flips to 01110000 00000000 00000000 00000000, which is when we'll lose the next bit to the epochalypse.

#epochalypse #unix #unixtime #year2038 #year2038problem #y2k38 #software

How much time until the Epochalypse?

A countdown to the end of 32-bit unix time