Now this is quite telling. I have calendar appointments stored on plaxo with start dates outside of the 32bit unix representation of a date (i.e. before 1970. Gosh, what a surprise that I would have a recurring appointment that started before 1970, now who’s birthday could that be?).
It’s probably a limitation of the javascript underlying what they’re using. It seems to screw up birthday entries as well (off by one, for some reason?)
If it wasn't for carbon-14, I wouldn't date at all