Tomorrow the Unix timestamp will get to 1,666,666,666

Re:Tomorrow the Unix timestamp will get to 1,666,666,666 by tiagod on Monday October 24, 2022 @10:44AM (#33317338)

I went and checked 2000000000. It will happen on 2033-05-18T03:33:20.000Z (edited)

[ Parent | on HN ]

Re:Tomorrow the Unix timestamp will get to 1,666,666,666 by mzzter on Monday October 24, 2022 @10:50AM (#33317405)

Assuming 2000000000 is unix seconds, epochconverter.com converts it to Wednesday, May 18, 2033 3:33:20 AM GMT.

[ Parent | on HN ]

Re:Tomorrow the Unix timestamp will get to 1,666,666,666 by tiagod on Monday October 24, 2022 @10:55AM (#33317495)

My bad, thank you for the correction. I had converted it properly to 2033 but decided I wanted to switch to the format with ms. Ended up adding a zero in the process without checking the output (other than the .000 being there). Edited

[ Parent | on HN ]

Re:Tomorrow the Unix timestamp will get to 1,666,666,666 by hummusandsushi on Monday October 24, 2022 @10:53AM (#33317478)

i think you have an extraneous 0. It would not make sense for it to take a longer time to get from 1,000,000,000 to 2,000,000,000 than from the unix epoch to 1,000,000,000.

The time I think you meant to post is Wed May 18 2033 03:33:20 UTC+0000 (Greenwich Mean Time).

[ Parent | on HN ]

Re:Tomorrow the Unix timestamp will get to 1,666,666,666 by jtylr on Monday October 24, 2022 @10:51AM (#33317425)

I think you've added an extra 0 in there.

$ date -r 2000000000

Wed 18 May 2033 04:33:20 BST

$ date -r 20000000000

Tue 11 Oct 2603 12:33:20 BST

[ Parent | on HN ]

Re:Tomorrow the Unix timestamp will get to 1,666,666,666 by dis-sys on Monday October 24, 2022 @10:53AM (#33317472)

realizing that I would be long gone by 2603, your reply made me really sad. then I realized that your calculation is obviously wrong.

can I sue you for such such emotional distress?

[ Parent | on HN ]