Re: [tor-bugs] #24256 [Metrics/Atlas]: atlas complains "outdated tor version" for too *new* tor versions too

[Tor Bug Tracker & Wiki]

#24256: atlas complains "outdated tor version" for too *new* tor versions too
---+--
 Reporter:  arma   |  Owner:  metrics-team
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by arma):

 Replying to [comment:2 karsten]:
 > I'd guess that the relay operator knows pretty well whether they're
 running something experimental or haven't updated their package for a
 while.

 And if only the relay operator used the atlas page for the relay, that
 would be enough. I worry that users look at the atlas pages for other
 relays and get scared.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #24256 [Metrics/Atlas]: atlas complains "outdated tor version" for too *new* tor versions too

[Tor Bug Tracker & Wiki]

#24256: atlas complains "outdated tor version" for too *new* tor versions too
---+--
 Reporter:  arma   |  Owner:  metrics-team
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--
Changes (by nickm):

 * milestone:  Tor: 0.3.3.x-final =>


Comment:

 oops; wrong ticket.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #24256 [Metrics/Atlas]: atlas complains "outdated tor version" for too *new* tor versions too

[Tor Bug Tracker & Wiki]

#24256: atlas complains "outdated tor version" for too *new* tor versions too
---+
 Reporter:  arma   |  Owner:  metrics-team
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:  Tor: 0.3.3.x-final
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+
Changes (by nickm):

 * milestone:   => Tor: 0.3.3.x-final


--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #24256 [Metrics/Atlas]: atlas complains "outdated tor version" for too *new* tor versions too

[Tor Bug Tracker & Wiki]

#24256: atlas complains "outdated tor version" for too *new* tor versions too
---+--
 Reporter:  arma   |  Owner:  metrics-team
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by karsten):

 One possible way to fix this would be to change "outdated" to "not
 recommended" in that Atlas text and let the user figure out whether that
 means too old or too new. I'd guess that the relay operator knows pretty
 well whether they're running something experimental or haven't updated
 their package for a while.

 However, if that's a major usability issue, let's add the logic for
 deciding whether "not recommended" means "outdated" to Onionoo. In that
 case I wouldn't mind working from a spec.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

Re: [tor-bugs] #24256 [Metrics/Atlas]: atlas complains "outdated tor version" for too *new* tor versions too

[Tor Bug Tracker & Wiki]

#24256: atlas complains "outdated tor version" for too *new* tor versions too
---+--
 Reporter:  arma   |  Owner:  metrics-team
 Type:  defect | Status:  new
 Priority:  Medium |  Milestone:
Component:  Metrics/Atlas  |Version:
 Severity:  Normal | Resolution:
 Keywords: |  Actual Points:
Parent ID: | Points:
 Reviewer: |Sponsor:
---+--

Comment (by arma):

 Replying to [ticket:24256 arma]:
 > Tor has some somewhat complicated logic for deciding whether a version
 is obsolete -- see tor_version_is_obsolete(). Is atlas's best plan to try
 to reproduce Tor's logic? Should we try to specify it, e.g. in version-
 spec.txt, so external programs have a chance of getting it right?

 I opened #24257 for the Tor side of this fix.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs