🚀 go-pugleaf

From: jsq%tzec.UTEXAS@ut-sally.ARPA (John Quarterman)

My assumption was that checking the time of independent hosts should
be more dependable than checking anything on the local host, especially
after a bad crash or operator error.

There are many other things which netdate could do.  Once it's chosen
what it thinks is the set of most accurate hosts, it could take the
RMS average, toss out anything which deviates too far, average again,
and use the result as the time.  It could poll the whole set of accurate
hosts several times when averaging, or it could just poll the single
most accurate host several times and average.  It could notice
the network latency and adjust for it.

I may add some of these things (preferably after wiser heads remark
on which ones would be most useful).  What I wanted to start with
was something simple which could be depended upon to reject truly
bogus times.