tor-webwml.git

1) ## translation metadata

2) # Revision: $Revision$

3) # Translation-Priority: 4-optional
4) 
5) #include "head.wmi" TITLE="Tor: Volunteer" CHARSET="UTF-8"
6) <div id="content" class="clearfix">
7)   <div id="breadcrumbs">

8)     <a href="<page index>">Home &raquo; </a>

9)     <a href="<page getinvolved/volunteer>">Volunteer</a>
10)   </div>

11)   <div id="maincol">

12)     <!-- PUT CONTENT AFTER THIS TAG -->
13)     <h1>A few things everyone can do now:</h1>
14)     <ol>
15)     <li>Please consider <a href="<page docs/tor-doc-relay>">running
16)     a relay</a> to help the Tor network grow.</li>
17)     <li>Tell your friends! Get them to run relays. Get them to run hidden
18)     services. Get them to tell their friends.</li>
19)     <li>If you like Tor's goals, please <a href="<page donate/donate>">take a moment
20)     to donate to support further Tor development</a>. We're also looking
21)     for more sponsors &mdash; if you know any companies, NGOs, agencies,
22)     or other organizations that want anonymity / privacy / communications
23)     security, let them know about us.</li>
24)     <li>We're looking for more <a href="<page about/torusers>">good examples of Tor
25)     users and Tor use cases</a>. If you use Tor for a scenario or purpose not
26)     yet described on that page, and you're comfortable sharing it with us,
27)     we'd love to hear from you.</li>
28)     </ol>

29) 

30)     <a id="Documentation"></a>
31)     <h2><a class="anchor" href="#Documentation">Documentation</a></h2>
32)     <ol>

33)     <li>Help translate the
34) <!-- web page and -->
35)     documentation into other

36)     languages. See the <a href="<page getinvolved/translation>">translation
37)     guidelines</a> if you want to help out. We especially need Arabic or
38)     Farsi translations, for the many Tor users in censored areas.</li>
39)     <li>Evaluate and document

40)     <a href="<wiki>doc/TorifyHOWTO">our

41)     list of programs</a> that can be configured to use Tor.</li>
42)     <li>We have a huge list of <a

43)     href="<wiki>doc/SupportPrograms">potentially useful

44)     programs that interface with Tor</a>. Which ones are useful in which

45)     situations? Please help us test them out and document your results.</li>
46)     </ol>

47) 

48)     <a id="Advocacy"></a>
49)     <h2><a class="anchor" href="#Advocacy">Advocacy</a></h2>
50)     <ol>

51)     <li>Monitor some of our <a
52)     href="https://lists.torproject.org/cgi-bin/mailman/listinfo">public mailing
53)     lists</a>, like <a
54)     href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk">tor-talk</a>, <a
55)     href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays">tor-relays</a>, <a
56)     href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev">tor-dev</a>, or <a
57)     href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tbb-dev">tbb-dev</a>,

58)     and summarize noteworthy changes into articles for our blog and newsletter.</li>

59)     <li>Create a presentation that can be used for various user group
60) meetings around the world.</li>

61)     <li>Create a video about the positive uses of Tor, what Tor is,
62)     or how to use it.  Some have already started on <a

63)     href="https://media.torproject.org/video/">Tor's Media server</a>,

64)     <a

65)     href="http://www.howcast.com/videos/90601-How-To-Circumvent-an-Internet-Proxy/">Howcast</a>,
66)     and <a href="http://www.youtube.com/c/thetorproject">YouTube</a>.</li>

67)     <li>Create a poster around a theme, such as "Tor for Freedom!"</li>

68)     <li>Create a t-shirt design that incorporates "<a
69)     href="https://check.torproject.org/">Congratulations! You are using
70)     Tor!</a>" in any language.</li>

71)     <li>Spread the word about Tor at a symposium or conference and use these
72)     <a href="https://media.torproject.org/misc/2015-03-tor-brochure/">Tor
73)     brochures</a> in PDF and ODG format and translated to at least ten
74)     different languages as conversation starter.</li>

75)     </ol>

76) 

77)     <a id="gsoc"></a>
78)     <h2><a class="anchor" href="#gsoc">Google Summer of Code</a></h2>
79) 
80)     <p>
81)     Tor is also taking part in this year's <a

82)     href="https://summerofcode.withgoogle.com/">Google
83)     Summer of Code</a>! To apply but you need to be either <a
84)     href="https://developers.google.com/open-source/gsoc/faq#what_are_the_eligibility_requirements_for_participation">a
85)     present student or just graduated</a>. <b>See our page for <a href="<page
86)     about/gsoc>">Google Summer of Code</a> for more information.</b>

87)     </p>
88) 

89)     <a id="Projects"></a>
90)     <h2><a class="anchor" href="#Projects">Projects</a></h2>

91) 

92)     <p>
93)     Below are a list of Tor related projects we're developing and/or
94)     maintaining. Most discussions happen on IRC so if you're interested in any
95)     of these (or you have a project idea of your own), then please <a

96)     href="<page about/contact>#irc">join us in #tor-dev</a>. Don't be shy
97)     to ask questions, and don't hesitate to ask even if the main contributors
98)     aren't active at that moment.

99)     </p>

100) 

101)     <p>
102)     For a presentation summarizing many of these projects see...
103)     </p>
104) 
105)     <div id="ecosystem_presentation">

106)       <a href="https://www.youtube.com/watch?v=fb6iqZcQsSg">Tor Ecosystem</a> (<a href="https://media.torproject.org/video/2013-11-t3am-damian-johnson.mp4">mp4</a>, <a href="https://svn.torproject.org/svn/projects/presentations/2013-11-t3am-tor-ecosystem.pdf">slides</a>)

107)     </div>
108) 
109)     <br /></br />
110) 

111)     <table id="projects">
112)       <tr>
113)         <th>Name</th>
114)         <th>Category</th>
115)         <th>Language</th>
116)         <th>Activity</th>
117)         <th>Contributors</th>
118)       </tr>

119) 

120)       <tr>
121)         <td><a href="#project-tor">Tor</a></td>
122)         <td>Core</td>
123)         <td>C</td>
124)         <td>Heavy</td>

125)         <td>nickm, athena, arma, dgoulet, asn, teor</td>

126)       </tr>

127) 

128)       <tr>

129)         <td><a href="#project-torbrowser">Tor Browser</a></td>

130)         <td>Bundle</td>

131)         <td>Javascript, XUL, Scripting</td>

132)         <td>Heavy</td>

133)         <td>mikeperry, Pearl Crescent, GeKo</td>

134)       </tr>
135) 

136)       <tr>

137)         <td><a href="#project-httpseverywhere">HTTPS Everywhere</a></td>
138)         <td>Browser Add-on</td>
139)         <td>Javascript</td>

140)         <td>Moderate</td>

141)         <td>pde, mikeperry</td>

142)       </tr>

143) 

144)       <tr>

145)         <td><a href="#project-nyx">Nyx</a></td>

146)         <td>User Interface</td>
147)         <td>Python, Curses</td>

148)         <td>Moderate</td>

149)         <td>atagar</td>
150)       </tr>

151) 

152)       <tr>

153)         <td><a href="#project-orbot">Orbot</a></td>
154)         <td>User Interface</td>
155)         <td>Java</td>

156)         <td>Moderate</td>

157)         <td>n8fr8</td>

158)       </tr>

159) 

160)       <tr>

161)         <td><a href="#project-tails">Tails</a></td>
162)         <td>OS image</td>
163)         <td>Sys Admin</td>
164)         <td>Heavy</td>
165)         <td><a href="https://tails.boum.org/">#tails</a></td>

166)       </tr>

167) 

168)       <tr>

169)         <td><a href="#project-torramdisk">tor-ramdisk</a></td>
170)         <td>OS image</td>
171)         <td>Sys Admin</td>

172)         <td>Light</td>

173)         <td>blueness</td>
174)       </tr>
175) 

176)       <tr>

177)         <td><a href="#project-torsocks">Torsocks</a></td>
178)         <td>Usability</td>
179)         <td>C</td>

180)         <td>Light</td>

181)         <td>David Goulet</td>

182)       </tr>
183) 

184)       <tr>
185)         <td><a href="#project-tormessenger">Tor Messenger</a></td>
186)         <td>Bundle</td>
187)         <td>JavaScript, XUL, Scripting</td>
188)         <td>Heavy</td>
189)         <td>arlolra, boklm, sukhe</td>
190)       </tr>
191) 

192)       <tr>

193)         <td><a href="#project-torbirdy">TorBirdy</a></td>
194)         <td>Browser Add-on</td>
195)         <td>JavaScript</td>

196)         <td>Light</td>
197)         <td>sukhe</td>

198)       </tr>

199) 

200)       <tr>

201)         <td><a href="#project-shadow">Shadow</a></td>

202)         <td>Simulator</td>

203)         <td>C, Python</td>

204)         <td>Moderate</td>

205)         <td>robgjansen</td>
206)       </tr>

207) 

208)       <tr>
209)         <td><a href="#project-chutney">Chutney</a></td>
210)         <td>Simulator</td>
211)         <td>Python</td>
212)         <td>Light</td>

213)         <td>teor</td>

214)       </tr>
215) 

216)       <tr>

217)         <td><a href="#project-stem">Stem</a></td>

218)         <td>Library</td>
219)         <td>Python</td>

220)         <td>Heavy</td>

221)         <td>atagar</td>

222)       </tr>

223) 

224)       <tr>

225)         <td><a href="#project-txtorcon">Txtorcon</a></td>
226)         <td>Library</td>
227)         <td>Python, Twisted</td>

228)         <td>Moderate</td>

229)         <td>meejah</td>
230)       </tr>

231) 

232)       <tr>
233)         <td><a href="#project-metrics-lib">metrics-lib</a></td>
234)         <td>Library</td>
235)         <td>Java</td>
236)         <td>Moderate</td>
237)         <td>karsten, iwakeh</td>
238)       </tr>
239) 

240)       <tr>

241)         <td><a href="#project-metrics">Metrics</a></td>
242)         <td>Client Service</td>
243)         <td>Java</td>

244)         <td>Heavy</td>

245)         <td>karsten, iwakeh</td>

246)       </tr>

247) 

248)       <tr>

249)         <td><a href="#project-atlas">Atlas</a></td>
250)         <td>Client Service</td>
251)         <td>JavaScript</td>

252)         <td>Light</td>

253)         <td>irl</td>

254)       </tr>

255) 

256)       <tr>

257)         <td><a href="#project-compass">Compass</a></td>
258)         <td>Client Service</td>
259)         <td>Python</td>

260)         <td>None</td>
261)         <td></td>

262)       </tr>

263) 

264)       <tr>

265)         <td><a href="#project-onionoo">Onionoo</a></td>
266)         <td>Backend Service</td>

267)         <td>Java</td>

268)         <td>Heavy</td>
269)         <td>karsten, iwakeh</td>

270)       </tr>
271) 

272)       <tr>
273)         <td><a href="#project-exitmap">ExitMap</a></td>
274)         <td>Backend Service</td>
275)         <td>Python</td>

276)         <td>None</td>

277)         <td>phw</td>
278)       </tr>
279) 

280)       <tr>
281)         <td><a href="#project-doctor">DocTor</a></td>
282)         <td>Backend Service</td>
283)         <td>Python</td>

284)         <td>Light</td>

285)         <td>atagar</td>
286)       </tr>
287) 

288)       <tr>

289)         <td><a href="#project-gettor">GetTor</a></td>
290)         <td>Client Service</td>
291)         <td>Python</td>

292)         <td>None</td>

293)         <td>ilv</td>

294)       </tr>

295) 

296)       <tr>

297)         <td><a href="#project-torcheck">TorCheck</a></td>
298)         <td>Client Service</td>

299)         <td>Go</td>

300)         <td>None</td>

301)         <td>Arlo</td>

302)       </tr>

303) 

304)       <tr>

305)         <td><a href="#project-bridgedb">BridgeDB</a></td>
306)         <td>Backend Service</td>
307)         <td>Python</td>

308)         <td>Light</td>

309)         <td>isis</td>

310)       </tr>

311) 

312)       <tr>

313)         <td><a href="#project-ooni-probe">Ooni Probe</a></td>

314)         <td>Scanner</td>
315)         <td>Python</td>

316)         <td>Heavy</td>

317)         <td>hellais, aagbsn</td>

318)       </tr>
319) 

320)       <tr>
321)         <td><a href="#project-torps">TorPS</a></td>
322)         <td>Backend Service</td>
323)         <td>Python</td>

324)         <td>None</td>

325)         <td>Aaron Johnson</td>
326)       </tr>
327) 

328)       <tr>

329)         <td><a href="#project-torflow">TorFlow</a></td>
330)         <td>Backend Service</td>
331)         <td>Python</td>

332)         <td>None</td>

333)         <td>aagbsn</td>

334)       </tr>

335) 

336)       <tr>
337)         <td><a href="#project-collector">CollecTor</a></td>
338)         <td>Backend Service</td>
339)         <td>Java</td>

340)         <td>Moderate</td>

341)         <td>karsten, iwakeh</td>
342)       </tr>
343) 
344)       <tr>
345)         <td><a href="#project-exonerator">ExoneraTor</a></td>
346)         <td>Client Service</td>
347)         <td>Java</td>
348)         <td>Light</td>
349)         <td>karsten, iwakeh</td>
350)       </tr>

351) 
352)       <tr>
353)         <td><a href="#project-anonbib">Anonbib</a></td>
354)         <td>Website</td>
355)         <td>Python</td>
356)         <td>None</td>
357)         <td>arma, nickm</td>
358)       </tr>

359)     </table>

360) 

361)     <sub>
362)     * Project is still in an alpha state.
363)     </sub>

364) 

365)     <br /><br />

366) 

367)     <a id="project-tor"></a>
368)     <h3>Tor (<a href="https://gitweb.torproject.org/tor.git">code</a>, <a

369)     href="https://trac.torproject.org/projects/tor/report/12">bug

370)     tracker</a>)</h3>

371) 

372)     <p>
373)     Central project, providing the core software for using and participating in
374)     the Tor network. Numerous people contribute to the project to varying
375)     extents, but the chief architects are Nick Mathewson and Roger Dingledine.
376)     </p>

377) 

378)     <p>
379)     <b>Project Ideas:</b><br />

380)     <i><a href="#improveHiddenServices">Help improve Tor hidden services</a></i><br />
381)     <i><a href="#torFuzzing">Fuzzing coverage of Tor</a></i><br />
382)     <i><a href="#relayCryptoParallelism">Relay crypto parallelism</a></i><br />
383)     <i><a href="#anonymousLocalCountStatistics">Anonymous local count statistics</a></i><br />
384)     <i><a href="#improveSocks5Variant">Improved SOCKS5 variant</a></i><br />
385)     <i><a href="#hiddenServiceCryptoParallelism">Hidden service crypto parallelism</a></i><br />
386)     <i><a href="#supportAllDNS">Support all kinds of DNS in Tor</a></i><br />
387)     <i><a href="#improveIpv6Support">Improve IPv6 support</a></i>

388)     </p>

389) 

390)     <a id="project-torbrowser"></a>

391)     <h3><a href="<page projects/torbrowser>">Tor Browser</a> (<a

392)     href="https://gitweb.torproject.org/tor-browser.git">code</a>, <a

393)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Applications%2FTor+Browser&component=Applications%2FTorbutton&component=Applications%2FTor+Launcher&component=Applications%2FTor+bundles%2Finstallation&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&order=priority">bug

394)     tracker</a>, <a href="https://www.torproject.org/projects/torbrowser/design/">design doc</a>)</h3>
395) 

396)     <p>

397)     Tor Browser is an easy-to-use, portable package of Tor, HTTPS-Everywhere,
398)     NoScript, TorLauncher, Torbutton, and a Firefox fork, all  preconfigured

399)     to work together out of
400)     the box. The modified copy of Firefox aims to resolve the

401)     privacy and security issues in mainline version.

402)     </p>

403) 

404)     <p>
405)     <b>Project Ideas:</b><br />

406)     <i><a href="#feedbackExtension">Feedback Extension for Tor Browser</a></i><br />

407)     <i><a href="#torBrowserCrashReport">Crash Reporter for Tor Browser</a></i><br />
408)     <i><a href="#fasterTorBrowser">Make Tor Browser Faster</a></i>

409)     </p>
410) 

411)     <a id="project-httpseverywhere"></a>
412)     <h3><a href="https://www.eff.org/https-everywhere">HTTPS Everywhere</a> (<a
413)     href="https://gitweb.torproject.org/https-everywhere.git">code</a>, <a
414)     href="https://trac.torproject.org/projects/tor/report/19">bug

415)     tracker</a>)</h3>

416) 

417)     <p>

418)     HTTPS Everywhere is a Firefox and Chrome extension that encrypts
419)     your communications with many major websites, making your browsing
420)     more secure.

421)     </p>

422) 

423)     <a id="project-nyx"></a>

424)     <h3><a href="https://nyx.torproject.org/">Nyx</a> (<a

425)     href="https://gitweb.torproject.org/nyx.git">code</a>, <a

426)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Core+Tor%2FNyx&order=priority">bug

427)     tracker</a>)</h3>

428) 

429)     <p>

430)     Nyx (previously <i>arm</i>) is a terminal status monitor for Tor

431)     intended for command-line aficionados, ssh connections, and anyone with a
432)     tty terminal. This works much like top does for system usage, providing
433)     real time statistics for bandwidth, resource usage, connections, and quite
434)     a bit more.

435)     </p>

436) 

437)     <a id="project-orbot"></a>
438)     <h3><a href="https://guardianproject.info/apps/orbot/">Orbot</a> (<a

439)     href="https://gitweb.torproject.org/orbot.git">code</a>, <a

440)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Applications%2FOrbot&order=priority">bug

441)     tracker</a>)</h3>

442) 
443)     <p>

444)     Provides Tor on the Android platform. The project is under active
445)     development, updates to latest Tor releases, and working to stay up to

446)     date with all changes in Android and mobile threats.

447)     </p>
448) 
449)     <a id="project-tails"></a>
450)     <h3><a href="https://tails.boum.org/">The Amnesic Incognito Live System</a> (<a

451)     href="https://git-tails.immerda.ch/tails/">code</a>, <a
452)     href="https://labs.riseup.net/code/projects/tails">bug

453)     tracker</a>, <a href="https://tails.boum.org/doc/">documentation</a>, <a

454)     href="https://tails.boum.org/contribute/design/">design</a>, <a

455)     href="https://tails.boum.org/contribute/">contribute</a>)</h3>

456) 
457)     <p>
458)     The Amnesic Incognito Live System is a live CD/USB distribution
459)     preconfigured so that everything is safely routed through Tor and leaves no
460)     trace on the local system. This is a merger of the Amnesia and <a

461)     href="https://web.archive.org/web/20080512054152/http://anonymityanywhere.com/incognito/">Incognito</a> projects,

462)     and still under very active development.
463)     </p>
464) 

465)     <a id="project-torramdisk"></a>
466)     <h3><a href="http://opensource.dyc.edu/tor-ramdisk">Tor-ramdisk</a> (<a

467)     href="https://gitweb.torproject.org/tor-ramdisk.git">code</a>, <a

468)     href="http://opensource.dyc.edu/tor-ramdisk-documentation">documentation</a>)</h3>

469) 
470)     <p>

471)     Tor-ramdisk is a uClibc-based micro Linux distribution whose sole
472)     purpose is to securely host a Tor server purely in RAM.

473)     </p>
474) 

475)     <a id="project-torsocks"></a>

476)     <h3>Torsocks (<a

477)     href="https://gitweb.torproject.org/torsocks.git">code</a>, <a

478)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Core+Tor%2FTorsocks&order=priority">bug

479)     tracker</a>)</h3>
480) 

481)     <p>

482)     Utility for adapting other applications to work with Tor. Development has
483)     slowed and compatibility issues remain with some platforms, but it's
484)     otherwise feature complete.

485)     </p>

486) 

487)     <a id="project-tormessenger"></a>
488)     <h3><a href="https://trac.torproject.org/projects/tor/wiki/doc/TorMessenger">Tor Messenger</a> (<a
489)     href="https://gitweb.torproject.org/tor-messenger-build.git">code</a>, <a

490)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=merge_ready&status=needs_information&status=needs_review&status=needs_revision&status=new&status=reopened&component=Applications%2FTor+Messenger&order=priority">bug tracker</a>)</h3>

491) 
492)     <p>
493)     Tor Messenger is a cross-platform chat program that aims to be secure by default and sends all of its traffic over Tor.
494)     </p>
495) 

496)     <a id="project-torbirdy"></a>
497)     <h3>TorBirdy (<a

498)     href="https://gitweb.torproject.org/torbirdy.git">code</a>, <a

499)     href="https://trac.torproject.org/projects/tor/wiki/torbirdy/dev">bug
500)     tracker</a>)</h3>

501) 

502)     <p>
503)     TorBirdy is Torbutton for Thunderbird and related Mozilla mail clients.
504)     </p>

505) 

506)     <a id="project-shadow"></a>

507)     <h3><a href="http://shadow.github.io/">Shadow</a> (<a

508)     href="https://github.com/shadow">code</a>, <a
509)     href="https://github.com/shadow/shadow/issues">bug
510)     tracker</a>)</h3>

511) 

512)     <p>
513)     Shadow is a discrete-event network simulator that runs the real
514)     Tor software as a plug-in. Shadow is open-source software that enables
515)     accurate, efficient, controlled, and repeatable Tor experimentation.

516)     For another simulator, see <a

517)     href="https://crysp.uwaterloo.ca/software/exptor/">ExperimenTor</a>.

518)     </p>

519) 

520)     <a id="project-chutney"></a>
521)     <h3>Chutney (<a href="https://gitweb.torproject.org/chutney.git">code</a>,
522)     <a href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_information&status=needs_review&status=needs_revision&status=new&status=reopened&component=Core+Tor%2FChutney&order=priority">bug
523)     tracker</a>)</h3>
524) 
525)     <p>
526)     Integration test suite that spawns a local tor network, checking the
527)     interactions of its components.
528)     </p>
529) 

530)     <a id="project-stem"></a>

531)     <h3><a href="https://stem.torproject.org/">Stem</a> (<a

532)     href="https://gitweb.torproject.org/stem.git">code</a>, <a

533)     href="https://trac.torproject.org/projects/tor/wiki/doc/stem/bugs">bug

534)     tracker</a>)</h3>

535) 

536)     <p>

537)     Python controller library for scripts and controller applications using
538)     Tor.

539)     </p>

540) 

541)     <p>
542)     <b>Project Ideas:</b><br />
543)     <i><a href="#stemDescriptors">Stem Descriptors</a></i>
544)     </p>
545) 

546)     <a id="project-txtorcon"></a>

547)     <h3><a href="https://txtorcon.readthedocs.io/en/latest/">Txtorcon</a> (<a

548)     href="https://github.com/meejah/txtorcon">code</a>, <a

549)     href="https://github.com/meejah/txtorcon/issues">bug tracker</a>)</h3>

550) 

551)     <p>
552)     Twisted-based asynchronous Tor control protocol implementation. Includes
553)     unit-tests, examples, state-tracking code and configuration abstraction.
554)     Used by OONI and APAF.
555)     </p>

556) 

557)     <a id="project-metrics-lib"></a>
558)     <h3>metrics-lib
559)     (<a href="https://gitweb.torproject.org/metrics-lib.git">code</a>,
560)     <a href="https://trac.torproject.org/projects/tor/query?status=!closed&component=Metrics%2Fmetrics-lib&order=priority">bug tracker</a>)</h3>
561) 
562)     <p>metrics-lib is a Java library that processes Tor network data
563)     provided by <a href="#project-collector">CollecTor</a> or from other
564)     sources.</p>
565) 

566)     <a id="project-metrics"></a>

567)     <h3><a href="https://metrics.torproject.org/">Metrics</a> (<a

568)     href="https://gitweb.torproject.org/metrics-web.git">web</a>)</h3>

569) 

570)     <p>
571)     Processing and analytics of consensus data, provided to users via the
572)     metrics portal. This has been under active development for several years by

573)     Karsten Loesing.

574)     </p>

575) 

576)     <a id="project-atlas"></a>
577)     <h3><a href="https://atlas.torproject.org/">Atlas</a> (<a
578)     href="https://gitweb.torproject.org/atlas.git">code</a>)</h3>

579) 

580)     <p>
581)     Atlas is a web application to discover Tor relays and bridges. It provides
582)     useful information on how relays are configured along with graphics about

583)     their past usage.

584)     </p>

585) 

586)     <p>

587)     This is the spiritual successor to <a
588)     href="https://gitweb.torproject.org/torstatus.git">TorStatus</a>, the <a

589)     href="https://svn.torproject.org/svn/torstatus/trunk/">original

590)     codebase</a> for which was written in PHP, and rewritten by students from

591)     Wesleyan as Django. If you dig into this space then also check out <a
592)     href="http://globe.rndm.de/">Globe</a>, another similar site that's since
593)     been discontinued.

594)     </p>
595) 

596)     <a id="project-compass"></a>
597)     <h3><a href="https://compass.torproject.org/">Compass</a> (<a
598)     href="https://gitweb.torproject.org/compass.git">code</a>, <a

599)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Metrics%2FCompass&order=priority">bug

600)     tracker</a>)</h3>

601) 

602)     <p>
603)     Compass is a web and command line application that filters and
604)     aggregates the Tor relays based on various attributes.
605)     </p>

606) 
607)     <a id="project-onionoo"></a>

608)     <h3><a href="https://onionoo.torproject.org/">Onionoo</a> (<a
609)     href="https://gitweb.torproject.org/onionoo.git">code</a>,

610)     <a href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Metrics%2FOnionoo&order=priority">bug tracker</a>)</h3>

611) 
612)     <p>
613)     Onionoo is a JSON based protocol to learn information about currently
614)     running Tor relays and bridges.
615)     </p>
616) 

617)     <a id="project-exitmap"></a>
618)     <h3><a href="http://www.cs.kau.se/philwint/spoiled_onions/">ExitMap</a> (<a
619)     href="https://github.com/NullHypothesis/exitmap">code</a>, <a
620)     href="https://github.com/NullHypothesis/exitmap/issues">bug tracker</a>)</h3>
621) 
622)     <p>

623)     Scanner for the Tor network by Philipp Winter to detect malicious and
624)     misconfigured exits. For more information about how it works see his <a
625)     href="http://www.cs.kau.se/philwint/spoiled_onions/pets2014.pdf">Spoiled

626)     Onions</a> research paper.
627)     </p>
628) 

629)     <a id="project-doctor"></a>
630)     <h3>DocTor (<a
631)     href="https://gitweb.torproject.org/doctor.git">code</a>, <a

632)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Core+Tor%2FDocTor&order=priority">bug

633)     tracker</a>)</h3>
634) 
635)     <p>
636)     DocTor is a notification service that monitors newly published descriptor
637)     information for issues. This is primarily a service to help the tor
638)     directory authority operators, but it also checks for a handful of other
639)     issues like sybil attacks.
640)     </p>
641) 

642)     <a id="project-weather"></a>

643)     <h3><a href="https://trac.torproject.org/projects/tor/wiki/org/roadmaps/Weather">Weather</a> (<a

644)     href="https://gitweb.torproject.org/weather.git">code</a>, <a

645)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Metrics%2FTor+Weather&order=priority">bug

646)     tracker</a>)</h3>

647) 

648)     <p>
649)     Provides automatic notification to subscribed relay operators when their
650)     relay's unreachable. This underwent a rewrite by the <a
651)     href="http://hfoss.wesleyan.edu/">Wesleyan HFOSS team</a>, which went live
652)     in early 2011.
653)     </p>

654) 

655)     <a id="project-gettor"></a>

656)     <h3><a href="https://trac.torproject.org/projects/tor/wiki/org/roadmaps/GetTor">GetTor</a> (<a

657)     href="https://gitweb.torproject.org/gettor.git">code</a>, <a

658)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Applications%2FGetTor&order=priority">bug

659)     tracker</a>)</h3>

660) 

661)     <p>
662)     E-mail autoresponder providing Tor's packages over SMTP. This has been
663)     relatively unchanged for quite a while.
664)     </p>

665) 

666)     <a id="project-torcheck"></a>

667)     <h3><a href="https://trac.torproject.org/projects/tor/wiki/org/roadmaps/TorCheck">TorCheck</a> (<a

668)     href="https://gitweb.torproject.org/check.git">code</a>, <a

669)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Applications%2FTor+Check&order=priority">bug

670)     tracker</a>)</h3>

671) 

672)     <p>

673)     Site for determining if the visitor is using Tor or not.

674)     </p>

675) 

676)     <a id="project-bridgedb"></a>

677)     <h3><a href="https://pythonhosted.org/bridgedb/">BridgeDB</a> (<a

678)     href="https://gitweb.torproject.org/bridgedb.git">code</a>, <a

679)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Obfuscation%2FBridgeDB&order=priority">bug

680)     tracker</a>)</h3>

681) 

682)     <p>
683)     Backend bridge distributor, handling the various pools they're distributed
684)     in. This was actively developed until Fall of 2010.
685)     </p>

686) 
687)     <a id="project-ooni-probe"></a>

688)     <h3><a href="https://ooni.torproject.org/">Ooni Probe</a> (<a

689)     href="https://github.com/TheTorProject/ooni-probe/">code</a>, <a
690)     href="https://github.com/TheTorProject/ooni-probe/issues">bug

691)     tracker</a>)</h3>
692) 
693)     <p>
694)     Censorship scanner, checking your local connection for blocked or modified
695)     content.
696)     </p>
697) 

698)     <a id="project-torps"></a>
699)     <h3>TorPS</a> (<a href="https://github.com/torps/torps">code</a>)</h3>
700) 
701)     <p>
702)     The Tor Path Simulator (TorPS) is a tool for efficiently simulating
703)     path selection in Tor. It chooses circuits and assigns user streams to
704)     those circuits in the same way that Tor does. TorPS is fast enough to
705)     perform thousands of simulations over periods of months.
706)     </p>
707) 

708)     <a id="project-torflow"></a>

709)     <h3><a href="https://trac.torproject.org/projects/tor/wiki/org/roadmaps/TorFlow">TorFlow</a> (<a

710)     href="https://gitweb.torproject.org/torflow.git">code</a>, <a

711)     href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Metrics%2FTorflow&order=priority">bug

712)     tracker</a>)</h3>

713) 

714)     <p>
715)     Library and collection of services for actively monitoring the Tor network.
716)     These include the Bandwidth Scanners (measuring throughput of relays) and
717)     SoaT (scans for malicious or misconfigured exit nodes). SoaT was last
718)     actively developed in the Summer of 2010, and the Bandwidth Scanners a few
719)     months later. Both have been under active use since then, but development
720)     has stopped.
721)     </p>

722) 

723)     <a id="project-collector"></a>
724)     <h3><a href="https://collector.torproject.org/">CollecTor</a>
725)     (<a href="https://gitweb.torproject.org/collector.git">code</a>,
726)     <a href="https://trac.torproject.org/projects/tor/query?status=!closed&component=Metrics%2FCollecTor&order=priority">bug tracker</a>)</h3>
727) 
728)     <p>CollecTor is the Tor network data archive that powers other
729)     services like <a href="#project-metrics">Metrics</a> and
730)     <a href="#project-onionoo">Onionoo</a>.</p>
731) 
732)     <a id="project-exonerator"></a>
733)     <h3><a href="https://exonerator.torproject.org/">ExoneraTor</a>
734)     (<a href="https://gitweb.torproject.org/exonerator.git">code</a>,
735)     <a href="https://trac.torproject.org/projects/tor/query?status=!closed&component=Metrics%2FExoneraTor&order=priority">bug tracker</a>)</h3>
736) 
737)     <p>ExoneraTor is a service that answers the question whether there was
738)     a Tor relay running on a given IP address on a given date.</p>
739) 

740)     <a id="project-anonbib"></a>
741)     <h3><a
742)     href="http://freehaven.net/anonbib/">Anonymity Bibliography</a> (<a
743)     href="https://gitweb.torproject.org/anonbib.git">code</a>)</h3>
744) 
745)     <p>
746)     Anonbib is a list of important papers in the field of anonymity. It's
747)     also a set of scripts to generate the website from Latex (bibtex). If
748)     we're missing any important papers, please let us know!
749)     </p>
750) 

751)     <a id="Coding"></a>
752)     <a id="Summer"></a>

753)     <h2><a class="anchor" href="#Coding">Project Ideas</a></h2>

754) 

755)     <p>

756)     You may find some of these projects to be good ideas for <a href="<page

757)     about/gsoc>">Google Summer of Code</a>. We have labelled each idea with
758)     which of our <a href="<page about/corepeople>">core developers</a> would be
759)     good mentors. If one or more of these ideas looks promising to you, please
760)     <a href="<page about/contact>">contact us</a> to discuss your plans rather
761)     than sending blind applications. You may also want to propose your own
762)     project idea &mdash; which often results in the best applications.

763)     </p>

764) 

765)     <ol>

766) 

767)     <a id="improveHiddenServices"></a>
768)     <li>
769)     <b>Help improve Tor hidden services</b>
770)     <br>

771)     Language: <i>C</i>

772)     <br>

773)     Likely Mentors: <i>George (asn), David Goulet (dgoulet)</i>

774)     <br><br>

775)     <p>

776) The hidden services team is busy implementing <a
777) href="https://gitweb.torproject.org/torspec.git/tree/proposals/224-rend-spec-ng.txt">proposal
778) 224</a> but we are always open to mentoring fun and exciting hidden
779) service projects.

780)     </p>
781) 
782)     <p>

783) In the past, we've mentored a wide variety of projects related to hidden
784) services, ranging from <a
785) href="https://lists.torproject.org/pipermail/tor-dev/2016-April/010832.html">onion
786) search engines</a>, <a
787) href="https://lists.torproject.org/pipermail/tor-talk/2015-May/037966.html">to
788) scaling techniques for hidden services</a>,
789) and also various approaches
790) of making onion services more <a
791) href="https://lists.torproject.org/pipermail/tor-dev/2012-June/003588.html">usable</a>
792) <a href="https://lists.torproject.org/pipermail/tor-dev/2015-May/008826.html">by
793) common people</a>.

794)     </p>
795) 
796)     <p>

797) Let us know if you have a project you would like to work on, or check
798) our proposals and technical documents for <a
799) href="https://lists.torproject.org/pipermail/tor-dev/2016-October/011514.html">various</a>
800) ideas.

801)     </p>
802)     </li>
803) 

804)     <a id="torFuzzing"></a>
805)     <li>
806)     <b>Fuzzing coverage of Tor</b>
807)     <br>
808)     Likely Mentors: <i>Nick (nickm), ahf, teor</i>
809)     <br><br>
810)     <p>
811) Starting in 0.3.0.x, Tor supports a few fuzzing systems to check our
812) code for bugs.  But as of now, we only support a few possible entry
813) points to Tor.  It would be great to add fuzzing support for more of
814) our codebase -- ideally to include our whole network-facing interface.
815) That way, we could find more bugs in our code faster, and fix them
816) before they can get out of hand.
817)     </p>
818) 
819)     <p>
820) This won't be so easy, however: to fuzz effectively, we need to
821) refactor or mock the target function so that it doesn't change any
822) global state, or verify any signatures, or take too long to run.  With
823) lots of our network code, that's not so easy.  Make sure you
824) understand how our mocking system works, and what the challenges are,
825) before you apply for this one.
826)     </p>
827)     </li>
828) 
829)     <a id="relayCryptoParallelism"></a>
830)     <li>
831)     <b>Relay crypto parallelism</b>
832)     <br>
833)     Likely Mentors: <i>Isis, Nick (nickm)</i>
834)     <br><br>
835)     <p>
836) Tor relays spend a lot of time encrypting and decrypting relay
837) traffic, doing SHA1 and AES-CTR operations.  But right now, all of
838) this is done in the main thread!  It would be cool to split this
839) across multiple cores instead.
840)     </p>
841) 
842)     <p>
843) This won't be so easy though.  The code today is written to expect
844) immediate results from its encryption operations, so you would need to
845) do some pretty tricky refactoring in order get performance and
846) correctness here.  Make sure you understand how circuit crypto is
847) invoked today, and what the challenges are, before you apply for this
848) one.
849)     </p>
850) 
851)     <p>
852) For more information <a href="https://trac.torproject.org/projects/tor/ticket/1749">see its ticket</a>.
853)     </p>
854)     </li>
855) 
856)     <a id="anonymousLocalCountStatistics"></a>
857)     <li>
858)     <b>Anonymous local count statistics</b>
859)     <br>
860)     Likely Mentors: <i>Nick (nickm), teor</i>
861)     <br><br>
862)     <p>
863) There are some places in Tor where we count things (like distinct IPs)
864) to later report anonymized statistics.  But if the local Tor instance
865) were compromised, this data would be exposed.  There are statistical
866) methods which insteasd allow us to record this data in a way that's
867) already anonymous, before we ever summarize it.  Interested?
868)     </p>
869) 
870)     <p>
871) For more information <a href="https://trac.torproject.org/projects/tor/ticket/7532">see its ticket</a>.
872)     </p>
873)     </li>
874) 
875)     <a id="improveSocks5Variant"></a>
876)     <li>
877)     <b>Improved SOCKS5 variant</b>
878)     <br>
879)     Likely Mentors: <i>Nick (nickm), David Goulet (dgoulet)</i>
880)     <br><br>
881)     <p>
882) In proposal 229, we describe a bunch of additional SOCKS extensions
883) that Tor-aware applications could use to get more fine-grained control
884) over how Tor handles their streams.  It would be cool to implement
885) this!  If there's time remaining, you might want to add support to one
886) or more applications.  Or maybe to torsocks?
887)     </p>
888) 
889)     <p>
890) For more information <a href="https://trac.torproject.org/projects/tor/ticket/12456">see its ticket</a>.
891)     </p>
892)     </li>
893) 
894)     <a id="hiddenServiceCryptoParallelism"></a>
895)     <li>
896)     <b>Hidden service crypto parallelism</b>
897)     <br>
898)     Likely Mentors: <i>Nick (nickm), David Goulet (dgoulet)</i>
899)     <br><br>
900)     <p>
901) Hidden services, hidden service clients, hidden service directories,
902) and introduction points all need to do a few public-key operations as
903) they operate.  But right now, these operations are all done on the
904) main thread.  It would be good to have these run across multiple cores.
905)     </p>
906) 
907)     <p>
908) This could probably be done in a way similar to how we currently hand
909) circuit extension handshakes in onion.c and cpuworker.c, but we'd need
910) to extend the state machine for hidden services to add an additional
911) state.  It could help hidden services operate much more efficiently.
912)     </p>
913) 
914)     <p>
915) For more information <a href="https://trac.torproject.org/projects/tor/ticket/13738">see its ticket</a>.
916)     </p>
917)     </li>
918) 
919)     <a id="supportAllDNS"></a>
920)     <li>
921)     <b>Support all kinds of DNS in Tor</b>
922)     <br>
923)     Likely Mentors: <i>Nick (nickm), George (asn)</i>
924)     <br><br>
925)     <p>
926) Right now Tor can query for the kind of DNS information you'd find in
927) A records, AAAA records, and PTR records.  It would be neat to be able
928) to support more general DNS queries to allow things like MX loopups,
929) DNSSEC lookups, and so on.  We have a design proposal (number 219) for
930) this, but it might need some clean-up.
931)     </p>
932) 
933)     <p>
934) For more information <a href="https://trac.torproject.org/projects/tor/ticket/7829">see its ticket</a>.
935)     </p>
936)     </li>
937) 
938)     <a id="improveIpv6Support"></a>
939)     <li>
940)     <b>Improve IPv6 support</b>
941)     <br>
942)     Likely Mentors: <i>ahf, teor</i>
943)     <br><br>
944)     <p>
945) Tor works over IPv6, but require some manual configuration.
946) Clients and relays could automatically detect IPv6 availability,
947) and configure themselves appropriately. Implementing a
948) "happy eyeballs"-like algorithm is a challenge in an anonymity
949) network: are you up for it?
950)     </p>
951) 
952)     <ul>
953)       <li><a href="https://trac.torproject.org/projects/tor/ticket/6939">Missing IPv6 ORPort reachability check</a></li>
954)       <li><a href="https://trac.torproject.org/projects/tor/ticket/4847">Bridges binding only to an IPv6 address doesn't work</a></li>
955)       <li><a href="https://trac.torproject.org/projects/tor/ticket/5940">Figure out own IPv6 address</a></li>
956)       <li><a href="https://trac.torproject.org/projects/tor/ticket/17011">Teach chutney to verify over IPv6</a></li>
957)     </ul>
958) 
959)     <p>
960) For more information <a href="https://trac.torproject.org/projects/tor/ticket/17811">see its ticket</a>.
961)     </p>
962)     </li>
963) 

964)     <a id="feedbackExtension"></a>
965)     <li>
966)     <b>Feedback Extension for Tor Browser</b>
967)     <br>
968)     Likely Mentors: <i>Nima (mrphs)</i>, <i>Sukhbir (sukhe)</i>
969)     <p>
970)     Design and implement an extension for Tor Browser that can be used to gather
971)     end-user UI/UX feedback on an opt-in basis. While the design and
972)     implementation is left as an exercise for the applicant (and also serves as
973)     the qualification task), examples of the information we are looking to gather
974)     can include troubleshooting network connectivity issues, testing the various
975)     pluggable transports, or gathering information about the network of the users.
976)     </p>
977) 
978)     <p>
979)     Please propose the extension design in a way that the information is strictly
980)     on an opt-in basis and scrubs any information that can be used to identify a
981)     user, and also come up with a way to send the gathered information to a
982)     central server, whether to an onion address (if the user has Tor running), or
983)     otherwise. To start with, we are looking to gather only text as part of the
984)     feedback process.
985)     </p>
986)     </li>
987) 
988)     <a id="torBrowserCrashReport"></a>
989)     <li>
990)     <b>Crash Reporter for Tor Browser</b>
991)     <br>
992)     Likely Mentors: <i>Tom Ritter (tjr)</i>, <i>Georg (GeKo)</i>
993)     <p>
994)     Currently Tor Browser disables the Crash Reporter. We would like to
995)     build it reproducible, enable it, and configure it to report crashes
996)     containing non-detailed and impersonal information to Tor, on a .onion
997)     submission platform that would allow us to view and explore the
998)     crashes.
999)     </p>
1000) 
1001)     <p>
1002)     The project will entail enabling the Crash Report on Tor Browser and
1003)     creating a backend to receive reports from it. Once created, the crash
1004)     reporter data will be analyzed and modified to fit Tor's requirements
1005)     for personal data collection. As time permits, we will update the
1006)     build system to ensure the crash reporter is built reproducibly and
1007)     add data analysis tools for the crash report database to visualize top
1008)     crashers and similar statistics.
1009)     </p>
1010)     </li>
1011) 
1012)     <a id="fasterTorBrowser"></a>
1013)     <li>
1014)     <b>Make Tor Browser Faster</b>
1015)     <br>
1016)     Likely Mentors: <i>Tom Ritter (tjr)</i>, <i>Georg (GeKo)</i>
1017)     <p>
1018)     This project will enable and take advantage of HTTP/2, the Alt-Srv
1019)     header, and tor's new single hop .onion mode to enable websites to
1020)     transparently move their traffic to a .onion address. In addition to
1021)     improvements in security, we will benchmark page load and paint times
1022)     under normal HTTP/1.1, HTTP/2, and when taking advantage of features
1023)     such as Server Push.
1024)     </p>
1025)     </li>
1026) 

1027)     <a id="stemDescriptors"></a>
1028)     <li>
1029)     <b>Stem Descriptors</b>
1030)     <br>
1031)     Language: <i>Python</i>
1032)     <br>

1033)     Likely Mentors: <i>Damian Johnson (atagar), Philipp Winter (phw)</i>

1034)     <p>
1035)     <a href="https://stem.torproject.org/">Stem</a> is a Python library for working with tor. With it you can build applications on tor as well as learn information about the relay network. This project concerns this second capability.
1036)     </p>
1037) 
1038)     <p>
1039)     Information about relays are published hourly in documents called <a href="https://stem.torproject.org/tutorials/mirror_mirror_on_the_wall.html">descriptors</a>. With Stem you can download, parse, and validate all kinds of descriptor documents.
1040)     </p>
1041) 
1042)     <p>
1043)     Ideas welcome! You're encouraged to brainstorm improvements we can make to this space but here's a few to get you started...
1044)     </p>
1045) 
1046)   <ul>
1047)     <li><p><b><a href="https://trac.torproject.org/projects/tor/ticket/11045">Validate signatures in the consensus</a></b>. Stem has the ability to validate cryptographic signatures in several descriptor types but not the consensus.</p></li>
1048)     <li><p><b><a href="https://trac.torproject.org/projects/tor/ticket/21086">Migrate from pycrypto to a supported library</a></b>. Stem presently uses pycrypto for signature validation but it's no longer maintained. We should evaluate options and move to whatever whavever the cool kids are using nowadays.</p></li>
1049)     <li><p><b><a href="https://trac.torproject.org/projects/tor/ticket/18856">Retrieve descriptors over tor's ORPort</a></b>. Tor relays commonly provide two ports, an <b>ORPort</b> which is used by clients and a <b>DirPort</b> which is obsolete nowadays but in the past was used by tor to download descriptors. Stem still uses tor's DirPort to retrieve descriptors, but it would be neat if we could download from the ORPort instead.</p>
1050)       <p>This requires implementing part of tor's communication protocol. Depending how complicated this is it might be neat to expand this task to allow the full construction of circuits, allowing client usage of tor without the C executable. Keep in mind though that this later bit hasn't been investigated and might be a pipe dream. ;P</p></li>
1051)     <li><p><b>Improve performance of reading descriptors</b>. Stem <a href="https://stem.torproject.org/tutorials/mirror_mirror_on_the_wall.html#are-there-any-other-parsing-libraries">isn't the only descriptor parsing library</a> and sadly is the slowest. Tricks like lazy loading have substantially improved our performance but no doubt a dedicated effort to profile Stem would find more low hanging fruit.</p></li>
1052)   </ul>
1053) 
1054) 
1055)     <p>
1056)     <b>As part of applying for this project please get your hands wet with the codebase by contributing some patches for <a href="https://stem.torproject.org/faq.html#how-do-i-get-started">Stem</a>!</b>
1057)     </p>
1058)     </li>
1059) 

1060)     <a id="ahmiaSearch"></a>
1061)     <li>
1062)     <b>Ahmia - Hidden Service Search</b>
1063)     <br>
1064)     Language: <i>Python, Django</i>
1065)     <br>
1066)     Likely Mentors: <i>Juha Nurmi (numes), George (asn)</i>
1067)     <p>
1068)     Ahmia is open-source search engine software for Tor hidden service deep
1069)     dark web sites. You can test the running search engine at ahmia.fi. For
1070)     more information see our <a
1071)     href="https://blog.torproject.org/category/tags/ahmiafi">blog post about
1072)     Ahmia's GSoC2014 development</a>.
1073)     </p>
1074) 
1075)     <p>
1076)     Ahmia is a working search engine that indexes, searches, and catalogs
1077)     content published on Tor Hidden Services. Furthermore, it is an environment
1078)     to share meaningful insights, statistics, insights, and news about the Tor
1079)     network itself. In this context, there is a lot of work to do.
1080)     </p>
1081) 
1082)     <p>
1083)     The Ahmia web service is written using the Django web framework. As a
1084)     result, the server-side language is Python. On the client-side, most of the
1085)     pages are plain HTML. There are some pages that require JavaScript, but the
1086)     search itself works without client-side JavaScript.
1087)     </p>
1088) 
1089)     <p>
1090)     There are several possible directions for this project, including...
1091)     </p>
1092) 
1093)     <ol>
1094)       <li>Automate blacklisting (very important)<br />
1095)         <ul>
1096)           <li>Fetch a list of child abuse media sites</li>
1097)           <li>Remove these sites from the search results</li>
1098)         </ul>
1099)       </li>
1100)       <li>Add hidden services funtion (very important)<br />
1101)         <ul>
1102)           <li>You can add onions using HTML form</li>
1103)           <li>Call the crawler immidiately when a new site is added</li>
1104)         </ul>
1105)       </li>
1106)       <li>Elasticsearch<br />
1107)         <ul>
1108)           <li>Must be updated to 5.X.X sooner or later</li>
1109)           <li>Adjust the settings</li>
1110)           <li>Automatically remove data older than, for instance, 90 days</li>
1111)         </ul>
1112)       </li>
1113)       <li>Maintainance<br />
1114)         <ul>
1115)           <li>Update all software dependencies</li>
1116)           <li>Automate crash recovery for Tor, Elasticsearch and crawler</li>
1117)         </ul>
1118)       </li>
1119)     </ol>
1120)     </li>
1121) 

1122) <!--
1123)     <a id=""></a>
1124)     <li>
1125)     <b></b>
1126)     <br>

1127)     Language: <i>Python</i>

1128)     <br>
1129)     Likely Mentors: <i>Damian (atagar)</i>

1130)     <br><br>

1131)     <p>
1132) 
1133)     </p>
1134) 
1135)     <p>
1136) 
1137)     </p>
1138)     </li>
1139) -->
1140) 

1141)     <li>
1142)     <b>Bring up new ideas!</b>

1143)     <br>

1144)     Don't like any of these? Look at the <a

1145)     href="/press/presskit/2008-12-19-roadmap-full.pdf">Tor development

1146)     roadmap</a> for more ideas, or just try out Tor and Tor Browser,

1147)     and find out what you think needs fixing.

1148)     Some of the <a href="<spectree>proposals">current proposals</a>

1149)     might also be short on developers.
1150)     </li>

1151) 

1152)     </ol>
1153)   </div>
1154)   <!-- END MAINCOL -->
1155)   <div id = "sidecol">
1156) #include "side.wmi"
1157) #include "info.wmi"
1158)   </div>
1159)   <!-- END SIDECOL -->
1160) </div>
1161) <!-- END CONTENT -->