For fans of entirely spurious numbers, the UNIX timestamp is about to hit 17777777.
Hold on to your butts!
Post
Replies:
16
@Edent
Excellent, I may get up early to witness it!
(I won't get up early... 😂 )
As an aside I did some Y2K remediation way back then, customer wanted to know if it would be 2038 compliant...
Told them that if they were still using the same server then and I was still alive I'd take a look at it.
The company no longer exists (Nothing to do with whatever I did there...)
@Edent in that vein, there's 2 common ways of incrementing DNS zone serial numbers:
YYYYMMDDnn – date-based (e.g., 2025102800)
Unix timestamp – seconds since 1970-01-01 UTC epoch
On 2034-06-16 09:06:40 UTC, these 2 schemes will produce the same serial# of 2034061600.
I have a heuristic in our codebase to use the previous serial# to work out which approach they're using, and a test that will start failing in 2034.
That's how much I care about DNS correctness!
@Edent
Just realized I missed 1337133700. A very leet time to experience no doubt.
@Edent dad are we all gonna die
Add 450288000 to get my age.
@Edent chmod 17777777
@Edent I feel old. I remember when it was only 1234567890.
I'm always wary of coincidences about numbers that only happen with a base-10 representation.
Edit: in more plain words: it means jack shit.
@hnapel what do you think the word "spurious" means?
@Edent Haha, what a strangely satisfying milestone 😄 Gotta love those nerdy moments—counting down like it’s New Year’s Eve!
I'm looking girl for vc
@Edent Use a proper time server or at least a client and forget about this crap. Not all with unix in the name has to be non plus ultra...
@Edent I do indeed enjoy this. My sister and I sometimes send screenshots or photos to each other when we notice the time hit 12:34. It’s a simple way of letting the other know we’re thinking of each other.
@Edent Let's goooo 🚀
