Posts and replies

@ari @mudkip someone should start an event where people all collectively gather to a single place with random stuff that needs to keep track of time(the older the better)

then everyone just stares at them until the overflow happens to see how many of them break

@mudkip technically because it's signed it'll overflow to -2^32-1, and because all negative unix timestamps are undefined the date will also be undefined (or if you ignore that you'll be somewhere around 1901)

@mudkip Signed? [sighs]

@smiteri Thank you. That’s a fantastic point.

@mudkip If it's signed it would flip around to -INT32_MAX tho, meaning 1902 or something

@mudkip $ date -uIsec --date=\@$((1 - 2 ** 31))
1901-12-13T20:45:53+00:00

Edit: I forgot to mention an unsigned 64-bit count of microseconds comes to more than 500 thousand years.

@mudkip@wetdry.world meme is inaccurate: that calendar wraps after December 2038, but it should say January 2038 on the previous page and only have about 18 squares, with 13.5% of the 19th square. the next page should also say December 1901 and be missing the first 12 squares and also only have 13.5% of the 13th square (but be missing the first parts of that square, instead of the last)

(alternatively it can flip back to January 1970 if the previous page is February 2106, with just 6.27 squares)

literally unenjoyable, please fix.