...
#python3 -c 'import time; print(time.localtime(-17890896514))'
time.struct_time(tm_year=1403, tm_mon=1, tm_mday=23, tm_hour=0, tm_min=0, tm_sec=0, tm_wday=6, tm_yday=23, tm_isdst=0)

#perl -e 'print join q[ ], localtime(-17890896514)'
0 0 0 23 0 -497 0 22 0

... funny thing is (Perl) "localtime" function in scalar context produces, as a string, sensible individual values (format sucks however) ...

perl -e 'print scalar localtime(-17890896514)'
Sun Jan 23 00:00:00 1403

#C #localtime(3)

@sundew @aphyr Blame that on #C & programming language makers continuing to use, expose the underlying foundation; see "#localtime(3)" & friends https://man.freebsd.org/cgi/man.cgi?query=localtime&apropos=0&sektion=3&manpath=FreeBSD+14.2-STABLE&arch=default&format=html -- search for "External declaration" (could not quote fields of "tm" structure with comments due to the character limit of the server).

In this respect, #Python "time.struct_time", 9-element tuple, https://docs.python.org/3/library/time.html#time.struct_time has better structure (year is not based around 0 for you to add 1900 to it as it does in fucking #Perl; etc)

@7331 @asahi95 #DST / #DaylightSavingsTime is just torture and if it was my decision we'd instead have #Unixtime and #LocalTime only.

@mcc @gsuberland That reminds me of @fuchsiii which knows a thing from the #ArchWiki on how to force Redmondian #Govware to accept #Unixtime as System Clock yet display #LocalTime on the Desktop...

Maybe she got that link handy...

@jensilber @gbhnews @jaspar I've toyed with proclaiming the Somerville Meridian, centered on Prospect Hill. (Lots of great cities have had their own meridian, why shouldn't Somerville!?) Get clocks prominently labeled "Somerville Standard Time", all synchronized to SST, put them in prominent locations.

SST would be about 12-minutes east of EST, maybe you would like that?