tor-webwml.git

@@ -74,7 +74,7 @@ it in our bugtracker.) The

 </li>

 <li>

-<a href="https://blog.torproject.org/">Tor has a blog now</a>.

+<a href="<blog>">Tor has a blog now</a>.

 We try to keep it updated every week or two with the latest news.

 </li>

@@ -359,7 +359,7 @@ handle file-sharing traffic load.

 <p>

 For the much more in-depth answer, see <a

-href="https://blog.torproject.org/blog/why-tor-is-slow">Roger's blog

+href="<blog>why-tor-is-slow">Roger's blog

 post on the topic</a>, which includes both a detailed PDF and a video

 to go with it.

 </p>

@@ -879,7 +879,7 @@ the services, hosts, and networks he wants to allow connections to,

 based on abuse potential and his own situation. Read the FAQ entry on 

 <a href="<page faq-abuse>#TypicalAbuses">issues you might encounter</a> 

 if you use the default exit policy, and then read Mike Perry's 

-<a href="https://blog.torproject.org/blog/tips-running-exit-node-minimal-harassment">tips

+<a href="<blog>tips-running-exit-node-minimal-harassment">tips

 for running an exit node with minimal harassment</a>.

 </p>

@@ -1151,7 +1151,7 @@ we need to understand this threat better and learn how to mitigate it.

 <p>

 Fifth, we might need some sort of incentive scheme to encourage people

 to relay traffic for others, and/or to become exit nodes. Here are our

-<a href="https://blog.torproject.org/blog/two-incentive-designs-tor">current

+<a href="<blog>two-incentive-designs-tor">current

 thoughts on Tor incentives</a>.

 </p>

@@ -79,7 +79,7 @@ a <a href="<page donate>">tax-deductible donation.</a>

 <li>02 May 2010: Tor 0.2.1.26 released as stable.  Fixes yet more

 OpenSSL compatibility issues and lets relays defend themselves from

 connection floods.  Read the <a

-href="https://blog.torproject.org/blog/tor-02126-stable-released">full

+href="<blog>tor-02126-stable-released">full

 announcement</a> for the list of changes.</li>

 <li>29 March 2010:  Tor and Printfection announce The Tor Store.  More

 details are available in the <a href="<page

@@ -16,7 +16,7 @@

 <li>02 May 2010: Tor 0.2.1.26 released as stable.  Fixes yet more

 OpenSSL compatibility issues and lets relays defend themselves from

 connection floods.  Read the <a

-href="https://blog.torproject.org/blog/tor-02126-stable-released">full

+href="<blog>tor-02126-stable-released">full

 announcement</a> for the list of changes.</li>

 <li>29 March 2010:  Tor and Printfection announce The Tor Store.  More

 details are available in the <a href="<page

@@ -39,7 +39,7 @@ locations.  Read the <a

 href="http://archives.seul.org/or/announce/Jan-2010/msg00000.html">announcement</a>

 for the full list of fixes.</li>

 <li>21 December 2009: Tor 0.2.1.21 released as stable.  Fixes issues with OpenSSL and helps exit relays.  Read the <a href="http://archives.seul.org/or/announce/Dec-2009/msg00000.html">announcement</a> for the full list of fixes. </li>

-<li>10 October 2009:  Tor 0.2.1.20 released as stable.  Read the <a href="https://blog.torproject.org/blog/tor-02120-released">announcement</a> for the updates and changes.</li>

+<li>10 October 2009:  Tor 0.2.1.20 released as stable.  Read the <a href="<blog>tor-02120-released">announcement</a> for the updates and changes.</li>

 <li>28 July 2009: Tor 0.2.1.19 released as stable.  Read the <a

 href="http://archives.seul.org/or/announce/Aug-2009/msg00000.html">announcement</a>

 for the updates and changes.</li>

@@ -64,7 +64,7 @@ for the updates and changes.</li>

 <li>25 August 2008: Tor 0.2.0.30 released as stable.  Read the

 <a

 href="http://archives.seul.org/or/announce/Aug-2008/msg00000.html">announcement</a> or <a

-href="https://blog.torproject.org/blog/tor-0.2.0.30-released-stable">blog

+href="<blog>tor-0.2.0.30-released-stable">blog

 post</a> for the numerous updates and changes.</li>

 <li>25 May 2008: Tor receives two awards from the <a

 href="http://nlnet.nl/">NLnet Foundation</a>.  The first is to improve the performance

@@ -83,21 +83,21 @@ whose keys were generated by Debian, Ubuntu, or any derived distribution may

 have to replace their identity keys.  See our

 <a href="http://archives.seul.org/or/announce/May-2008/msg00000.html">security

 advisory</a> or the <a

-href="https://blog.torproject.org/blog/debian-openssl-flaw%3A-what-does-it-mean-tor-clients%3F">blog

+href="<blog>debian-openssl-flaw%3A-what-does-it-mean-tor-clients%3F">blog

 follow-up</a> for full details.  As always, you can find Tor 0.2.0.26-rc on

 the <a href="<page download>#Dev">downloads page</a>.</li>

 <li>Mar 2008: <a

-href="https://blog.torproject.org/blog/tor-project-google-summer-code-2008!">Tor

+href="<blog>tor-project-google-summer-code-2008!">Tor

 Project is in Google Summer of Code 2008!</a></li>

 <li>Feb 2008: The <a href="<page people>#Board">Board

 of Directors</a> welcomes <a

-href="https://blog.torproject.org/blog/isaac-mao-elected-one-our-new-directors">Isaac

+href="<blog>isaac-mao-elected-one-our-new-directors">Isaac

 Mao</a> to the board.  We thank Rebecca McKinnon for her support and

 contributions to the project.</li>

 <li>Feb 2008: Tor is happy to announce the <a

-href="https://blog.torproject.org">official Tor blog</a>.</li>

+href="<blog>">official Tor blog</a>.</li>

 <li>Jan 2008: <a href="<page download>">Tor 0.1.2.19</a> (the latest

 stable release) fixes a huge memory leak on exit relays, makes the

@@ -409,7 +409,7 @@ How To: Set Up Anonymous Browsing in 30 Seconds or Less</a>.

 Hackers Can Expose Masked Surfers, Study Says</a>

 A report on <a href="http://www.lightbluetouchpaper.org/2007/12/10/covert-channel-vulnerabilities-in-anonymity-systems/">

 Steven Murdoch's recent PhD thesis</a>. Steven <a

-href="http://blog.torproject.org/blog/media-coverage-%2526quot%3Bcovert-channel-vulnerabilities-anonymity-systems%2526quot%3B">

+href="<blog>media-coverage-%2526quot%3Bcovert-channel-vulnerabilities-anonymity-systems%2526quot%3B">

 responds on the Tor Blog</a>.</td>

 </tr>

 <tr style="background-color: #e5e5e5;">

@@ -218,7 +218,7 @@ service (Python). Tor aims to give out <a href="<page bridges>">bridge

 relay addresses</a> to users that can't reach the Tor network

 directly, but there's an arms race between algorithms for distributing

 addresses and algorithms for gathering and blocking them. See <a

-href="https://blog.torproject.org/blog/bridge-distribution-strategies">our

+href="<blog>bridge-distribution-strategies">our

 blog post on the topic</a> as an overview, and then look at <a

 href="http://archives.seul.org/or/dev/Dec-2009/msg00000.html">Roger's

 or-dev post</a> from December for more recent thoughts &mdash; lots of

@@ -34,3 +34,5 @@

 }:></define-tag>

 <define-tag wiki whitespace=delete>https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/</define-tag>

+# If you change this link also update it in */navigation.wmi.

+<define-tag blog whitespace=delete>https://blog.torproject.org/blog/</define-tag>