tor-webwml.git

1) ## translation metadata
2) # Revision: $Revision$
3) 

4) #include "head.wmi" TITLE="GUI Competition"

5) 
6) <div class="main-column">
7) 
8) <!-- LEFT HAND MENU FOR GUI CONTEST PAGES -->
9) <div class="guileft">
10) <div class="guimenu">

11) 

12)   <div class="curveleft">
13)   <div class="curveright">
14)   &nbsp;
15)   </div>
16)   </div>
17) 
18) <div class="guimenuinner">
19) <h1>Tor GUI Competition</h1>
20) 
21) <a class="on" href="index.html">Overview &amp; Goals</a>
22) <a href="categories.html">What to Submit</a>
23) <a href="submit.html">How to Submit</a>
24) <a href="criteria.html">Judging &amp; Timeline</a>
25) <a href="technotes.html">Technical Notes</a>
26) <a href="legal.html">Licensing</a>
27) <h1>&nbsp;</h1>
28) <a class="wiki" href="http://wiki.noreply.org/noreply/TheOnionRouter/ContestFAQ">Wiki/FAQ</a>
29) </div>
30) 
31)   <div class="curvebottomleft">
32)   <div class="curvebottomright">
33)   &nbsp;
34)   </div>
35)   </div>
36) 
37) </div>
38) </div>
39) 
40) <h2>News:</h2>
41) 

42) <p>

43) Jul 2006: Phase two is over, and brought us three fine interface
44) projects: <a href="http://vidalia-project.net/">Vidalia</a>,

45) <a href="http://freehaven.net/~squires/torbutton/">Torbutton</a>, and

46) <a href="http://tork.sf.net/">TorK</a>. Thank you to each of you who

47) participated. The GUI competition is now ended — but don't let that

48) stop you from <a href="<page volunteer>">helping out</a>!

49) </p>

50) 

51) <p>
52) Feb 2006: The <a

53) href="http://wiki.noreply.org/noreply/TheOnionRouter/ContestEntries">first

54) design phase</a> is over, and we have two winners. The <a
55) href="http://cups.cs.cmu.edu/pubs/TorGUIContest113005.pdf">CMU

56) Usable Privacy and Security Laboratory</a> won "Best Overall,"

57) and <a href="http://www.april3rd.com/tor/">the April3rd team</a> won
58) "Most Aesthetically Pleasing." Feel free to use their ideas if you
59) like them.</p>

60) 
61) <p>

62) Dec 2005: We're excited to have just added <a href="criteria.html">Edward Tufte

63) and Bruce Schneier</a> to our already impressive list of judges. And don't

64) forget the free <a href="http://tor.eff.org/tshirt.html">Tor T-shirt</a>
65) for every submission!

66) </p>
67) 
68) <h2>Tor: GUI Competition Overview</h2>
69) 
70) <p>
71) Tor is a decentralized network of computers on the Internet that increases
72) privacy in Web browsing, instant messaging, and other applications. We

73) estimate there are some 200,000 Tor users currently, routing their traffic

74) through about 500 volunteer Tor servers on six continents. However, Tor's

75) current user interface approach — running as a service in the background
76) — does a poor job of communicating network status and security levels
77) to the user.
78) </p>
79) 
80) <p>
81) The Tor project, affiliated with the
82) <a href="http://www.eff.org/">Electronic Frontier Foundation</a>, is
83) running a <b>GUI competition</b> to develop a vision of how Tor can
84) work in a user's everyday anonymous browsing experience. Some of the
85) challenges include how to make alerts and error conditions visible on
86) screen; how to let the user configure Tor to use or avoid certain routes
87) or nodes; how to learn about the current state of a Tor connection,
88) including which servers it uses; and how to find out whether (and which)
89) applications are using Tor safely.
90) </p>
91) <br />
92) 
93) <h2>Goals</h2>

94) <p>Submitters for phase two will produce a work of <a

95) href="http://www.opensource.org/">Open Source Software</a>

96) that will provide a user interface to the Tor system, perhaps by way of the

97) <a href="/svn/torctl/doc/howto.txt">Tor Controller Protocol</a>.</p>

98) 
99) <p>We are looking for a vision of how Tor can work in a user's everyday
100) anonymous browsing experience.</p>
101) 

102) <p>Entries may:</p>

103) <ul>
104) <li>Allow the user to fully configure Tor rather than manually searching
105) for and opening text files.</li>
106) <li>Let users learn about the current state of their Tor connection
107) (for example, how well the current Tor connection is working),

108) and configure or find out whether any of their applications are using it.</li>

109) <li>Make alerts and error conditions visible to the user.</li>
110) <li>Run on at least one of Windows, Linux, and OS&nbsp;X, on a
111) not-unusually-configured consumer-level machine.</li>
112) </ul>
113) 

114) <p>Other ideas include:</p>

115) <ul>
116) <li>Provide detailed information about which
117) applications, ports, or packets are (or are not!) passing through Tor,
118) including accounting for both Tor- and non-Tor traffic.</li>
119) <li>Provide
120) additional statistics about the Tor connection.</li>
121) <li>Give users more control over how their Tor behaves at certain times
122) of day or in other contexts (like operating as a server).</li>
123) </ul>
124) 

125) <p>More examples of useful features include:</p>