#Year2038

Bebef ๐Ÿฆฆ๐Ÿ‡ช๐Ÿ‡บ๐Ÿดโ€โ˜ ๏ธ๐Ÿณ๏ธโ€๐ŸŒˆ๐Ÿณ๏ธโ€โšง๏ธ๐Ÿš™๐Ÿผ๐Ÿฅฆ๐Ÿšฉ๐ŸดBebef
2026-01-19

@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....

2026-01-19

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

Gato Negro :archlinux:crp@infosec.exchange
2026-01-14

Options...
1) By that date all computers, including your laptop, will be quantum.
2) I will either be dead or 78 years old, or I will be in a nursing home, asylum or mental hospital.
3) AI, wars, viruses, and stupidity will have exterminated humanity, leaving only human fossils on Mars and a computer that will continue sending useless data into space.

#y2k38 #y2038bug #Year2038

PurpleJillybeans :PrideDisk:PurpleJillybeans@kind.social
2026-01-08

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?

Unofficial LowEndBox BotLowEndBox@toot.earth
2026-01-03

Deep Lore: The Time Traveller Looking for a โ€œPortable Mainframeโ€ Who Freaked Out the Early Internet lowendbox.com/blog/john-titor- #internetfolklore #Editorial&News #CoasttoCoastAM #retrocomputing #timetravel #JohnTitor #Year2038 #ArtBell #IBM5100 #Y2038

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

2025-05-03

Are you worried about Y2K38 or the Year 2038 Problem?

#poll #y2k38 #year2038 #year2038problem #software

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

2024-05-30
GlitchyZorua :blobfoxcofe:GlitchyZorua@wetdry.world
2024-04-12
---------------------------
Windows Media Player
---------------------------
โš  Your computer is set to the year 2038, which will cause Windows Media Player to stop responding. Set your computer to the correct date and then try again.
---------------------------
OK   
---------------------------
2024-04-11

I desire #Year2038 Bug stickers.

2024-04-11

@damieng yep the #year2038 will be interesting

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

Luke T. Shumakerlukeshu@fosstodon.org
2024-02-26

Elsewhere in the source, there's a comment indicating that the #OpenPGP spec mandates timestamps be 32-bit numbers... #year2038

Luke T. Shumakerlukeshu@fosstodon.org
2024-02-26

#GnuPG trustdb file format updated to avoid the #year2038 problem when?

DebugPoint - Linux &Dev Portaldebugpoint@floss.social
2024-02-06

Beyond 2038: Debian Strengthens 32-Bit Builds with Critical Patches
debugpointnews.com/debian-time

#linux #opensource #debian #time_t #year2038

Debian
Rachael Ava ๐Ÿ’๐Ÿปโ€โ™€๏ธRachaelAva1024@tech.lgbt
2024-01-28

UNIX Time naming proposal? :blobfoxthink:

Little UNIX Time = 32-Bit UNIX Time
Big UNIX Time = 64-Bit UNIX Time

#UNIX #UNIXTime #UNIXTimestamp #2038Bug #Year2038

Today, I came across my first ever instance of the #year2038 problem in a real non-manufactured scenario.

It was running the `date` command on a Raspberry Pi, for anyone who might care.

This was to get the expiry date of a CA certificate that is expiring 15yrs from now.

Stuart Longland (VK4MSL)stuartl@longlandclan.id.au
2023-01-04

@onthisday โ€ฆ and soon, software written with a 32-bit signed `time_t` will overflow in 2038, which isn't that far off into the future. #year2038

Client Info

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