# [or-cvs] r23179: {projects} improve the section titles. (projects/articles)

Andrew Lewman andrew at torproject.org
Tue Sep 14 14:51:55 UTC 2010

Author: phobos
Date: 2010-09-14 14:51:55 +0000 (Tue, 14 Sep 2010)
New Revision: 23179

Modified:
projects/articles/circumvention-features.pdf
projects/articles/circumvention-features.tex
Log:
improve the section titles.

Modified: projects/articles/circumvention-features.pdf
===================================================================
(Binary files differ)

Modified: projects/articles/circumvention-features.tex
===================================================================
--- projects/articles/circumvention-features.tex	2010-09-14 14:38:55 UTC (rev 23178)
+++ projects/articles/circumvention-features.tex	2010-09-14 14:51:55 UTC (rev 23179)
@@ -61,7 +61,7 @@
that some other tool developers may not care about), I have also tried
to include features that other tool developers consider important.

-\section{Diverse set of users}
+\section{Has a diverse set of users}

One of the simplest questions you can ask when looking at a circumvention
tool is who else uses it. A wide variety of users means that if somebody
@@ -98,7 +98,7 @@
on the other hand, if you're in Saudi Arabia and need a circumvention
tool, some otherwise useful tools are not an option for you.

-\section{Sustainable network and software development}
+\section{Provides sustainable network and software development}

If you're going to invest the time to figure out how to use a given tool,
you want to make sure it's going to be around for a while. There are
@@ -136,7 +136,7 @@
a tool uses can help you predict what problems it might encounter in
the future.

-\section{Open design}
+\section{Uses open design}

The first step to transparency and reusability of the tool's software and
design is to distribute the software (not just the client-side software,
@@ -179,7 +179,7 @@
projects and the field of circumvention development as a whole moves
forward too slowly.

-\section{Decentralized architecture}
+\section{Uses decentralized architecture}

Another feature to look for in a circumvention tool is whether its network
is centralized or decentralized. A centralized tool puts all of its users'
@@ -291,7 +291,7 @@
strangers who get to see your entire traffic profile (and link you to
it). Anybody who promises ``100\% security'' is selling something.

-\section{Fast}
+\section{Runs fast}

The next feature you might look for in a circumvention tool is speed. Some
tools tend to be consistently fast, some consistently slow, and some
@@ -319,7 +319,7 @@
downside is that the network is often overwhelmed by users doing bulk
transfer.

-\section{Easy to get the software and updates}
+\section{Makes it easy to get the software and updates}

Once a circumvention tool becomes well-known, its website is going to get
blocked. If it's impossible to get a copy of the tool itself, who cares