#Epochalypse

Michael :donor:hertg@infosec.exchange
2025-04-17

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

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

iokevinsiokevins
2025-04-16
Kay :heart_bi: :tinoflag:Kay@mastodon.nz
2025-03-24

US News: White House Shifting Cyber Risk to State and Local Agencies
Executive Order Shifts Cyber Responsibilities to States, Sparking Security Concerns

This could be a good time to be a #cybersecurity / #infosec expert in the USA. Or an appalling time. I guess it depends on how comfortable they are at coping with risk and uncertainty and potential disasters.

Also time to start prepping for Year2038 aka #Epochalypse (when Unix systems reach time end). 💻 ⌛
bankinfosecurity.com/white-hou

2025-02-23

Soviel zum Thema im Jahr 2038 gibt es keine Legacy Systeme mehr 😂 #y2k38 #Epochalypse
Windows XP und 8-Zoll-Disketten steuern Atomwaffen und Kriegsschiffe - PC-WELT
pcwelt.de/article/2571917/wind

2025-01-12

REMEMBER 2038-01-19!

I made a new batch of #y2k38 stickers. Slightly different design this time.
If you are around at #fosdem2025, I'll drop some there.

SVG: sink.deebas.com/2038-sticker.s
License: CC BY-NC-SA 4.0

#epochalypse #sticker

A hand holding a sticker dispensers.
One sticker is visible. It's yellow/black/white. In the lower right corner is a stylized 32bit microchip. The text reads:

REMEMBER
Turn your computer off before 03:14:07 UTC on 2038-01-19.

@henry Maybe because they are "AI Resistant" and survived the AI Apocalypse in 2037, and had no RTC, so also survived the #Epochalypse in Jan 2038 (tomsguide.com/us/2038-bug-bh20)

😜

Thorsten Leemhuis (acct. 1/4)kernellogger@fosstodon.org
2024-06-10
Thorsten Leemhuis (acct. 1/4)kernellogger@fosstodon.org
2024-06-07

Enjoy it while it lasts, as soon we will have made 80 percent of the way to #epochalypse[1]: botsin.space/@countdownY2K38/1

[1] en.wikipedia.org/wiki/Year_203

#Y2038 #Y2K38

Freddie Weaselshitweaselshit
2024-04-21

How come we've successfully dealt with Y2K problem, but struggle with leap seconds and even daylight saving every time?

Can't wait for the in 2038. Nice to imagine being pulled out of a retirement at a remote cabin to deal with it 90s action movies style.

2024-03-09

Die #unixzeit hat einen runden Geburtstag 🎉 Es sind jetzt genau 1710000000 (1.71 Mia) Sekunden seit dem Urknall (The #epoch) am 01.01.1970. Wir haben noch gut 437 Mio. Sekunden bis zur #Epochalypse , geniessen wir es!

#y2k38 #Unix #unixtime

WinFuture.deWinFuture
2024-03-06

Bei X hat ein Nutzer an das Problem erinnert, dass -Systeme im Jahr 2038 treffen könnte. Es handelt sich dabei um den "Nachfolger" des Jahr-2000-Problems: winfuture.de/news,141592.html?

2024-03-03

TIL about the #year2038 #2038Problem "Many systems use a 32-bit integer to store the Unix time - the number of seconds since 1 January 1970, known as the Unix epoch. On 10 January 10 2038 at 03:14:07 UTC this count will exceed the maximum value a 32-bit integer can hold, causing an overflow." 👀 :goose_hacker:
en.wikipedia.org/wiki/Year_203
#Y2038 #Y2K38 #Y2K38 #epochalypse

2024-02-29

@basti Zeit als Endgegner 😁 Genau auf den Punkt gebracht! Gefällt mir. #y2k38 #Epochalypse

Der Fahrplan wurde wohl in Excel berechnet 😉

det.social/@beoz/1120118262673

George Bailygeorgebaily
2024-02-11

From the wiki page on
>The ext4 filesystem, when used with inode sizes larger than 128 bytes, has an extra 32-bit field per timestamp, of which 30 bits are used for the nanoseconds part of the timestamp, and the other 2 bits are used to extend the timestamp range to the year 2446.
en.wikipedia.org/wiki/Year_203

ByREVbyrev
2024-01-30

Y2K38 superbug or the Epochalypse, when 32-bit time_t expires, and all old hardware is forced out of service.

monkee :scawyduck:mp@fedi.monkee.ch
2024-01-19
Thorsten Leemhuis (acct. 4/4)thleemhuisfoss@social.tchncs.de
2024-01-19

@isotopp

Falls jemand gelegentlich hier an das #Y2K38-Problem (aka #y2038 #epochalypse) erinnert werden will, folgt @countdownY2K38

2024-01-19

We are now 14 years away from software storing UNIX time as signed 32-bit integers overflowing and taking us back to 1901. Hopefully your software has been upgraded to store UNIX time in 64-bit integers!

en.wikipedia.org/wiki/Year_203

#Y2038 #Year2038Problem #Epochalypse #UNIXtime

Marcel Waldvogelmarcel@waldvogel.family
2024-01-19

Zum Glück ist noch Zeit. Wir könnten Hersteller und Importeure dazu verpflichten, ihre Geräte auch bei ins Jahr 2038 vorgestellter Zeit auszuprobieren.

Das wäre der Idealfall. Ob es soweit kommt, hängt am politischen Willen. Der typischerweise mehrjährige Gesetzgebungsprozess müsste jetzt gestartet werden, damit die in den nächsten Jahren gekauften Geräte auch 10 Jahre halten.

Wir haben aber auch Tipps zur Selbsthilfe auf Lager.
#Y2K38 #2038 #2038Bug #Epochalypse
dnip.ch/2024/01/19/y2k38-timed

Client Info

Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst