tor-webwml.git

1) ## translation metadata
2) # Revision: $Revision$
3) 
4) #include "head.wmi" TITLE="Tor: 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>2006-02: Phase two is now underway &mdash; developing actual interfaces
43) for Tor. It's open to all who want to participate. We've set the new
44) deadline to Apr 30 2006.
45) </p>

46) 

47) <p>2006-02: The <a

48) href="http://wiki.noreply.org/noreply/TheOnionRouter/ContestEntries">first
49) design phase</a> is over, and we have two winners. Feel free to

50) use their ideas if you like them:
51) <ul>
52) <li>Best overall: <a
53) href="http://cups.cs.cmu.edu/pubs/TorGUIContest113005.pdf">CMU Usable
54) Privacy and Security Laboratory</a></li>
55) <li>Most aesthetically pleasing:
56) <a href="http://www.april3rd.com/tor/">the April3rd team</a></li>
57) </ul>

58) 
59) <p>

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

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

62) forget the free Tor T-shirt for every submission!

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

70) estimate there are some 200,000 Tor users currently, routing their traffic
71) through about 400 volunteer Tor servers on six continents. However, Tor's

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

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

92) href="http://www.opensource.org/">Open Source Software</a>
93) that will provide a user interface to the Tor system by way of the

94) <a href="/cvs/control/doc/howto.txt">Tor Controller Protocol</a>.</p>

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

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

100) <ul>
101) <li>Allow the user to fully configure Tor rather than manually searching
102) for and opening text files.</li>
103) <li>Let users learn about the current state of their Tor connection
104) (for example, how well the current Tor connection is working),
105) and find out whether any of their applications are using it.</li>
106) <li>Make alerts and error conditions visible to the user.</li>
107) <li>Run on at least one of Windows, Linux, and OS&nbsp;X, on a
108) not-unusually-configured consumer-level machine.</li>
109) </ul>
110) 

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

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

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