Ah right, linebreaks.. (10452ac17) - tor-webwml.git

@@ -12,34 +12,77 @@
 <hr />
 
 <p>
-The Metrics Project aims at measuring various aspects of the Tor network, including both contributed resources and network usage. These information are important, e.g., for deciding what parts of the network require more support to better meet user needs.
+The Metrics Project aims at measuring various aspects of the Tor network,
+including both contributed resources and network usage. These information
+are important, e.g., for deciding what parts of the network require more
+support to better meet user needs.
 </p>
 
 <p>
-There are at least three aspects of the Tor network which shall be considered in this project:
+There are at least three aspects of the Tor network which shall be
+considered in this project:
 </p>
 
 <ul>
-<li><b>Relays:</b> There are already statistics covering the data that relays report about themselves and which are confirmed in parts by the directory authorities. The <a href="http://torstatus.kgprog.com/">TorStatus</a> project evaluates the hourly published directories containing lists of all running relays and keeps track of their uptimes and advertised bandwidths. However, an aggregate view of the development of relays over an extended period of time is still missing. In addition to that, all information about provided bandwidth capacity as reported by the relays is not necessarily trustworthy. There has not been a comprehensive measurement of relay performance so far to validate bandwidth claims and relay stability.
-<li><b>Bridges:</b> A special type of relays is running as bridges. Bridges are relaying traffic, too, but are not listed in the public directory. The purpose of bridges is to allow censored clients to connect to the Tor network without their censor being able to prohibit access easily. The number and capacity of bridges is therefore not publicly known and has not been evaluated, yet.
-<li><b>Clients:</b> Little is known about usage of the Tor network. In particular, the number and location of clients are largely unknown. A rough estimation is that there are a few hundreds of thousands of clients in the network; a number which is very hard to verify. There are no recent studies on the number of Tor users which would help obtaining a better picture on usage of the Tor network. Clearly, all investigations of clients need to be performed with special care and in highly aggregated form to protect users' anonymity.
+<li><b>Relays:</b> There are already statistics covering the data that
+relays report about themselves and which are confirmed in parts by the
+directory authorities. The <a
+href="http://torstatus.kgprog.com/">TorStatus</a> project evaluates the
+hourly published directories containing lists of all running relays and
+keeps track of their uptimes and advertised bandwidths. However, an
+aggregate view of the development of relays over an extended period of time
+is still missing. In addition to that, all information about provided
+bandwidth capacity as reported by the relays is not necessarily
+trustworthy. There has not been a comprehensive measurement of relay
+performance so far to validate bandwidth claims and relay stability.
+<li><b>Bridges:</b> A special type of relays is running as bridges. Bridges
+are relaying traffic, too, but are not listed in the public directory. The
+purpose of bridges is to allow censored clients to connect to the Tor
+network without their censor being able to prohibit access easily. The
+number and capacity of bridges is therefore not publicly known and has not
+been evaluated, yet.
+<li><b>Clients:</b> Little is known about usage of the Tor network. In
+particular, the number and location of clients are largely unknown. A rough
+estimation is that there are a few hundreds of thousands of clients in the
+network; a number which is very hard to verify. There are no recent studies
+on the number of Tor users which would help obtaining a better picture on
+usage of the Tor network. Clearly, all investigations of clients need to be
+performed with special care and in highly aggregated form to protect users'
+anonymity.
 </li>
 </ul>
 
 <p>
-The Metrics Project is planned to run for three years from September 2008 to August 2011 (see section 5.7 of the <a href="https://svn.torproject.org/svn/tor/trunk/doc/roadmaps/2008-12-19-roadmap-full.pdf">three-year development roadmap</a> for more details). Milestones are scheduled for every six months in this period. The following sections (yet only one) show progress made in these milestones.
+The Metrics Project is planned to run for three years from September 2008
+to August 2011 (see section 5.7 of the <a
+href="https://svn.torproject.org/svn/tor/trunk/doc/roadmaps/2008-12-19-roadmap-full.pdf">three-year
+development roadmap</a> for more details). Milestones are scheduled for
+every six months in this period. The following sections (yet only one) show
+progress made in these milestones.
 </p>
 
 <h3>February 2009</h3>
 
 <p>
-The first milestone of the Metrics Project is intended to evaluate already existing and newly gathered data about the Tor network. These evaluations shall help decide what data will be needed in the future to measure contribution to and usage of the Tor network. The following results are already available. <a href="mailto:tor-assistants@freehaven.net">Feedback</a> is very welcome!
+The first milestone of the Metrics Project is intended to evaluate already
+existing and newly gathered data about the Tor network. These evaluations
+shall help decide what data will be needed in the future to measure
+contribution to and usage of the Tor network. The following results are
+already available. <a
+href="mailto:tor-assistants@freehaven.net">Feedback</a> is very welcome!
 </p>
 
 <ul>
-<li>Evaluation of Relays from Public Directory Data (<a href="http://freehaven.net/~karsten/metrics/dirarch-2009-02-08.pdf">PDF</a>, 194K) from February 8, 2009.
-<li>Analysis of Bridge Usage in Tor (<a href="http://freehaven.net/~karsten/metrics/bridges-2008-12-25.pdf">PDF</a>, 4.3M) from December 25, 2008.
-<li>All scripts and sources used in these evaluations (not the data, unfortunately) are available in a public Git repository that can be cloned using the following command:<br /> <tt>git clone git://git.torproject.org/~karsten/git/metrics/</tt>
+<li>Evaluation of Relays from Public Directory Data (<a
+href="http://freehaven.net/~karsten/metrics/dirarch-2009-02-08.pdf">PDF</a>,
+194K) from February 8, 2009.
+<li>Analysis of Bridge Usage in Tor (<a
+href="http://freehaven.net/~karsten/metrics/bridges-2008-12-25.pdf">PDF</a>,
+4.3M) from December 25, 2008.
+<li>All scripts and sources used in these evaluations (not the data,
+unfortunately) are available in a public Git repository that can be cloned
+using the following command:<br /> <tt>git clone
+git://git.torproject.org/~karsten/git/metrics/</tt>
 </ul>
 
 <br />


...	...	@@ -12,34 +12,77 @@
12	12	<hr />
13	13
14	14	<p>
15		-The Metrics Project aims at measuring various aspects of the Tor network, including both contributed resources and network usage. These information are important, e.g., for deciding what parts of the network require more support to better meet user needs.
	15	+The Metrics Project aims at measuring various aspects of the Tor network,
	16	+including both contributed resources and network usage. These information
	17	+are important, e.g., for deciding what parts of the network require more
	18	+support to better meet user needs.
16	19	</p>
17	20
18	21	<p>
19		-There are at least three aspects of the Tor network which shall be considered in this project:
	22	+There are at least three aspects of the Tor network which shall be
	23	+considered in this project:
20	24	</p>
21	25
22	26	<ul>
23		-<li><b>Relays:</b> There are already statistics covering the data that relays report about themselves and which are confirmed in parts by the directory authorities. The <a href="http://torstatus.kgprog.com/">TorStatus</a> project evaluates the hourly published directories containing lists of all running relays and keeps track of their uptimes and advertised bandwidths. However, an aggregate view of the development of relays over an extended period of time is still missing. In addition to that, all information about provided bandwidth capacity as reported by the relays is not necessarily trustworthy. There has not been a comprehensive measurement of relay performance so far to validate bandwidth claims and relay stability.
24		-<li><b>Bridges:</b> A special type of relays is running as bridges. Bridges are relaying traffic, too, but are not listed in the public directory. The purpose of bridges is to allow censored clients to connect to the Tor network without their censor being able to prohibit access easily. The number and capacity of bridges is therefore not publicly known and has not been evaluated, yet.
25		-<li><b>Clients:</b> Little is known about usage of the Tor network. In particular, the number and location of clients are largely unknown. A rough estimation is that there are a few hundreds of thousands of clients in the network; a number which is very hard to verify. There are no recent studies on the number of Tor users which would help obtaining a better picture on usage of the Tor network. Clearly, all investigations of clients need to be performed with special care and in highly aggregated form to protect users' anonymity.
	27	+<li><b>Relays:</b> There are already statistics covering the data that
	28	+relays report about themselves and which are confirmed in parts by the
	29	+directory authorities. The <a
	30	+href="http://torstatus.kgprog.com/">TorStatus</a> project evaluates the
	31	+hourly published directories containing lists of all running relays and
	32	+keeps track of their uptimes and advertised bandwidths. However, an
	33	+aggregate view of the development of relays over an extended period of time
	34	+is still missing. In addition to that, all information about provided
	35	+bandwidth capacity as reported by the relays is not necessarily
	36	+trustworthy. There has not been a comprehensive measurement of relay
	37	+performance so far to validate bandwidth claims and relay stability.
	38	+<li><b>Bridges:</b> A special type of relays is running as bridges. Bridges
	39	+are relaying traffic, too, but are not listed in the public directory. The
	40	+purpose of bridges is to allow censored clients to connect to the Tor
	41	+network without their censor being able to prohibit access easily. The
	42	+number and capacity of bridges is therefore not publicly known and has not
	43	+been evaluated, yet.
	44	+<li><b>Clients:</b> Little is known about usage of the Tor network. In
	45	+particular, the number and location of clients are largely unknown. A rough
	46	+estimation is that there are a few hundreds of thousands of clients in the
	47	+network; a number which is very hard to verify. There are no recent studies
	48	+on the number of Tor users which would help obtaining a better picture on
	49	+usage of the Tor network. Clearly, all investigations of clients need to be
	50	+performed with special care and in highly aggregated form to protect users'
	51	+anonymity.
26	52	</li>
27	53	</ul>
28	54
29	55	<p>
30		-The Metrics Project is planned to run for three years from September 2008 to August 2011 (see section 5.7 of the <a href="https://svn.torproject.org/svn/tor/trunk/doc/roadmaps/2008-12-19-roadmap-full.pdf">three-year development roadmap</a> for more details). Milestones are scheduled for every six months in this period. The following sections (yet only one) show progress made in these milestones.
	56	+The Metrics Project is planned to run for three years from September 2008
	57	+to August 2011 (see section 5.7 of the <a
	58	+href="https://svn.torproject.org/svn/tor/trunk/doc/roadmaps/2008-12-19-roadmap-full.pdf">three-year
	59	+development roadmap</a> for more details). Milestones are scheduled for
	60	+every six months in this period. The following sections (yet only one) show
	61	+progress made in these milestones.
31	62	</p>
32	63
33	64	<h3>February 2009</h3>
34	65
35	66	<p>
36		-The first milestone of the Metrics Project is intended to evaluate already existing and newly gathered data about the Tor network. These evaluations shall help decide what data will be needed in the future to measure contribution to and usage of the Tor network. The following results are already available. <a href="mailto:tor-assistants@freehaven.net">Feedback</a> is very welcome!
	67	+The first milestone of the Metrics Project is intended to evaluate already
	68	+existing and newly gathered data about the Tor network. These evaluations
	69	+shall help decide what data will be needed in the future to measure
	70	+contribution to and usage of the Tor network. The following results are
	71	+already available. <a
	72	+href="mailto:tor-assistants@freehaven.net">Feedback</a> is very welcome!
37	73	</p>
38	74
39	75	<ul>
40		-<li>Evaluation of Relays from Public Directory Data (<a href="http://freehaven.net/~karsten/metrics/dirarch-2009-02-08.pdf">PDF</a>, 194K) from February 8, 2009.
41		-<li>Analysis of Bridge Usage in Tor (<a href="http://freehaven.net/~karsten/metrics/bridges-2008-12-25.pdf">PDF</a>, 4.3M) from December 25, 2008.
42		-<li>All scripts and sources used in these evaluations (not the data, unfortunately) are available in a public Git repository that can be cloned using the following command:<br /> <tt>git clone git://git.torproject.org/~karsten/git/metrics/</tt>
	76	+<li>Evaluation of Relays from Public Directory Data (<a
	77	+href="http://freehaven.net/~karsten/metrics/dirarch-2009-02-08.pdf">PDF</a>,
	78	+194K) from February 8, 2009.
	79	+<li>Analysis of Bridge Usage in Tor (<a
	80	+href="http://freehaven.net/~karsten/metrics/bridges-2008-12-25.pdf">PDF</a>,
	81	+4.3M) from December 25, 2008.
	82	+<li>All scripts and sources used in these evaluations (not the data,
	83	+unfortunately) are available in a public Git repository that can be cloned
	84	+using the following command:<br /> <tt>git clone
	85	+git://git.torproject.org/~karsten/git/metrics/</tt>
43	86	</ul>
44	87
45	88	<br />
46	89