[M T]

Because engineers had to pick a t=0.

https://kb.narrative.io/what-is-unix-time

I think we switched software some years ago, and when we did so, everyone who was ported over was set to a start date of 1970.


BC

or 

Registration Date: Wednesday, December 31st, 1969, 05:33 pm

Yes, the bogus dates aren't quite Unix time zero. I noticed that at the time but didn't look into where the conversation script went wrong. I don't think it was the most recent software change but the one before that, and I don't think I was an admin yet.

Unix time zero would be 12/31/69 4PM PST.  So the value there (5:33PM) is about 5550 to 5639 (taking into account possible rounding or truncation).  Nothing jumps out at me.  (I thought maybe it was going to be  ASCII characters interpreted as a number.)

[M T]

Because engineers had to pick a t=0.

https://kb.narrative.io/what-is-unix-time

I think we switched software some years ago, and when we did so, everyone who was ported over was set to a start date of 1970.


BC

or 

Registration Date: Wednesday, December 31st, 1969, 05:33 pm

Yes, the bogus dates aren't quite Unix time zero. I noticed that at the time but didn't look into where the conversation script went wrong. I don't think it was the most recent software change but the one before that, and I don't think I was an admin yet.

Unix time zero would be 12/31/69 4PM PST.  So the value there (5:33PM) is about 5550 to 5639 (taking into account possible rounding or truncation).  Nothing jumps out at me.  (I thought maybe it was going to be  ASCII characters interpreted as a number.)