Date/time bugs throughout the years for Apple

Actually yes! All of the photos I took on December 28, 29, 30 and 31 were mistakenly labeled as December 28-31, 2009 by the iPhone. I found this out when I imported them into iPhoto and found them in the wrong order!

My iMac (20" LCD) loses time whenever it falls asleep, almost like the clock runs backwards. What's worse, is that even though it's checked in the prefs, it doesn't automatically re-sync with the 'Net time server unless I open prefs, uncheck and re-check it. Been through OS upgrades and all, and it still does it. Started doing it when I got it back from the Apple Store after the 2nd defective logic board.

Is it worth it to mention the Boot Camp 8 hour bug when switching back to OSX?

an ipod touch won't connect to youtube if the date and/or time are incorrect, but its just a matter of making sure the time on your computer is correct when it syncs

Don't forget that Apple just "forgot" about New Zealand changing daylight saving start/end dates in 2007. It was the same year, I believe, that the US changed, so it's not like it wasn't at the front of their minds!

http://www.geekzone.co.nz/forums.asp?ForumId=47&TopicId=16224

I remember having problems when I first got my 2G iPod nano. Formatting it with HFS, whilst in a country that did dates in the dd/mm/yy format (ie everywhere minus USA) would make the iTunes sync fail. The fix was to change your mac's location to USA, or format as FAT on windows.

I wouldn't expect it's a leap-second issue, as the zune wouldn't know about it.

More likely is the fact that this is the first leap year zune will have encountered.

Some pics I imported from my iPhone that were shot on 12/31/2007 came into iPhoto marked as 12/31/2008. Don't know if it was a problem with the phone (my suspicion) or iPhoto. Hey, I should shoot some today and see what happens!

I desperately wish people would get a handle on the term "bricked". Anything that is likely to become functional again, like the Zune, is not bricked. Bricked means that the device is no longer ever going to function, as in, it is now only useful as a brick.

if I had to make a wild guess, I'd say that there's a line of code that performs some calculation on the day of the year, with a check to make sure that value isn't over 365. Since today is day 366 of the year, that caused it to choke.