[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-bugs] #13674 [Onionoo]: Remove advertised bandwidth and advertised bandwidth fraction graphs from weights document
#13674: Remove advertised bandwidth and advertised bandwidth fraction graphs from
weights document
-------------------------+---------------------
Reporter: karsten | Owner:
Type: enhancement | Status: new
Priority: normal | Milestone:
Component: Onionoo | Version:
Keywords: | Actual Points:
Parent ID: | Points:
-------------------------+---------------------
Onionoo's weights documents contain two graphs for advertised bandwidth
and advertised bandwidth fraction that I'd like to get rid of.
The reason is very similar to the reason stated in #13673 for removing the
`"advertised_bandwidth_fraction"` field from details documents:
maintaining these graphs increases code complexity which leads to errors
and makes it harder to implement new features. Further, initializing a
new Onionoo instance from descriptor archives becomes prohibitively
expensive with these two graphs.
It looks like both Atlas and Globe show the advertised bandwidth fraction
graph, but not the advertised bandwidth graph. In both cases, taking out
this graph and leaving in consensus weight fraction and guard/middle/exit
probability wouldn't hurt user experience too much.
In fact, little-t-tor doesn't depend on (self-reported) advertised
bandwidth for anything, because relays have been lying about that value in
the past. So, we shouldn't display a graph with fractions if it's known
that network totals may be inaccurate because of liars.
In the future, we might provide new bandwidth graphs for configured
bandwidth rate and burst, observed bandwidth, and advertised bandwidth
(but not fraction). Those can all be drawn from server descriptors
without having to combining them with consensuses. Adding these graphs is
not trivial and deserves a new ticket. I'm just mentioning this idea
here, because it seems relevant.
I'll leave this ticket open for discussion until beginning of next week.
If there are no convincing arguments for keeping these two graphs, I'll
remove them. They're optional, so there's no need for a month-long heads-
up here.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/13674>
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