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) Feb 2006: Phase two is now underway &mdash; developing actual interfaces

44) for Tor. It's open to all who want to participate. We've set the new
45) deadline to Apr 30 2006.
46) </p>

47) 

48) <p>
49) Feb 2006: The <a

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

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

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

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

57) 
58) <p>

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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