(Not) Looking forward to 2038 onwards as people ignore the fact we coordinated to fix this and start saying it was all a big hoax.
Same thing happened with Y2K. You can’t let such people bother you, or you’ll be miserable.
The Epochalypse Project
11–20 of 91 posts
Re: The Epochalypse Project
#12my capitalist side remembers that many people made retirement money because of Y2K. Maybe I should start thinking about an early retirement :)
How exactly? asking for a friend
Re: The Epochalypse Project
#13my capitalist side remembers that many people made retirement money because of Y2K. Maybe I should start thinking about an early retirement :)
Well, by 2038 the chatbots will have long since fixed all the time format problems, all our problems, and will be working away at problems of which we cannot concieve.
So, ahem, your “early retirement” is assured?
A year is a lot longer than it used to be. And quickly getting longer. Measured in change.
Re: The Epochalypse Project
#14Born too early for Y2K, but just in time for the Epochalypse lol
Well we don’t know if it will actually be an e/apocalypse. Which sounds very scary and doomsy to me.
But it will be the end of time, as we know it!
Re: The Epochalypse Project
#15I 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…
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. I'm just pushing back against the idea that examples would make much difference to advocacy efforts)
Re: The Epochalypse Project
#16Telling home users to check that their existing smart devices will still work in 13 years seems like overkill. It seems unlikely that more than a tiny fraction of them will still be in use then, if any.
Businesses installing new smart infrastructure and devices will need to pay attention to this, and in 10-15 years they'll need to work out what to replace, of course.
Re: The Epochalypse Project
#17yeah sure.
Re: The Epochalypse Project
#18I 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…
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.…
“Planes falling pit of the sky” still gets used both as an example of overblown Y2k fear-mongering AND the reason why all those quiet preparations were necessary.
Re: The Epochalypse Project
#19(Not) Looking forward to 2038 onwards as people ignore the fact we coordinated to fix this and start saying it was all a big hoax.
Will people use planes falling out of the sky as the reason the fix must be priority 1 this time?
Re: The Epochalypse Project
#20I 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…
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.