commit 2ed1ce17e5bea1d65b369522025dad8423e6cfa3 Author: Karsten Loesing karsten.loesing@gmx.net Date: Sun Aug 26 17:34:25 2012 +0200

Stop highlighting old news. --- web/index.html | 26 ++++++++++---------------- 1 files changed, 10 insertions(+), 16 deletions(-)

diff --git a/web/index.html b/web/index.html index 384bfd4..aba746d 100755 --- a/web/index.html +++ b/web/index.html @@ -302,7 +302,7 @@ same family as this relay. Optional field. Omitted if empty or if descriptor containing this information cannot be found.</li> -<li><b><font color="blue">"advertised_bandwidth_fraction":</font></b> +<li><b>"advertised_bandwidth_fraction":</b> Relative advertised bandwidth of this relay compared to the total advertised bandwidth in the network. If there were no bandwidth authorities, this fraction would be a very @@ -310,17 +310,15 @@ rough approximation of the probability of this relay to be selected by clients. Optional field. Omitted if the relay is not running, or router descriptor containing this -information cannot be found. -<font color="blue">Added field on July 19, 2012.</font></li> -<li><b><font color="blue">"consensus_weight_fraction":</font></b> +information cannot be found.</li> +<li><b>"consensus_weight_fraction":</b> Fraction of this relay's consensus weight compared to the sum of all consensus weights in the network. This fraction is a very rough approximation of the probability of this relay to be selected by clients. Optional field. -Omitted if the relay is not running. -<font color="blue">Added field on July 19, 2012.</font></li> -<li><b><font color="blue">"guard_probability":</font></b> +Omitted if the relay is not running.</li> +<li><b>"guard_probability":</b> Probability of this relay to be selected for the guard position. This probability is calculated based on consensus weights, relay flags, and bandwidth weights in the consensus. @@ -328,9 +326,8 @@ Path selection depends on more factors, so that this probability can only be an approximation. Optional field. Omitted if the relay is not running, or the consensus does not contain -bandwidth weights. -<font color="blue">Added field on July 19, 2012.</font></li> -<li><b><font color="blue">"middle_probability":</font></b> +bandwidth weights.</li> +<li><b>"middle_probability":</b> Probability of this relay to be selected for the middle position. This probability is calculated based on consensus weights, relay flags, and bandwidth weights in the consensus. @@ -338,9 +335,8 @@ Path selection depends on more factors, so that this probability can only be an approximation. Optional field. Omitted if the relay is not running, or the consensus does not contain -bandwidth weights. -<font color="blue">Added field on July 19, 2012.</font></li> -<li><b><font color="blue">"exit_probability":</font></b> +bandwidth weights.</li> +<li><b>"exit_probability":</b> Probability of this relay to be selected for the exit position. This probability is calculated based on consensus weights, relay flags, and bandwidth weights in the consensus. @@ -348,8 +344,7 @@ Path selection depends on more factors, so that this probability can only be an approximation. Optional field. Omitted if the relay is not running, or the consensus does not contain -bandwidth weights. -<font color="blue">Added field on July 19, 2012.</font></li> +bandwidth weights.</li> </ul> </li> <li><b>"bridges_published":</b> UTC timestamp (YYYY-MM-DD hh:mm:ss) when @@ -647,7 +642,6 @@ fingerprints in the URL. <h3><a href="#weights" class="anchor">Weights documents</a></h3> <p>Weights documents contain aggregate statistics of a relay's probability to be selected by clients for building paths. -<font color="blue">Added document type on July 24, 2012.</font> Weights documents contain different time intervals and are available for all relays that have been running in the past week. Weights documents contain the following fields: