HN Explorer

8 comments

[ 3.8 ms ] story [ 27.6 ms ] thread
Timothee
Does anyone know what the nature of the bug is? The article lacked on this aspect unfortunately.
ugh
None of the many German articles I read about the topic mentioned the exact nature of the bug.
ABrandt
My first guess would be that the software somehow recognized "2010" as "1910". Not sure exactly what dating structure would lead to this though.
aarongough
Perhaps they thought they would improve on the 2 digit method of representing years, and used a single digit method instead?

ie: 2009(9) -> 2010(0)

I would be pretty sad if it was a bug as obvious as this though. No idea what the real bug is likely to be...

sp332
I thought this was discussed earlier this week, but I can't find a link anywhere. The representation of the date is ambiguous about decimal/hexadecimal. So some devices are reading "10" as equal to 16, yielding the year 2016 instead of 2010.
please
as a workaround one can put a strip of tape over the chip, that way the magnetic strip on the other side gets used.
83457
The dreaded Y2.01K Bug
zb
Actually, Y2k01. Engineers don't use decimal points - it's too easy for them to disappear during copying.