[or-cvs] r22013: {website} put some more polish on my brilliant wishlist item (website/trunk/en)

[Roger Dingledine <arma@xxxxxxxxxxxxxx>]

Author: arma
Date: 2010-03-18 09:06:10 +0000 (Thu, 18 Mar 2010)
New Revision: 22013

Modified:
   website/trunk/en/volunteer.wml
Log:
put some more polish on my brilliant wishlist item


Modified: website/trunk/en/volunteer.wml
===================================================================
--- website/trunk/en/volunteer.wml	2010-03-18 07:22:41 UTC (rev 22012)
+++ website/trunk/en/volunteer.wml	2010-03-18 09:06:10 UTC (rev 22013)
@@ -170,7 +170,7 @@
 <br />
 This project would make use of <a
 href="https://svn.torproject.org/svn/torflow/trunk/README";>TorFlow</a>,
-a set of Python scripts to interact with Tor; the project would be
+a set of Python scripts to interact with Tor,
 to figure out how our Tor Exit Checker should actually work, and then
 build it &mdash; probably in Python since Torflow is in Python. The main
 goal is to reduce false positives as much as possible, by making sure
@@ -179,8 +179,12 @@
 passed to the Check script quickly. As a bonus, we should standardize
 (specify) the format of the exitAddresses file, and rewrite the <a
 href="https://svn.torproject.org/svn/check/trunk/cgi-bin/TorBulkExitList.py";>Tor
-Bulk Exit List</a> script to use that file rather than its current
-horrible DNS hacks.
+Bulk Exit List</a> script to use that file rather than its current <a
+href="https://bugs.torproject.org/flyspray/index.php?do=details&id=1019";>horrible
+DNS hacks</a>. As an extra bonus, we should work with Freenode, OFTC,
+and/or other IRC networks to make sure that the scripts we offer are
+actually the scripts they want, in terms of accurately identifying which
+of their users are coming from the Tor network.
 <br />
 You can fetch the <a href="git://git.torproject.org/git/tordnsel">latest
 tordnsel</a> via git.