Post AwYdwSCUViCgbMIo2C by lanodan@queer.hacktivis.me
 (DIR) More posts by lanodan@queer.hacktivis.me
 (DIR) Post #AwYcilDGvRKVYlZfCS by kaia@brotka.st
       2025-07-27T11:38:34.686332Z
       
       4 likes, 1 repeats
       
       the people born on Jan 1st 1970 get Linux database admins worrying
       
 (DIR) Post #AwYdCpFAVKP2kQnUwa by lanodan@queer.hacktivis.me
       2025-07-27T11:44:01.155441Z
       
       1 likes, 0 repeats
       
       @kaia And something like 1980-01-01 for Windows
       
 (DIR) Post #AwYdmdPBzpVSSOYqmW by erincandescent@akko.erincandescent.net
       2025-07-27T11:48:26.269356Z
       
       1 likes, 0 repeats
       
       @lanodan @kaia windows is 1601-01-01
       
 (DIR) Post #AwYdwSCUViCgbMIo2C by lanodan@queer.hacktivis.me
       2025-07-27T11:52:15.602661Z
       
       0 likes, 0 repeats
       
       @erincandescent @kaia Huh, even though 1980-01-01 is used by FAT, zip, … how confusing
       
 (DIR) Post #AwYeAy5Alr77XHnfZw by erincandescent@akko.erincandescent.net
       2025-07-27T11:53:30.497248Z
       
       1 likes, 0 repeats
       
       @lanodan @kaia NT uses 1601-01-01, which is imo perhaps the most sensible epoch in common use (2001-01-01 is also good)
       
 (DIR) Post #AwYemUVr9sWipcAp6G by lanodan@queer.hacktivis.me
       2025-07-27T12:01:40.057553Z
       
       0 likes, 0 repeats
       
       @erincandescent @kaia I feel like 1970-01-01 makes sense, specially as it can avoid having troubles with signed vs. unsigned (like python zip raises an error on dates prior to 1980-01-01, which is of course a pain since 1970-01-01 can happen quite easily).Although I think I'd have put it as the rounded up birthday of the oldest human alive in 1970 (likely something like 1870~1890).
       
 (DIR) Post #AwYfubBGLpxtmYyG12 by erincandescent@akko.erincandescent.net
       2025-07-27T12:10:32.110240Z
       
       2 likes, 0 repeats
       
       @lanodan @kaia the Gregorian calendar works on 400 year repeating cycles that start 1601, 2001, 2401, ...FILETIME is a 64 bit unsigned count out 100ns ticks since 1601, it only has issues with times before that date
       
 (DIR) Post #AwYsBhi8WYXqPNGoam by kartoffelcheetah@social.kartoffelcheetah.eu
       2025-07-27T14:20:05.206011Z
       
       1 likes, 0 repeats
       
       @lanodan @erincandescent @kaia i once worked on an ecommerce site's UI which had to be integrated with a massive salesforce system. the best thing was that the sf validated the customer birth date to be between [18,100) years. i tried to unsuccessfully change their mind. so i had to make an error message that you can not be more than 100 years old to at least communicate the problem to the user, but that just felt really bad.
       
 (DIR) Post #AwZ0LDSYeSx37B1vfc by Christian_Freiherr_von_Wolff@infosec.exchange
       2025-07-27T15:54:24Z
       
       1 likes, 0 repeats
       
       @kaia How do you like UTC 23:59:59 1969-12-31?