Re:AWS us-east-1 down
by dylan604 on Tuesday June 13, 2023 @03:43PM
(#36315847)
just report it in epoch seconds
[ Parent
| on HN ]
Or stardate ¯\_(ツ)_/¯
Julian Date
that's based on UTC, so just use UTC?
based on is not the same thing though is it?
UTC is human readable even if it is not calculated correctly. yes, i'm saying that if you can read epoch seconds, you're not human. 1970-01-01 00:00:00 is always a give away that something is a foot
"anchored on" then? I might be wrong but we're both talking about showing time as distance from the same starting point are we not? One's just more human readable so that's why I say why not just use that? Seconds since can be miscalculated too, especially if current time isn't known/reliable
I wish it was based on TAI though.
Or Swatch Internet time (.beat time). No time zones, it's always UTC+1, with the day divided into 1000 beats.
Re:AWS us-east-1 down
by inopinatus on Tuesday June 13, 2023 @05:19PM
(#36317535)
I will pass you the address of a struct timespec, please fill it in.
Just make sure not to confuse it with epoch milliseconds!
better:
time encoded as a float of trecenti-seconds since year -8435 of the Georgian Calendar
why?
'caus it hurt to even just think about implementing that anywhere