[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[or-cvs] new-contribute is now valid xhtml 1.1
Update of /home/or/cvsroot/website
In directory moria:/tmp/cvs-serv12451
Modified Files:
new-contribute.html
Log Message:
new-contribute is now valid xhtml 1.1
Index: new-contribute.html
===================================================================
RCS file: /home/or/cvsroot/website/new-contribute.html,v
retrieving revision 1.6
retrieving revision 1.7
diff -u -d -r1.6 -r1.7
--- new-contribute.html 14 Jun 2005 03:41:14 -0000 1.6
+++ new-contribute.html 14 Jun 2005 03:55:30 -0000 1.7
@@ -1,5 +1,4 @@
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
-"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd";>
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd";>
<html xmlns="http://www.w3.org/1999/xhtml"; xml:lang="en">
<head>
@@ -69,26 +68,26 @@
<li>Change server descriptors to declare log level.</li>
<li>Add in support for clients to avoid servers that are too loggy based upon user configuration of acceptable log level.</li>
<li>Separate node discovery from routing to allow neat extensions. [Goodell?]</li>
-<ul>
+<li><ul>
<li>Add SetServerStatus control event to adjust verified/running status of nodes.</li>
<li>Add NoDownload config option to prevent regular directory downloads from happening.</li>
-</ul>
+</ul></li>
<li>Choosing exit node by meta-data, e.g. country.</li>
<li>Use cpuworker for more heavy lifting.</li>
-<ul>
+<li><ul>
<li>Signing (and verifying) hidserv descriptors</li>
<li>Signing (and verifying) intro/rend requests</li>
<li>Signing (and verifying) router descriptors</li>
<li>Signing (and verifying) directories</li>
<li>Doing TLS handshake (this is very hard to separate out, though)</li>
-</ul>
+</ul></li>
<li>Buffer size pool: allocate a maximum size for all buffers, not a maximum size for each buffer. So we don't have to give up as quickly (and kill the thickpipe!) when there's congestion.</li>
<li>Add alternative versions of crypto.c and tortls.c to use libnss or libgcrypt+gnutls.</li>
<li>Implement a way to stop falling back to forbidden ports when FascistFirewall blocks all good dirservers, if there is already a good, cached directory locally.</li>
<li>Extend our NSIS-based windows installer to include FreeCap and/or Privoxy.</li>
<li>Develop a way to handle OS X installation and uninstallation.</li>
<li>Develop a GUI or other controller program, to do configuration, etc. See our control specification for details, and the rudimentary demonstration Python control script. </li>
-<ul>
+<li><ul>
<li>Design an interface for the control program. You can use any license you want, but we'd recommend 3-clause BSD or maybe GPL; and we can only help out if your license conforms to the DFSG.</li>
<li>Periodically people running servers tells us they want to have one
BandwidthRate during some part of the day, and a different
@@ -99,7 +98,7 @@
until appropriate times and then do its tweak (that's probably more
portable). Can somebody write one for us and we'll put it inside
tor/contrib/?</li>
-</ul>
+</ul></li>
<li>Develop a way to become a Windows NT service. </li>
<li>Develop a systray app for Tor under MS Windows (all versions). </li>
<li>Integrate a good (portable, fast, clean, BSD-free) asynchronous DNS library so we don't have to keep forking DNS worker threads to do gethostbyname.</li>
@@ -128,11 +127,11 @@
<ul>
<li>Test out why some of our tor servers have dns resolvers that resolve
unknown addresses to 127.0.0.1.</li>
-<ul>
+<li><ul>
<li>Identify the servers that experience this issue. </li>
<li>Identify how to cause and repair the issue in BIND, DJBDNS, or
whatever daemon the misconfigured servers use.</li>
-</ul>
+</ul></li>
<li>Figure out how to setup web proxy gateways to let normal people
browse hidden services. (This has been done a few times, but nobody has
sent us code.)</li>
@@ -160,14 +159,14 @@
**hard**
<ul>
<li>Arranging membership management for independence.</li>
-<ul>
+<li><ul>
<li>Sybil defenses without having a human bottleneck.</li>
<li>How to gather random sample of nodes.</li>
<li>How to handle nodelist recommendations.</li>
<li>Consider incremental switches: a p2p tor with only 50 users has
different anonymity properties than one with 10k users, and should be
treated differently.</li>
-</ul>
+</ul></li>
<li>Incentives to relay; incentives to exit.</li>
<li>Allowing dissidents to relay through Tor clients.</li>
<li>Experiment with mid-latency systems. How do they impact usability,
@@ -180,7 +179,7 @@
<li>Attacking freenet-gnunet/timing-delay-randomness-arguments.</li>
<li>Is exiting from the middle of the circuit always a bad idea?</li>
<li>IPv6 support (For exit addresses)</li>
-<ul>
+<li><ul>
<li>Spec issue: if a resolve returns an IP4 and an IP6 address,
which to use?</li>
<li>Add to exit policy code</li>
@@ -189,7 +188,7 @@
a generalize address struct.</li>
<li>Change relay cell types to accept new addresses.</li>
<li>Add flag to serverdescs to tell whether IPv6 is supported.</li>
-</ul>
+</ul></li>
<li>patch tsocks with our current patches + gethostbyname, getpeername,
etc.</li>
<li>make freecap (or whichever) do what we want.</li>
@@ -235,10 +234,10 @@
followup for details.</li>
<li>Congestion control. Is our current design sufficient once we have
heavy use? Need to measure and tweak, or maybe overhaul.</li>
+</ul>
Drop by the #tor IRC channel at irc.oftc.net or email tor-volunteer@xxxxxxxxxxxxx if you want to help out!
-</pre>
</div><!-- #main -->
</div>
<div class="bottom" id="bottom">