Rebuild site

ept · Sep 4, 2017 · 5ce1656 · 5ce1656
1 parent 1cdedf2
commit 5ce1656
Show file tree

Hide file tree

Showing 5 changed files with 19 additions and 9 deletions.
diff --git a/static/2015/12/08/preventing-key-theft-at-passwords15.html b/static/2015/12/08/preventing-key-theft-at-passwords15.html
@@ -56,7 +56,7 @@ <h1>Strengthening public key authentication against key theft</h1>
 
                 <p>
 
-                    <a href="http://www.cl.cam.ac.uk/events/passwords2015/">9th International Conference on Passwords (Passwords15)</a>,
+                    <a href="http://www.cl.cam.ac.uk/events/passwords2015/">9th International Conference on Passwords</a>,
 
 
                     Cambridge, UK,
@@ -70,6 +70,8 @@ <h1>Strengthening public key authentication against key theft</h1>
 
 
 
+                    <li><a href="http://dx.doi.org/10.1007/978-3-319-29938-9_9">doi:10.1007/978-3-319-29938-9_9</a></li>
+
 
 
                     <li><a href="https://speakerdeck.com/ept/strengthening-public-key-authentication-against-key-theft">Slides</a></li>

diff --git a/static/2016/02/08/how-to-do-distributed-locking.html b/static/2016/02/08/how-to-do-distributed-locking.html
@@ -58,7 +58,7 @@ <h1>How to do distributed locking</h1>
 
                 <p>As part of the research for <a href="http://dataintensive.net/">my book</a>, I came across an algorithm called <a href="http://redis.io/topics/distlock">Redlock</a> on the
 <a href="http://redis.io/">Redis</a> website. The algorithm claims to implement fault-tolerant distributed locks (or rather,
-<a href="http://web.stanford.edu/class/cs240/readings/89-leases.pdf" title="Cary G Gray and David R Cheriton. Leases: An Efficient Fault-Tolerant Mechanism for Distributed File Cache Consistency. SOSP 1989">leases</a> [1]) on top of Redis, and the page asks for feedback from people who are into
+<a href="https://pdfs.semanticscholar.org/a25e/ee836dbd2a5ae680f835309a484c9f39ae4e.pdf" title="Cary G Gray and David R Cheriton. Leases: An Efficient Fault-Tolerant Mechanism for Distributed File Cache Consistency. SOSP 1989">leases</a> [1]) on top of Redis, and the page asks for feedback from people who are into
 distributed systems. The algorithm instinctively set off some alarm bells in the back of my mind, so
 I spent a bit of time thinking about it and writing up these notes.</p>
 
@@ -395,7 +395,7 @@ <h2 id="conclusion">Conclusion</h2>
 <h2 id="references">References</h2>
 
 <p>[1] Cary G Gray and David R Cheriton:
-“<a href="http://web.stanford.edu/class/cs240/readings/89-leases.pdf" title="Cary G Gray and David R Cheriton. Leases: An Efficient Fault-Tolerant Mechanism for Distributed File Cache Consistency. SOSP 1989">Leases: An Efficient Fault-Tolerant Mechanism for Distributed File Cache Consistency</a>,”
+“<a href="https://pdfs.semanticscholar.org/a25e/ee836dbd2a5ae680f835309a484c9f39ae4e.pdf" title="Cary G Gray and David R Cheriton. Leases: An Efficient Fault-Tolerant Mechanism for Distributed File Cache Consistency. SOSP 1989">Leases: An Efficient Fault-Tolerant Mechanism for Distributed File Cache Consistency</a>,”
 at <em>12th ACM Symposium on Operating Systems Principles</em> (SOSP), December 1989.
 <a href="http://dx.doi.org/10.1145/74850.74870">doi:10.1145/74850.74870</a></p>
 

diff --git a/static/2017/10/25/verifying-crdt-isabelle.html b/static/2017/10/25/verifying-crdt-isabelle.html
@@ -56,9 +56,11 @@ <h1>Verifying Strong Eventual Consistency in Distributed Systems</h1>
 
                 <p>
 
-                    OOPSLA,
+                    Proceedings of the ACM on Programming Languages (PACMPL), Vol. 1, OOPSLA, Article 109,
 
 
+                    Vancouver, BC, Canada,
+
                   October 2017.
                 </p>
 
@@ -68,6 +70,8 @@ <h1>Verifying Strong Eventual Consistency in Distributed Systems</h1>
 
 
 
+                    <li><a href="http://dx.doi.org/10.1145/3133933">doi:10.1145/3133933</a></li>
+
 
 
 

diff --git a/static/feed.rss b/static/feed.rss
@@ -10,7 +10,7 @@
         <atom:link href="http://martin.kleppmann.com/feed.rss" rel="self" type="application/rss+xml" />
         <link>http://martin.kleppmann.com/</link>
         <description></description>
-        <lastBuildDate>Fri, 11 Aug 2017 18:23:31 BST</lastBuildDate>
+        <lastBuildDate>Mon, 04 Sep 2017 13:17:21 BST</lastBuildDate>
         <language>en</language>
         <sy:updatePeriod>hourly</sy:updatePeriod>
         <sy:updateFrequency>1</sy:updateFrequency>
@@ -808,7 +808,7 @@ would cause far more harm than good.</p>
                 <content:encoded><![CDATA[
                     <p>As part of the research for <a href="http://dataintensive.net/">my book</a>, I came across an algorithm called <a href="http://redis.io/topics/distlock">Redlock</a> on the
 <a href="http://redis.io/">Redis</a> website. The algorithm claims to implement fault-tolerant distributed locks (or rather,
-<a href="http://web.stanford.edu/class/cs240/readings/89-leases.pdf" title="Cary G Gray and David R Cheriton. Leases: An Efficient Fault-Tolerant Mechanism for Distributed File Cache Consistency. SOSP 1989">leases</a> [1]) on top of Redis, and the page asks for feedback from people who are into
+<a href="https://pdfs.semanticscholar.org/a25e/ee836dbd2a5ae680f835309a484c9f39ae4e.pdf" title="Cary G Gray and David R Cheriton. Leases: An Efficient Fault-Tolerant Mechanism for Distributed File Cache Consistency. SOSP 1989">leases</a> [1]) on top of Redis, and the page asks for feedback from people who are into
 distributed systems. The algorithm instinctively set off some alarm bells in the back of my mind, so
 I spent a bit of time thinking about it and writing up these notes.</p>
 
@@ -1145,7 +1145,7 @@ academic peer review (unlike either of our blog posts).</p>
 <h2 id="references">References</h2>
 
 <p>[1] Cary G Gray and David R Cheriton:
-“<a href="http://web.stanford.edu/class/cs240/readings/89-leases.pdf" title="Cary G Gray and David R Cheriton. Leases: An Efficient Fault-Tolerant Mechanism for Distributed File Cache Consistency. SOSP 1989">Leases: An Efficient Fault-Tolerant Mechanism for Distributed File Cache Consistency</a>,”
+“<a href="https://pdfs.semanticscholar.org/a25e/ee836dbd2a5ae680f835309a484c9f39ae4e.pdf" title="Cary G Gray and David R Cheriton. Leases: An Efficient Fault-Tolerant Mechanism for Distributed File Cache Consistency. SOSP 1989">Leases: An Efficient Fault-Tolerant Mechanism for Distributed File Cache Consistency</a>,”
 at <em>12th ACM Symposium on Operating Systems Principles</em> (SOSP), December 1989.
 <a href="http://dx.doi.org/10.1145/74850.74870">doi:10.1145/74850.74870</a></p>
 

diff --git a/static/index.html b/static/index.html
@@ -362,10 +362,12 @@ <h2 class="title">Publications</h2>
     <li>
     Victor B. F. Gomes, Martin Kleppmann, Dominic P. Mulligan, and Alastair R. Beresford:
     “<a href="/2017/10/25/verifying-crdt-isabelle.html">Verifying Strong Eventual Consistency in Distributed Systems</a>”.
-    OOPSLA,
+    Proceedings of the ACM on Programming Languages (PACMPL), Vol. 1, OOPSLA, Article 109,
     October 2017.
 
 
+        <a href="http://dx.doi.org/10.1145/3133933">doi:10.1145/3133933</a>
+
 </li>
 
 
@@ -434,10 +436,12 @@ <h2 class="title">Publications</h2>
     <li>
     Martin Kleppmann and Conrad Irwin:
     “<a href="/2015/12/08/preventing-key-theft-at-passwords15.html">Strengthening public key authentication against key theft</a>”.
-    9th International Conference on Passwords (Passwords15),
+    9th International Conference on Passwords,
     December 2015.
 
 
+        <a href="http://dx.doi.org/10.1007/978-3-319-29938-9_9">doi:10.1007/978-3-319-29938-9_9</a>
+
 </li>