From: David Stainton Date: Fri, 5 Sep 2014 00:30:19 +0000 (+0000) Subject: Fix formatting X-Git-Url: https://git.rkrishnan.org/vdrive/%22file:/somewhere?a=commitdiff_plain;h=b7b0d47e84ee4476e9374109e4e470f218acddd2;p=tahoe-lafs%2Ftahoe-lafs.git Fix formatting --- diff --git a/docs/anonymity-roadmap.rst b/docs/anonymity-roadmap.rst index c8ab49d6..56aff644 100644 --- a/docs/anonymity-roadmap.rst +++ b/docs/anonymity-roadmap.rst @@ -8,26 +8,25 @@ Anonymity Development Roadmap Development phases ================== -1. Use Tor for network connectivity and protect identity of client. +1. Use Tor for network connectivity and protect identity of client **note:** Client side is endpoint agnostic and server side has TCP endpoint support. -Dependencies ------------- -* txsocksx: get this merged upstream -->> https://github.com/david415/txsocksx/tree/endpoint_parsers_retry_socks -* foolscap#203 -* #1010 -* #517 +**Dependencies** :: + * txsocksx: get this merged upstream -->> https://github.com/david415/txsocksx/tree/endpoint_parsers_retry_socks + * foolscap#203 + * #1010 + * #517 -2. Use I2p for network connectivity and protect identity of client. +2. Use I2p for network connectivity and protect identity of client * txi2p 3. endpoint-agnostic Foolscap server side -Completing these two tickets will make Foolscap endpoint agnostic on the server side. Therefore any Twisted server endpoint/parser can be used with Foolscap :: +Completing these two tickets will make Foolscap endpoint agnostic on the server side. Therefore any Twisted server endpoint/parser can be used with Foolscap * teach twisted to serialize a listeningPort into a client endpoint descriptor - https://twistedmatrix.com/trac/ticket/7603