4 ms·
At 00:00:00 UTC, I assume? I don't expect there's any reason for them to divide by a datetime...but one can hope that some ad server somewhere has crashed as a
by LeifCarrotson 4y ago
At 00:00:00 UTC, I assume?
I don't expect there's any reason for them to divide by a datetime...but one can hope that some ad server somewhere has crashed as a result.
My go-to birthday has always been January 1st of the year I was actually born. That way it doesn't raise any eyebrows if I want to convert something to a real account or interact with real people, but it fails verification if they mishandle my credentials.
That's worked great, except that one time when I inadvertently booked a flight on united.com (who should have my actual birthday, with whom I'd flown internationally several times before) with a session token or something set by a random travel search engine to whom I had given my fake January 1st birthday and then (I thought) abandoned before picking a different flight. Customs had pointed questions about the authenticity of my passport and driver's license, because their system showed that my documents should be different and they couldn't tell me why... They eventually let me back into the country, but that was not fun.
- vanilla_nut 4y agoEven better, if it ever ends up mattering -- say, at a border crossing -- you have plausible deniability. "Oh, that's the first Unix epoch timestamp, must be a bug in the system." Not sure how much it would help at a border crossing... but with any kind of tech support it would immediately elicit a chuckle.
- b800h 4y agoWhat, you reckon first or second line tech support would recognise that as the Unix epoch?
- vanilla_nut 4y agotech support at any level could likely web search for it and confirm it quickly. But maybe i'm being a smidge optimistic :-)