#y2k38

5 posts · Last used 21d

Back to Timeline
openSUSE Linux @opensuse@fosstodon.org · Jul 24, 2026
#Y2K38 isn't a distant problem; #openSUSE developers have been finding real breakages by #testing with #2038 clocks. #GCC now has -Wtime_t-conversion warnings, and #Leap 16 ships 2038-safe by default. The #community is tackling this head-on. https://news.opensuse.org/2026/01/20/os-community-tackling-y2k38-epoch/
4
0
2
Simon Zerafa @simonzerafa@infosec.exchange · Jul 18, 2026
The Unix time for Sunday 19th July 2026, at 03:14:07 UTC is 1784430847, which will be 11 years and 6 months from the Y2K38 rollover 🙂 https://time.is/Unix_time #Y2K38 #UnixTime
0
0
0
Tommaso Gagliardoni @tomgag@infosec.exchange · Jul 28, 2025
This made me chuckle. #debian #humor #ipv6 #y2k38 #hackernews
621
1
312
BEOZ @beoz@det.social · Jul 12, 2026
Fast 20 Jahre Zeitsprung bei Telstra: ein starkes Indiz für ein GPS-Week-Number-Rollover bzw. ein Epoch-Problem. Das zeigt einmal mehr, welche realen Ausfälle Zeit-Rollover auslösen können – und warum Y2K38 ernst genommen werden muss. Guardian: https://www.theguardian.com/australia-news/2026/jul/10/2006-throwback-took-down-telstra-national-phone-networ Kenia: https://streamlinefeed.co.ke/news/gps-timing-glitch-sparks-telstra-network-collapse #GPS #Y2K38 #Zeitsynchronisation
0
0
0
Christian Gudrian @cgudrian@social.tchncs.de · Jun 27, 2026
Alle Geräte, die für das Jahr-2038-Problem anfällig sind, werden vorher vermutlich den Hitzetod sterben. Hat ja auch was. #Y2K38
0
0
0

You've seen all posts