It's 2019.

We're now exactly halfway between y2k and the 32-bit Unix time overflow.

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

@Lumb @grufwub I like using this Wikipedia image to explain it to people:

Oh thanks now it all makes sense (it does not)

Oh wait no it does (for real) thanks ben lubar

@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 @eevee I would say that 32bit won't be used by then, but it will, and because Y2K nobody will care, then the world will truly end

@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 exactly half would be January 10th, 1:37:04, since overflow will occur on January 19th, 3:14:07 (all times in UTC)
Sign in to participate in the conversation

We are notbirdsite (aka not Twitter).

Largely dedicated to queer makers, whether you be a hardware/software developer, artist or writer. Strong emphasis on acceptance of LGBT identities, sex-work, body-positivity and anti-fascism (because oddly, in this day and age, it needs stating).

Though, as long as you abide by our rules, everyone is welcome!

We follow dzuk's list for instance-blocking:

For enquiries, please email: