2018-06-28 01:37:21 - sdwdate - WARNING - Maximum allowed number of failures reached in pool 1 (6 of 18). Giving up.
If the problem occurs too frequently, please report it.
Sleeping for 13 minutes.
Bad usability design by me especially in context of blocking networking until sdwdate finished.
Do you see the case for waiting randomized minutes and nanoseconds to improve anonymity (to avoid being detected as Whonix / sdwdate users) by avoiding predictable traffic between sdwdate time fetches?
On success sdwdate is currently waiting randomly between 60 and 180 minutes. (Plus always randomized nanoseconds.)
On error (even at first boot!) sdwdate is currently waiting between 5 and 15 minutes.
What about not waiting at all in case of error? Consequences:
- possibly continuous traffic to onion time sources
- predictable traffic?
- sdwdate log size ever increasing (but could find a solution maybe)
Maybe on error wait between 0 and 10 seconds? Or between 5 and 15 seconds? Or between 5 and 60 seconds? Or…?
//cc @HulaHoop