The Epochalypse Project

Post by AndrewKemendo » Sun, May 11, 2025, 12:46 PM UTC

Waterluvian wrote: post #9

I think this effort would benefit from trying to qualify what “unpredictable ways” actually means. If anyone is testing devices, a catalog of test results describing the actual failure modes that were revealed would help make this whole thing more concrete. I think many software engineers know that if you want to make any organization care about this type of issue, you need to be ready to demonstrate the severity and…

Post by jbeninger » Sun, May 11, 2025, 12:59 PM UTC

bongodongobob wrote: post #20

jbeninger wrote: post #15

Earlier quoted context omitted.

Demonstrate? Or just scaremonger? Y2K showed that you don't need details beyond vague threats of "medication administered at the wrong time" and "planes falling out of the air" to get organizations and the public to care. No idea how that's going to tie into the conspiracy-heavy media landscape we inhabit now. (Note I do think this is a serious issue that needs to be addressed. And I'd love to see specific examples.…

What? Y2K did have many demonstrable problems... Having a 2 digit year did obviously cause problems. The reason nothing happened is because a shit ton of time and money was spent making sure it didn't.

Post by [deleted] » Sun, May 11, 2025, 1:02 PM UTC

AndrewKemendo wrote: post #21

Waterluvian wrote: post #9

I think this effort would benefit from trying to qualify what “unpredictable ways” actually means. If anyone is testing devices, a catalog of test results describing the actual failure modes that were revealed would help make this whole thing more concrete. I think many software engineers know that if you want to make any organization care about this type of issue, you need to be ready to demonstrate the severity and…

So that means the best tool is a 2038 test environment - which people then install their application(s) and test it e2e to see what the impacts are. However, I’m not sure how you make a 2038 test environment It assumes that the OS/Kernel etc… are defacto frozen to 2025 or whatever increment until 2038 What was the y2k solution for the people that implemented those fixes in the 90s?

Post by bongodongobob » Sun, May 11, 2025, 1:09 PM UTC

jbeninger wrote: post #23

bongodongobob wrote: post #20

Earlier quoted context omitted.

What? Y2K did have many demonstrable problems... Having a 2 digit year did obviously cause problems. The reason nothing happened is because a shit ton of time and money was spent making sure it didn't.

Agreed. My point is that the orgs paying for all these updates were mostly motivated by the vague claims of experts rather than concrete examples

Post by lionkor » Sun, May 11, 2025, 1:27 PM UTC

fmbb wrote: post #10

panzi wrote: post #8

When will milliseconds since the Unix epoch not be precisely representable in IEEE double anymore? (As it's used in JavaScript.)

In the year 287390 (285420.9 years after 1970) according to my calculations using DuckDuckGo’s calculator. If you ask ChatGPT it’s: = 285,616 years after 1970 = Year 285,616