It's 2019.
We're now exactly halfway between y2k and the 32-bit Unix time overflow.
@ben
Oh thanks now it all makes sense (it does not)
@ben
Oh wait no it does (for real) thanks ben lubar
@grufwub 2spooky4me
@grufwub y2k38 is gonna be fun to explain to people who remember y2k but don't know how computers do math
@grufwub Not quite, that happens on January 10 at 1:37:04 UTC (assuming no leap seconds between then and now).
@fluffy i know just figured a pedantic status might not quite be as poignant (: also what's +-a number of days in the scheme of 68 years haha
@grufwub yeah mostly I'm surprised at how close to the beginning of the year the Y2K38 problem happens, for some reason I had it in my head it happens in September
@grufwub
"Time overflow" — got me thinking.
@grufwub
again a 2k year kinda bug
@grufwub the year just started can u not rn
@trashyfins i know I'm sorry 😆
@TheEnbyperor @eevee as someone on Twitter pointed out to me. There'll still probably be older machines running DOS/95/98 in places, or old mainframes using COBOL.
@grufwub
I don't know what any of those words mean but I assume this means my computer is gonna stop working at midnight so thanks for the heads up kim beans