[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #9814 [Atlas]: Atlas should make clear when relay details come from outdated consensus

#9814: Atlas should make clear when relay details come from outdated consensus
------------------------+--------------------------
     Reporter:  wfn     |      Owner:  phw
         Type:  defect  |     Status:  needs_review
     Priority:  normal  |  Milestone:
    Component:  Atlas   |    Version:
   Resolution:          |   Keywords:
Actual Points:          |  Parent ID:
       Points:          |
------------------------+--------------------------

Comment (by karsten):

 Replying to [comment:5 phw]:
 >  1. I renamed 'Status' to 'Current Status' to make it clear that this is
 the information to trust.

 Sounds good.

 >  1. I renamed 'Uptime' to 'Last Restarted'. It certainly makes more
 sense than 'Uptime'. It might be better to display it unconditionally
 because people could be interested in it even though the relay is offline.

 Hmm.  To me, 'last restarted' means the date and time when the relay or
 bridge has last been restarted, not the time that has elapsed since then.

 Here's an alternative: if a relay or bridge is not running, display its
 'Downtime' by subtracting `last_seen` from the current system time.  That
 information might be more interesting to users than the previous uptime
 anyway.

 >  1. If the relay is currently offline, 'Last Known Properties' is shown
 instead of 'Properties'. In that case an additional field, 'Last Seen', is
 shown.

 Makes sense.

 Also, here's a minor remark on Git commit messages: http://git-
 scm.com/book/ch5-2.html#Commit-Guidelines

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/9814#comment:6>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs