[or-cvs] r22092: {website} flesh out the bridgedb volunteer idea (website/trunk/en)

[Roger Dingledine <arma@xxxxxxxxxxxxxx>]

Author: arma
Date: 2010-03-30 05:32:14 +0000 (Tue, 30 Mar 2010)
New Revision: 22092

Modified:
   website/trunk/en/volunteer.wml
Log:
flesh out the bridgedb volunteer idea


Modified: website/trunk/en/volunteer.wml
===================================================================
--- website/trunk/en/volunteer.wml	2010-03-30 02:35:38 UTC (rev 22091)
+++ website/trunk/en/volunteer.wml	2010-03-30 05:32:14 UTC (rev 22092)
@@ -199,7 +199,7 @@
 <br />
 Priority: <i>Medium to High</i>
 <br />
-Effort Level: <i>Medium</i>
+Effort Level: <i>Medium to High</i>
 <br />
 Skill Level: <i>High</i>
 <br />
@@ -209,21 +209,29 @@
 href="<svnprojects>design-paper/blocking.html">significant
 improvements</a> in resisting national and organizational censorship.
 But Tor still needs better mechanisms for some parts of its
-anti-censorship design.  For example, current Tors can only listen on a
-single address/port combination at a time.  There's
+anti-censorship design.
+<br />
+One huge category of work is adding features to our <a
+href="http://gitweb.torproject.org//bridgedb.git?a=tree";>bridgedb</a>
+service (Python). Tor aims to give out <a href="<page bridges>">bridge
+relay addresses</a> to users that can't reach the Tor network
+directly, but there's an arms race between algorithms for distributing
+addresses and algorithms for gathering and blocking them. See <a
+href="https://blog.torproject.org/blog/bridge-distribution-strategies";>our
+blog post on the topic</a> as an overview, and then look at <a
+href="http://archives.seul.org/or/dev/Dec-2009/msg00000.html";>Roger's
+or-dev post</a> from December for more recent thoughts &mdash; lots of
+design work remains.
+<br />
+If you want to get more into the guts of Tor itself (C), another problem
+we should address is that current Tors can only listen on a single
+address/port combination at a time. There's
 <a href="<gitblob>doc/spec/proposals/118-multiple-orports.txt">a
 proposal to address this limitation</a> and allow clients to connect
 to any given Tor on multiple addresses and ports, but it needs more
 work.
 <br />
-Another area that needs work is our <a
-href="http://gitweb.torproject.org//bridgedb.git?a=tree";>bridgedb</a>
-service. See e.g. <a
-href="http://archives.seul.org/or/dev/Dec-2009/msg00000.html";>Roger's
-or-dev post</a> from December for details &mdash; lots of design work
-remains.
-<br />
-This project involves a lot of research and design. One of the big
+This project could involve a lot of research and design. One of the big
 challenges will be identifying and crafting approaches that can still
 resist an adversary even after the adversary knows the design, and
 then trading off censorship resistance with usability and robustness.