As 30GB Zune owners deal with the sudden bricking of their systems after midnight this morning, hopefully they can take comfort in the fact they are not alone in this. Throughout the years, Apple products had their share of time & date problems.

In February 2000, Newton owners began reporting that they were having issues with the Newton being rather confused about what century it was in. Some users discovered that when they entered two-digit numbers as part of birthdays and other common abbreviated dates, things got wonky. For example, if I entered my birth date as 2-28-80 on the Newton, it interpreted the number as being February 28, 2080 rather than 1980. Entries of full dates in the 1900s were also affected. Other users stated that when they tried finding 20th century dates in the Find applet of the Newton, the system actually performed the search using 21st-century dates.

Fixes included resetting the system clock back to 1999 to enter those dates before resetting it again back to 2000 and applying software patches. Sadly, it's a bug that HAL-9000 forgot to mention. Apple even reported back in 1998 that the Newton was Y2K-compliant. Of course, this won't even begin to cover the problems that Newton owners still using the product will have in 2010. If you see our own Newton-sporting Steve Sande at Macworld, be sure to tease him about it.

A Tiger bug discovered in 2005 revealed that Safari's RSS reader would list some items as being an hour ahead of when they were actually posted -- news from the future is not catastrophic, but certainly could be confusing.

Our research this morning hasn't turned up any date-related iPod or iPhone hiccups, but if you know of any examples please let us know in the comments. As for the Zune bricks, there's been no word yet from Microsoft regarding the failures, but Engadget's readers have already come up with a number of theories including blaming it on Steve Jobs, the year 2008 being one-second longer, and other conspiracy theories that are sure to come throughout the day.

ComputerWorld reports that Timothy Smith, an iPhone owner in California, plans to sue Apple for violating antitrust law. His claim rests on the fact that Apple forces consumers to use AT&T as their sole wireless carrier and that the 1.1.1 update bricked phones that were unlocked for other carriers. This sole agreement with AT&T is, according to his suit, anticompetitive, forcing customers to pay more for their phones and for the cell phone service than they would in a competitive market. The suit goes on to add that Apple knew that the probable result of the update would brick unlocked iPhones.

If you're feeling in a litigious mood or if you just want to rubberneck to see what the fuss is about, check out this website set up by the Law Offices of Van Smith and Fernandez. It's got some spiffy photos at the top with a guy on a phone (it's probably not an iPhone) and a couple of lawyers talking (probably neither Van Smith or Fernandez).

Apple continues posting warning signs around their stores, cautioning customers that unlocked and modded iPhones fall outside their warranty. And at the same time, Apple Geniuses around the country quietly are reportedly accepting bricked iphones, slipping into the back and returning with functioning units.

We're not sure whether they're doing a low-level reflash or just swapping units out. We have reports of at least four customers who walked in with iBricks and walked out with iPhones. It is unclear at this time whether these customers unlocked their iPhones or not--we're also receiving reports of iBricks from people who never unlocked or modded their units.

Thanks to Ronald Ishak and "Martyn".

Update: Bolding added to existing text for clarity and emphasis.