Mfr commited on 2008-07-03 20:23:26
Zeige 3 geänderte Dateien mit 9 Einfügungen und 11 Löschungen.
| ... | ... |
@@ -75,7 +75,7 @@ letting her opt to migrate from one major Tor version to the next. |
| 75 | 75 |
<br /> |
| 76 | 76 |
|
| 77 | 77 |
<!-- Do we want a people section? If so, would it make sense to write what |
| 78 |
-these people will be doing? And---what exactly are these people going to |
|
| 78 |
+these people will be doing? And what exactly are these people going to |
|
| 79 | 79 |
do? :) |
| 80 | 80 |
<a id="People"></a> |
| 81 | 81 |
<h2><a class="anchor" href="#People">People</a></h2> |
| ... | ... |
@@ -85,8 +85,6 @@ do? :) |
| 85 | 85 |
</ul> |
| 86 | 86 |
--> |
| 87 | 87 |
|
| 88 |
-</ul> |
|
| 89 |
- |
|
| 90 | 88 |
</div><!-- #main --> |
| 91 | 89 |
|
| 92 | 90 |
#include <foot.wmi> |
| ... | ... |
@@ -175,7 +175,7 @@ implementation and testing work on January 15, 2009. |
| 175 | 175 |
<a href="http://freehaven.net/~karsten/hidserv/perfanalysis-2008-06-15.pdf">report</a> |
| 176 | 176 |
that has been made public on the Tor |
| 177 | 177 |
<a href="http://archives.seul.org/or/dev/Jun-2008/msg00019.html">developer |
| 178 |
- mailing list</a>.</small></em> |
|
| 178 |
+ mailing list</a>.</em></small> |
|
| 179 | 179 |
<br/> |
| 180 | 180 |
<small><em>The analysis also unveiled a few bugs which were responsible |
| 181 | 181 |
for part of the delay in making a hidden service available for |
| ... | ... |
@@ -187,7 +187,7 @@ implementation and testing work on January 15, 2009. |
| 187 | 187 |
we discovered that some improvements require more in-depth |
| 188 | 188 |
changes to Tor which are not directly related to hidden services. These |
| 189 | 189 |
changes cannot be achieved in the time frame of this |
| 190 |
- project.</small></em> |
|
| 190 |
+ project.</em></small> |
|
| 191 | 191 |
</td> |
| 192 | 192 |
</tr> |
| 193 | 193 |
|
| ... | ... |
@@ -251,7 +251,7 @@ implementation and testing work on January 15, 2009. |
| 251 | 251 |
<br /> |
| 252 | 252 |
|
| 253 | 253 |
<!-- Do we want a people section? If so, would it make sense to write what |
| 254 |
-these people will be doing? And---what exactly are these people going to |
|
| 254 |
+these people will be doing? And what exactly are these people going to |
|
| 255 | 255 |
do? :) |
| 256 | 256 |
<a id="People"></a> |
| 257 | 257 |
<h2><a class="anchor" href="#People">People</a></h2> |
| ... | ... |
@@ -152,14 +152,14 @@ implementation and testing work on February 15, 2009. |
| 152 | 152 |
bootstrapping. The results are not very surprising: a client |
| 153 | 153 |
fetches about 10KB of certs, one consensus for 140KB (now 90KB, see |
| 154 | 154 |
next paragraph), and about 1.5 megs of Server Descriptors (after |
| 155 |
- half of which it starts building circuits).</small></em> |
|
| 155 |
+ half of which it starts building circuits).</em></small> |
|
| 156 | 156 |
<br /> |
| 157 | 157 |
<small><em><a href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/138-remove-down-routers-from-consensus.txt">Proposal |
| 158 | 158 |
138</a> shrinks consensus documents by 30% to |
| 159 | 159 |
40% and has already been implemented and merged into the spec. |
| 160 | 160 |
Implementation is part of the 0.2.1.x-alpha tree and the code will |
| 161 | 161 |
take effect once over two-thirds of the directory authorities |
| 162 |
- (i.e. 5 out of 6) have upgraded.</small></em> |
|
| 162 |
+ (i.e. 5 out of 6) have upgraded.</em></small> |
|
| 163 | 163 |
<br /> |
| 164 | 164 |
<small><em><a href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/140-consensus-diffs.txt">Proposal |
| 165 | 165 |
140</a> does not directly relate to reducing initial download size, |
| ... | ... |
@@ -168,7 +168,7 @@ implementation and testing work on February 15, 2009. |
| 168 | 168 |
href="http://archives.seul.org/or/dev/Jun-2008/msg00013.html">sent to |
| 169 | 169 |
or-dev</a>. There are some questions to be answered from other Tor |
| 170 | 170 |
developers first, but other than that I think it's fine and could |
| 171 |
- be implemented.</small></em> |
|
| 171 |
+ be implemented.</em></small> |
|
| 172 | 172 |
<br /> |
| 173 | 173 |
<small><em>The Big Thing is making clients not download all 1.5 megs |
| 174 | 174 |
of server descriptors. <a href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/141-jit-sd-downloads.txt">Proposal |
| ... | ... |
@@ -180,7 +180,7 @@ implementation and testing work on February 15, 2009. |
| 180 | 180 |
clients can fetch SDs on demand from routers along their circuit |
| 181 | 181 |
while they are building it (described in the draft), and deal with |
| 182 | 182 |
exit selection. We're still developing ideas for the last part; |
| 183 |
- some possibilities are mentioned in the draft.</small></em> |
|
| 183 |
+ some possibilities are mentioned in the draft.</em></small> |
|
| 184 | 184 |
</td> |
| 185 | 185 |
</tr> |
| 186 | 186 |
|
| ... | ... |
@@ -244,7 +244,7 @@ implementation and testing work on February 15, 2009. |
| 244 | 244 |
<br /> |
| 245 | 245 |
|
| 246 | 246 |
<!-- Do we want a people section? If so, would it make sense to write what |
| 247 |
-these people will be doing? And---what exactly are these people going to |
|
| 247 |
+these people will be doing? And what exactly are these people going to |
|
| 248 | 248 |
do? :) |
| 249 | 249 |
<a id="People"></a> |
| 250 | 250 |
<h2><a class="anchor" href="#People">People</a></h2> |
| 251 | 251 |