Increase time ago of last block for “up to date” status from 30 to 90 minutes #1026

1. 
   laanwj commented at 6:40 pm on April 2, 2012: member

   It was too hyperactive. @gmaxwell: I mean that right now when the block gap goes over an hour it starts showing synchronizing. Increasing that to 90 minutes or so would make it only happen about 6.4 times per year
2. Increase time ago of last block for "up to date" status from 30 to 90 minutes

   It was too hyperactive.
   gmaxwell: I mean that right now when the block gap goes over an hour it starts showing synchronizing. Increasing that to 90 minutes or so would make it only happen about 6.4 times per year

   2675fe6218
3. 
   gmaxwell commented at 6:47 pm on April 2, 2012: contributor

   Half an hour was 7 false alarms per day, an hour is a false alarm every three days. Two hours is once per three years.

   The tradeoff is how quickly you let the user know that something is broken vs false alarms. Since it’s already a pretty slow indicator even at 30 minutes, I think we should error towards fewer false alarms. 90 minutes is my recommendation too.

4. 
   Diapolo commented at 8:53 pm on April 2, 2012: none

   Seems like a good change.
5. 
   sipa commented at 1:27 am on April 3, 2012: member

   ACK
6. gmaxwell referenced this in commit 3263a245bb on Apr 3, 2012
7. gmaxwell merged this on Apr 3, 2012
8. gmaxwell closed this on Apr 3, 2012

   ---

9. coblee referenced this in commit 132aa66df2 on Jul 17, 2012
10. laanwj deleted the branch on Apr 9, 2014
11. suprnurd referenced this in commit 49fb3df3e3 on Dec 5, 2017
12. sanch0panza referenced this in commit 23c31bd643 on Apr 11, 2018
13. laanwj referenced this in commit e8ad580f51 on Jan 15, 2019
14. dexX7 referenced this in commit 43d5f03570 on Oct 22, 2019
15. lateminer referenced this in commit 968000bb33 on Oct 30, 2019
16. DrahtBot locked this on Sep 8, 2021

Contributors
laanwj gmaxwell Diapolo sipa