News for hackers. Stuff that matters.
Re:AWS us-east-1 down by dylan604 on Tuesday June 13, 2023 @03:43PM (#36315847)
just report it in epoch seconds
Re:AWS us-east-1 down by dramm on Tuesday June 13, 2023 @04:34PM (#36316741)
Or stardate ¯\_(ツ)_/¯
Re:AWS us-east-1 down by queuebert on Tuesday June 13, 2023 @04:16PM (#36316372)
Julian Date
Re:AWS us-east-1 down by conductr on Tuesday June 13, 2023 @03:49PM (#36315937)
that's based on UTC, so just use UTC?
Re:AWS us-east-1 down by dylan604 on Tuesday June 13, 2023 @04:05PM (#36316169)
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

Re:AWS us-east-1 down by conductr on Tuesday June 13, 2023 @05:51PM (#36318046)
"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
Re:AWS us-east-1 down by account42 on Wednesday June 14, 2023 @08:10AM (#36324652)
I wish it was based on TAI though.
Re:AWS us-east-1 down by drivers99 on Tuesday June 13, 2023 @05:18PM (#36317513)
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.
Re:AWS us-east-1 down by yen223 on Tuesday June 13, 2023 @07:08PM (#36318905)
Just make sure not to confuse it with epoch milliseconds!
Re:AWS us-east-1 down by dathinab on Tuesday June 13, 2023 @07:09PM (#36318919)
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

Re:AWS us-east-1 down by account42 on Wednesday June 14, 2023 @08:08AM (#36324631)
Ignoring leap seconds?