tor-webwml.git

@@ -990,18 +990,18 @@ meetings around the world.</li>

     Skill Level: <i>Low to Medium</i>

     <br>

     Likely Mentors: <i>intrigeri, anonym</i>

-    <p>Tor helps greatly publishing files anonymously. However, much personal

-    information can be enclosed *inside* such published files meta-data: GPS

-    coordinates, authors name and so on. Anyone who wants to anonymously

+    <p>Tor helps greatly in publishing files anonymously. However, much personal

+    information can be enclosed *inside* such published files' meta-data: GPS

+    coordinates, author's name and so on. Anyone who wants to anonymously

     publish a file can thus far too easily de-anonymize herself.</p>

-    <p>A set of tools allowing to easily inspect and cleanup meta-data in files

+    <p>A set of tools allowing users to easily inspect and clean up meta-data in files

     would benefit Tor users, and would e.g. be shipped in TAILS.</p>

     <p>A graphical user interface is a must, but library and command-line

     interfaces are most welcome so that future work can add support for

-    published files cleaning to various publishing tools, such as Desktop

+    cleaning published files to various publishing tools, such as desktop

     social networking clients and Web content management systems.</p>

-    <p>This project mostly consists in writing glue between the many existing

-    tools and libraries that provide read/write access to files meta-data. An

+    <p>This project mostly consists of writing glue between the many existing

+    tools and libraries that provide read/write access to files' meta-data. An

     extensible program design would probably be the best bet, so that support

     for other kinds of files can easily be added later.</p>

     <p>The meta-data cleaning toolkit would run at least on GNU/Linux;

@@ -1021,15 +1021,15 @@ meetings around the world.</li>

     <br>

     Likely Mentors: <i>intrigeri, anonym</i>

     <p>Data persistence is a somewhat tricky topic in a Live system context,

-    especially one explicitly designed to avoid leaving any trace of its use

-    such as TAILS.</p>

-    <p>Some real-life usecases however require to setup some kind of data

+    especially one such as TAILS, which is explicitly designed to avoid

+    leaving any trace of its use.</p>

+    <p>Some real-life use cases, however, require some kind of data

     persistence. To start with, TAILS should (carefully) support persistence of

     application-specific configurations (e.g. GnuPG keyring) and of a user

     arbitrary data store. Note that persistence in TAILS will always be opt-in

     and require encrypted storage.</p>

-    <p>The backend part work consists in improving Debian Live existing

-    persistence features to make them suit the specific TAILS context. A trust

+    <p>The backend work consists of improving Debian Live's existing

+    persistence features to make them suit the specific context of TAILS. A trust

     relationship is already established with upstream who is happy to merge our

     changes. The codebase is not that small and much refactoring is needed, so

     this really is a programming project rather than a fire'n'forget shell

@@ -1037,7 +1037,7 @@ meetings around the world.</li>

     <p>Anyone undertaking this project must be familiar with GNU/Linux, and

     preferably with Debian. Being able to (quickly learn to) write clean and

     safe programs in shell is also needed.</p>

-    <p>For more information see <a href="https://amnesia.boum.org/todo/persistence/">https://amnesia.boum.org/todo/persistence/</a></p>

+    <p>For more information, see <a href="https://amnesia.boum.org/todo/persistence/">https://amnesia.boum.org/todo/persistence/</a>.</p>

     <a id="torsocksForOSX"></a>

     <li>