[or-cvs] r22360: {website} rewrite the links to the wiki. (website/trunk/en)

Andrew Lewman andrew at torproject.org
Tue May 18 19:29:03 UTC 2010

Author: phobos
Date: 2010-05-18 19:29:03 +0000 (Tue, 18 May 2010)
New Revision: 22360

rewrite the links to the wiki.

Modified: website/trunk/en/faq.wml
--- website/trunk/en/faq.wml	2010-05-18 19:19:08 UTC (rev 22359)
+++ website/trunk/en/faq.wml	2010-05-18 19:29:03 UTC (rev 22360)
@@ -78,7 +78,7 @@
 <p>For other questions not yet on this version of the FAQ, see the <a
 FAQ</a> for now.</p>
 <hr />
@@ -161,9 +161,9 @@
 but we haven't researched the application-level anonymity
 issues on them well enough to be able to recommend a safe
 configuration. Our wiki has a list of instructions for <a
 specific applications</a>. There's also a <a
 of applications that help you direct your traffic through Tor</a>.
 Please add to these lists and help us keep them accurate!
@@ -391,7 +391,7 @@
 There are some steps that individuals
 can take to improve their Tor performance. <a
 can configure your Firefox to handle Tor better</a>, <a
 href="http://www.pps.jussieu.fr/~jch/software/polipo/tor.html">you can use
 Polipo with Tor</a>, or you can try <a href="<page download>">upgrading
@@ -695,7 +695,7 @@
 Tor, some IRC and IM applications, and a set of ipchains rules aimed to prevent
 non-Tor traffic from accidentally leaving your computer. More information at
 <li>Anonym.OS is a LiveCD similar to the above but is based on OpenBSD rather
 than Linux for maximum security. It was designed to be anonymous and secure
 from the ground up, and thus has some features and limitations not found in
@@ -780,11 +780,11 @@
 <li>Tor has built-in support for <a
 rate limiting</a>. Further, if you have a fast
 link but want to limit the number of bytes per
 day (or week or month) that you donate, check out the <a
 <li>Each Tor relay has an <a href="#ExitPolicies">exit policy</a> that
@@ -803,7 +803,7 @@
 <li>If your relay is behind a NAT and it doesn't know its public
 IP (e.g. it has an IP of 192.168.x.y), you'll need to set up port
 forwarding. Forwarding TCP connections is system dependent but 
-<a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ServerForFirewalledClients">this FAQ entry</a> 
+<a href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#ServerForFirewalledClients">this FAQ entry</a> 
 offers some examples on how to do this.
 <li>Your relay will passively estimate and advertise its recent
@@ -839,12 +839,12 @@
 The default exit policy allows access to many popular services (e.g. web browsing), but 
-<a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#DefaultPorts">restricts</a>
+<a href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#DefaultPorts">restricts</a>
 some due to abuse potential (e.g. mail) and some since
 the Tor network can't handle the load (e.g. default
 file-sharing ports). You can change your exit policy
 using Vidalia's "Sharing" tab, or by manually editing your 
-<a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#torrc">torrc</a>
+<a href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#torrc">torrc</a>
 file. If you want to avoid most if not all abuse potential, set it to
 "reject *:*" (or un-check all the boxes in Vidalia). This setting means
 that your relay will be used for relaying traffic inside the Tor network,
@@ -924,7 +924,7 @@
 <li>If you're running on Solaris, OpenBSD, NetBSD, or
 old FreeBSD, Tor is probably forking separate processes
 rather than using threads. Consider switching to a <a
 operating system</a>.</li>
 <li>If you still can't handle the memory load, consider reducing the
@@ -1034,7 +1034,7 @@
 Requiring every Tor user to be a relay would help with scaling the
-network to handle all our users, and <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayAnonymity">running a Tor
+network to handle all our users, and <a href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#RelayAnonymity">running a Tor
 relay may help your anonymity</a>. However, many Tor users cannot be good
 relays &mdash; for example, some Tor clients operate from behind restrictive
 firewalls, connect via modem, or otherwise aren't in a position where they
@@ -1071,7 +1071,7 @@
 <a href="<page volunteer>#Research">research section of the
 volunteer page</a>: "Tor doesn't work very well when relays
 have asymmetric bandwidth (e.g. cable or DSL)". It might be that <a
 to UDP transport</a> is the simplest answer here &mdash; which alas is
 not a very simple answer at all.
@@ -1132,7 +1132,7 @@
 A collection of templates for successfully responding to ISPs is <a

More information about the tor-commits mailing list