[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #24256 [Metrics/Atlas]: atlas complains "outdated tor version" for too *new* tor versions too
#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: <https://trac.torproject.org/projects/tor/ticket/24256#comment:2>
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