Date format in a JSON file

[Hypster]

Can anyone explain how to read this date format (i.e. to derive what day/month/year it is)?

"createdAt":1292246940

It's a timestamp inside a JSON file.

[XFool]

...It's 13 Dec 2010 01:29:00 PM

https://bytutorial.com/web-tools/timestamp-to-date-converter

If you need a routine to do this I'm sure further details are available online.

[pochisoldi]

Can anyone explain how to read this date format (i.e. to derive what day/month/year it is)?

"createdAt":1292246940

It's a timestamp inside a JSON file.

It's a Unix timestamp, the number of seconds since 1st Jan 1970.

[UncleEbenezer]

Lots of fun in January 2038, as the clock overflows on any remaining 32-bit representations of time. I wonder if the meeja will hype it as they did Y2K?

There may even be a legacy of code so badly written that the simple solution of recompiling on 64-bits (or more) is insufficient.

[servodude]

Lots of fun in January 2038, as the clock overflows on any remaining 32-bit representations of time. I wonder if the meeja will hype it as they did Y2K?

There may even be a legacy of code so badly written that the simple solution of recompiling on 64-bits (or more) is insufficient.

64 bits?
UTC is signed - change that and they can kick the can down the road for another 68 years

- sd

[Hypster]

Thank you for the answers, I really appreciate your help!

[UncleEbenezer]

Lots of fun in January 2038, as the clock overflows on any remaining 32-bit representations of time. I wonder if the meeja will hype it as they did Y2K?

There may even be a legacy of code so badly written that the simple solution of recompiling on 64-bits (or more) is insufficient.

64 bits?
UTC is signed - change that and they can kick the can down the road for another 68 years

- sd

Someone evidently thought 68 years would be ample.

I expect they were right, too. Around two thirds of the way through the 68 years, 64-bits became standard in pretty-much all general-purpose hardware (64 bits kicks the can down the road for many times the age of the universe). If they'd made it unsigned, the generation reaching crunch point in 2106 would have no memory of less-than-64-bit hardware.

How many today remember working with "far pointers"? Or even shaking our heads at those whose misfortune it was to have to? Even LFS support is becoming obsolete, except when you get the question about big files - usually in the context of archiving to a USB stick.

(post-hoc rationalisation can be fun ).