Tell HN: We are now closer to the Y2K38 problem than the Y2K problem
For those of you who remember Dec 31, 1999, this might amuse you: https://imgur.com/a/dQo0y8B
Proposed rebranding: The Epochalypse.
June 10th, 2024 we hit 80%.
April 1st 2031 - 90%. (maybe not a good day to tell everyone to start worrying)
August 25th 2034 - 95% (panic time)
As an aside, I always use 2038-01-19 for any far future end dates rather than a null.
1. https://en.wikipedia.org/wiki/Year_2038_problem#Network_Time...
2. http://www.lieberbiber.de/2017/03/14/a-look-at-the-year-2036...
I still remember the day we woke up to multiple emails and lawsuit threats from our top player whose net worth suddenly went negative on the leaderboard.
Our players were very competitive and loved pushing the boundaries by trying to find vulnerabilities, shortcuts, etc so we assumed the worst and thought we had a bug in our system! Turned out to be our JSON parsing library was using integerValue on our NSNumber instances causing the ints to overflow. It was a tough week waiting for Apple to review the app while our players lost faith in us.
Lesson learned :)
(Luckily the player and our community were understanding and stay around)