2010 bug?

ISTR a thread about a supposed ‘2010 bug’, reminiscent of the ‘Y2K bug’, but I can’t find it.

I went to a blog, and the last post was at the end of December. It occurred to me that there may have been a glitch related to the new year. I emailed the blogger, and he said he’s been ‘locked out’ since the new year, and that others are experiencing the same problem. He has emailed the host (google), but has received no reply.

Question: Is there such a thing as a ‘2010 bug’, and could it be affecting google blog pages?

There are a few hits on Slashdot for problems relating to the 2010 turnover. Mainly just a few systems screwing up on binary-coded decimal. “10” in BCD would be mistakenly interpreted as a binary number, resulting in some software thinking it was the year 2016. Just goes to show that you can screw up anything if you just try hard enough. :slight_smile:

Our application has a 2010 issue with one section. The developers appear to have set the default extension for an archive file as (time-day-month).0(last digit of the year). Because it worked fine since they wrote it in 2002 (files being generated with .02, .03, etc extensions) we were caught by surprise when the system refused to generate files this January as either .10 or .010.

Old thread Y2010 bug thread: Have any Y2010 bugs been noted yet? - Factual Questions - Straight Dope Message Board

There’s also a bug that might crop up in a few places in January of 2038

Thanks, all.