I've never seen this before, where a bad Unix timestamp has resulted in a year prior to the base of 1970, usually it results in 2038 .. I can only presume something along the lines of local time is getting involved.

Lord knows how SE broke such an ancient bit of code, but I presume the recent patch is to blame.