3 ms·

I'm curious about the title on this submission. I thought TrueTime had unusually strong guarantees about accuracy that don't seem to be called out in what I'm

• sizediterable 5y ago
  Sorry if it's a bit sensationalized. I wanted to give some color as to why this release might be interesting and took this tweet I saw at face value https://twitter.com/rbranson/status/1455923426359578631 https://twitter.com/rbranson/status/1455923426359578631
  • tyingq 5y ago
    Oh, I wasn't criticizing, just genuinely curious. If the AWS service has a similar design, that's interesting to me. AWS doesn't seem to say much about the details.
  • dang 5y ago
    If you want to say what you think is important about an article, that's great, but please do it by adding a comment to the thread. Then your view will be on a level playing field with everyone else's: https://hn.algolia.com/?dateRange=all&page=0&prefix=false&sort=byDate&type=comment&query=%22level%20playing%20field%22%20by:dang https://hn.algolia.com/?dateRange=all&page=0&prefix=false&so... "Please use the original title, unless it is misleading or linkbait; don't editorialize." https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
• morei 5y ago
  Not quite: Truetime has guarantees about ordering, rather than accuracy. If you ask for the time and get A, and then ask for the time again and get B, then Truetime guarantees that A is less than B. Obviously, in a distributed setting this is much easier to do if you have accurately sync'ed clocks, but that accuracy goes to reducing the uncertainty in the time (and hence making truetime faster) rather than providing accuracy.