You may have heard of the Y2038 32 bit epoch problem, but ARE YOU READY FOR Y287586 when in May we cross the point where Javascript millisecond time exceeds Number.MAX_SAFE_INTEGER & it can no longer do time math? Get your compliance plans ready! https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Number/MAX_SAFE_INTEGER

@bert_hubert I'm sure ultramarines will handle that situation too.

@bert_hubert Needs a catchier name like the epochalypse
has, maybe the "The fractioning"?

@bert_hubert And if you happen to be at #37C3, feel free to get yourself a Y2K38 reminder 😉

@c3manu @bert_hubert die hab ich ja ehrlich gesagt, schon auf dem Camp vermisst

@c3manu dieses Datum macht mich fertig; mm/dd/yyyy ist grausam

@c3manu @bert_hubert woah will those be in the sticker boxes? :D

@ink better late than never 🤷
die idee lag schon ne weile bei mir rum, aber für das camp waren mir andere designs wichtiger :)

@mangoiv same, das detail wollte ich aber originalgetreu lassen. du willst gar nicht wissen wir oft ich das nochmal überprüft habe vorm drucken lassen :D

https://commons.wikimedia.org/wiki/File:Best_Buy_-_Turn_your_computer_off_before_midnight_Y2K_Sticker.png

@c3manu

I like it!
Sadly I can't make it this year, any chance I could have the design so I can print some locally?
Thanks!

@bert_hubert You mean... Javascipt could do time maths before? 😇

@bert_hubert cavemen don't need JS

@bert_hubert There is also a Y2070 in between for software that assumed any year after 70 was 1900's and any year before 70 was 2000's.

@bert_hubert We'll get ready 10 years before the event. If we don't forget.