General Discussion
Related: Editorials & Other Articles, Issue Forums, Alliance Forums, Region ForumsWhat's so farkin' special about Dec 1969?
And why do all the threads have this date?
WilliamPitt
(58,179 posts)Warren Stupidity
(48,181 posts)Cooley Hurd
(26,877 posts)Enrique
(27,461 posts)Biden is beating Ryan with a pool cue
dogknob
(2,431 posts)LiberalEsto
(22,845 posts)which is the Harvard Lampoon's hilarious parody of "Lord of the Rings".
By that time I'd read and re-read the original trilogy 6 or 7 times.
I laughed so hard I fell off my bed.
Art_from_Ark
(27,247 posts)I got some great Christmas gifts, and spent New Year's Eve drawing all sorts of amazing designs on my Spirograph, while the Christmas tree sparkled with tinsel, ornaments and colorful lights, and the TV did a wrap-up of the decade that was the '60s
hootinholler
(26,449 posts)All time stored in a computer is stored as milliseconds since the Epoch which is Dec 31 1969 23:59:59.99
When DU get's too busy, one of the processing things to be dropped is calculation of the time of post and the posts get stamped with a 0 for the time which gets interpreted as the Epoch.
Clear as mud?
muriel_volestrangler
(101,333 posts)and so when that 'zero time' is converted to an American time zone, it shows up as Dec 31st 1969. That form of timestamp is measured in seconds, not fractions such as milliseconds. And since it's a signed 32 bit integer, it overflows in 2038: http://en.wikipedia.org/wiki/Year_2038_problem - unless, that is, DU is running on a 64 bit machine with software that has been fixed for the problem (I really don't know how many programs have been fixed so far).
hootinholler
(26,449 posts)Too long in the Java world where it is measured in millisecs and the timezone sounds right also.