News for hackers. Stuff that matters.
Re:SFO near miss might have triggered aviation disaster by justinjlynn on Tuesday July 11, 2017 @02:38AM (#14742047)
A broken clock is correct at least once a day.
Re:SFO near miss might have triggered aviation disaster by idlewords on Tuesday July 11, 2017 @02:51AM (#14742095)
That used to be true (twice a day, even), but now it just flashes 12:00, or the screen is dead.
Re:SFO near miss might have triggered aviation disaster by caf on Tuesday July 11, 2017 @03:48AM (#14742304)
A clock that flashes 12:00 is still right twice a day.
Re:SFO near miss might have triggered aviation disaster by glenneroo on Tuesday July 11, 2017 @04:44AM (#14742546)
Unless you live in a country which uses 24-hour clocks, which is most of the world.

Source: https://en.wikipedia.org/wiki/Date_and_time_representation_b...

Re:SFO near miss might have triggered aviation disaster by caf on Tuesday July 11, 2017 @07:38PM (#14748999)
Do unset clocks flash 12:00 in locations that use 24-hour clocks, or do they flash 00:00?
Re:SFO near miss might have triggered aviation disaster by glenneroo on Wednesday July 12, 2017 @12:08PM (#14753704)
I can't honestly say I ever paid attention, but I just checked all clocks I could find, one flashes 00:00 and the other 0:00. Most if not all clocks I've used had a 12 or 24-hour mode, not sure what happens if you set to 12-hour and unplug it (probably just reset to defaults).
Re:SFO near miss might have triggered aviation disaster by idlewords on Tuesday July 11, 2017 @10:46AM (#14744594)
Flashing is an error condition.
Re:SFO near miss might have triggered aviation disaster by justinjlynn on Tuesday July 11, 2017 @08:30PM (#14749239)
Indeed, a broken modern digital clock is likely to just be blank.
Re:SFO near miss might have triggered aviation disaster by Kliment on Tuesday July 11, 2017 @03:50AM (#14742313)
So it's correct at 12 and possibly at midnight too