I see this happen alot for some reason. Old threads come back to haunt the living. Some people dont check timestamps and thus the thread thats 2 years old becomes necrod.
There must be a problem with the script running the timestamps.
It's a glitch on the internal clock of AG's servers, which, if I'm not mistaken, run Linux, a UNIX based OS. UNIX time began on January 1st, for one of the global meridians.
That's about December 31st at 7:00, as I've seen it before.
Of course, I could be wrong, but I'm fairly confident in my analysis.
Oh dear... the ghost in the machine is back. Good thing he's old For anyone who hasn't figured it out, it's a very common timestamp glitch, especially given that the coding for the forum was written from the ground up. Obviously there are going to be some minor imperfections when the entire code is unique.