diff --git a/website/download.html b/website/download.html
index 5cea71de..f45a950b 100644
--- a/website/download.html
+++ b/website/download.html
@@ -221,7 +221,26 @@
           sudo apt-get update
           sudo apt-get install recoll
           </tt></pre>
+          <p>Source code for the lens (also included in the main
+            recoll tar file):<br>
+            For 1.18 installations: <a href="recoll-lens-1.18.1.2997.tar.gz">
+              recoll-lens-1.18.1.2997.tar.gz</a><br>
+            For 1.17: <a href="recoll-lens-1.17.2.2697.tar.gz">
+              recoll-lens-1.17.2.2697.tar.gz</a></p>
 
+          <p>The packages in the standard repository and on the PPA
+            are a bit different in the sense that the Python extension
+            is included in the PPA package, but it's a separate
+            package in the standard repository. This can give rise to
+            errors about overwriting the Python module when switching
+            between versions. Typically, the error message would be
+            like the following:</p>
+          <pre><tt>
+    ErrorMessage: trying to overwrite '/usr/lib/python2.7/dist-packages/recoll.so', which is also in package recoll 1.18.1-1~ppa1~quantal1</tt></pre>
+
+           <p>If this happens, you just need to delete
+            the previous package(s) before installing the other one(s)
+            instead of performing an upgrade.</p>
 
         <h3><a name="mint">Linux Mint</a></h3>
         <p>The Ubuntu PPA works perfectly for Mint 13 (and probably
diff --git a/website/idxthreads/threadingRecoll.html b/website/idxthreads/threadingRecoll.html
index c4d6ee71..ef927d8d 100644
--- a/website/idxthreads/threadingRecoll.html
+++ b/website/idxthreads/threadingRecoll.html
@@ -743,7 +743,17 @@ asciidoc.install();
 <span id="revdate">2012-12-03</span>
 </div>
 <div id="content">
-<div id="preamble">
+<div class="sect1">
+<h2 id="_abstract">Abstract</h2>
+<div class="sectionbody">
+<div class="paragraph"><p>This relates lessons learned while modifying <strong>Recoll</strong> indexing to be
+multithreaded. I am by no means a threaded applications expert, so that a
+few of the observations I made whole doing this may be of use to other
+novices.</p></div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_introduction">Introduction</h2>
 <div class="sectionbody">
 <div class="paragraph"><p><a href="http://www.recoll.org"><strong>Recoll</strong></a> is a document indexing application, it
 allows you to find documents by specifying search terms.</p></div>
@@ -1247,8 +1257,9 @@ configuration structure. This belonged to the thread which initially
 created the filter. But the filter would often be reused by a different
 thread, with the consequence that the configuration object was now accessed
 and modified by two unsynchronized threads&#8230; Resetting the config pointer
-at the time of filter reuse was the ridiculously simple single-line fix to
-this evasive problem.</p></div>
+at the time of filter reuse was the
+<a href="https://bitbucket.org/medoc/recoll/commits/943de4b78818079b0eb6ffd0fcbdfdd0746b4a40">ridiculously
+simple (almost)single-line fix</a> to this evasive problem.</p></div>
 <div class="paragraph"><p>Looking at multi-threaded stack dumps is mostly fun for people with several
 heads, which is unfortunately not my case, so I was quite elated when this
 was over.</p></div>
@@ -1278,7 +1289,7 @@ the executing of ephemeral external commands.</p></div>
 <div id="footnotes"><hr /></div>
 <div id="footer">
 <div id="footer-text">
-Last updated 2012-12-04 11:14:07 CET
+Last updated 2012-12-14 15:55:12 CET
 </div>
 </div>
 </body>
diff --git a/website/idxthreads/threadingRecoll.txt b/website/idxthreads/threadingRecoll.txt
index 0fe8e9a8..09b770a8 100644
--- a/website/idxthreads/threadingRecoll.txt
+++ b/website/idxthreads/threadingRecoll.txt
@@ -3,6 +3,15 @@
 :Email: jfd@recoll.org
 :Date: 2012-12-03
 
+== Abstract
+
+This relates lessons learned while modifying *Recoll* indexing to be
+multithreaded. I am by no means a threaded applications expert, so that a
+few of the observations I made whole doing this may be of use to other
+novices. 
+
+== Introduction
+
 http://www.recoll.org[*Recoll*] is a document indexing application, it
 allows you to find documents by specifying search terms. 
 
@@ -369,8 +378,9 @@ configuration structure. This belonged to the thread which initially
 created the filter. But the filter would often be reused by a different
 thread, with the consequence that the configuration object was now accessed
 and modified by two unsynchronized threads... Resetting the config pointer
-at the time of filter reuse was the ridiculously simple single-line fix to
-this evasive problem.
+at the time of filter reuse was the
+https://bitbucket.org/medoc/recoll/commits/943de4b78818079b0eb6ffd0fcbdfdd0746b4a40[ridiculously
+simple (almost)single-line fix] to this evasive problem.
 
 Looking at multi-threaded stack dumps is mostly fun for people with several
 heads, which is unfortunately not my case, so I was quite elated when this
diff --git a/website/index.html.en b/website/index.html.en
index fa3fdbf2..e0d030e1 100644
--- a/website/index.html.en
+++ b/website/index.html.en
@@ -84,6 +84,14 @@
       <h2>News</h2>
       <div class="news">
       <dl>
+        <dt>2012-12-14</dt><dd>The next version of Recoll indexing will be
+          multithreaded, and much faster on most current
+          processors. The conversion has been an interesting project
+          with multiple stages, and I've taken 
+          <a href="idxthreads/threadingRecoll.html">a few  notes</a> 
+          about the transformation.</dd>
+        </dd>
+
         <dt>2012-11-23</dt><dd>Released a minor update to the very
           stable 1.17
           branch: <a href="download-1.17.html">1.17.4</a>.