65 files changed, 3461 insertions, 237 deletions
diff --git a/template/about.html.j2 b/template/about.html.j2
index be9a7298..5dee5c2c 100644
--- a/template/about.html.j2
+++ b/template/about.html.j2
@@ -115,7 +115,7 @@
            {% endtrans %}
            <br>
            <a href="https://nlnet.nl/">NLnet Foundation</a><br>
-            <img src="{{ url('static/images/nlnet_logo.gif') }}" alt="NLnet logo">
+            <img src="{{ url('images/nlnet_logo.gif') }}" alt="NLnet logo">
            </p>
          </li>
          <li>
@@ -132,7 +132,7 @@
            {% endtrans %}
            <br>
            <a href="https://wiki.geant.org/display/NGITrust/">GEANT NGI TRUST</a><br>
-            <img style="width: 35%" src="{{ url('static/images/ngi_trust.png') }}" alt="NGI TRUST logo">
+            <img style="width: 35%" src="{{ url('images/ngi_trust.png') }}" alt="NGI TRUST logo">
            </p>
          </li>
@@ -156,25 +156,25 @@
          <li>
            <p>
            <a href="https://renewablefreedom.org/">Renewable Freedom Foundation / Stiftung Erneuerbare Freiheit</a><br>
-            <img src="{{ url('static/images/rff_logo.png') }}" alt="RFF logo">
+            <img src="{{ url('images/rff_logo.png') }}" alt="RFF logo">
            </p>
          </li>
          <li>
            <p>
            <a href="https://cordis.europa.eu/fp7/">European Commission (FP7)</a><br>
-            <img src="{{ url('static/images/fp7_logo.jpg') }}" alt="FP7 logo">
+            <img src="{{ url('images/fp7_logo.jpg') }}" alt="FP7 logo">
            </p>
          </li>
          <li>
            <p>
            <a href="http://www.dfg.de/">Deutsche Forschungsgemeinschaft</a><br>
-            <img src="{{ url('static/images/dfg_logo.gif') }}" alt="DFG logo">
+            <img src="{{ url('images/dfg_logo.gif') }}" alt="DFG logo">
            </p>
          </li>
          <li>
            <p>
            <a href="https://nlnet.nl/">NLnet Foundation</a><br>
-            <img src="{{ url('static/images/nlnet_logo.gif') }}" alt="NLnet logo">
+            <img src="{{ url('images/nlnet_logo.gif') }}" alt="NLnet logo">
            </p>
          </li>
        </ul>
diff --git a/template/applications.html.j2 b/template/applications.html.j2
index 43b0dd2f..f1f0e30f 100644
--- a/template/applications.html.j2
+++ b/template/applications.html.j2
@@ -19,7 +19,7 @@
          hierarchy, GNS uses a directed graph.  Naming conventions
          are similar to DNS, but queries and replies are private even
          with respect to peers providing the answers.  The integrity of
-          records and privacy of look-ups is cryptographically secured.
+          records and privacy of look-ups are cryptographically secured.
          <!-- Too technical: GNS integrates
               a robust, efficient and instant key revocation mechanism. -->
        {% endtrans %}
@@ -37,8 +37,8 @@
      <section>
      <h3>{{ _("Self-sovereign, decentralized identity provider") }}</h3>
      <p>
+        <a href="{{ url_localized('reclaim/index.html') }}">re:claimID</a>
        {% trans %}
-        <a href="https://reclaim.gnunet.org/">re:claimID</a>
        is a decentralized Identity Provider (IdP) service built in top of the
        GNU Name System. It allows users to securely share personal information
        with websites using standardized protocols (OpenID Connect).
@@ -162,7 +162,7 @@
          {% trans %}
          <a href="https://gitlab.com/gnunet-messenger/cadet-gtk">Cadet-GTK</a>
          is a convenient but feature-rich graphical application
-          providing messaging using especially the CADET subsystem. It is
+          providing messaging using the CADET subsystem. It is
          developed using GTK and libhandy for a convergent design.
          {% endtrans %}
        </p>
@@ -181,7 +181,7 @@
        <p>
          {% trans %}
          <a href="https://git.gnunet.org/groupchat.git/">groupchat</a>
-          is a terminal user interface providing messaging using especially the CADET subsystem. It is
+          is a terminal user interface providing messaging using the CADET subsystem. It is
          developed using nim. Cadet-GTK and groupchat are planned to be compatible.
          {% endtrans %}
        </p>
diff --git a/template/architecture.html.j2 b/template/architecture.html.j2
index e7d62c08..04067749 100644
--- a/template/architecture.html.j2
+++ b/template/architecture.html.j2
@@ -9,42 +9,7 @@
  <div class="container">
    <div class="row">
      <div class="col-10">
-        <img class="img-fluid border rounded" src="../static/images/gnunet-arch-full.svg">
+       <img class="img-fluid" src="../static/images/arch.png">
-      </div>
-      <div class="col-2 d-none d-sm-block">
-        <h4>{{ _("Legend") }}:</h4>
-        <dl>
-          <dt>house</dt>
-          <dd>application</dd>
-        </dl>
-        <dl>
-          <dt>circle</dt>
-          <dd>application</dd>
-        </dl>
-        <dl>
-          <dt>box</dt>
-          <dd>daemon</dd>
-        </dl>
-        <dl>
-          <dt>diamond</dt>
-          <dd>library</dd>
-        </dl>
-        <dl>
-          <dt>blackline</dt>
-          <dd>dependency</dd>
-        </dl>
-        <dl>
-          <dt>blue line</dt>
-          <dd>extension via plugin</dd>
-        </dl>
-        <dl>
-          <dt>red line</dt>
-          <dd>possibly useful</dd>
-        </dl>
-        <dl>
-          <dt>dashed</dt>
-          <dd>in planning</dd>
-        </dl>
      </div>
    </div>
  </div>
@@ -60,7 +25,7 @@
          messaging layer (CADET), a public key infrastructure
          (GNS) and a pluggable transport system (TRANSPORT).<br>
          Using public keys for addresses
-          and self-organized decentralized routing algorithms,
+          and self-organizing decentralized routing algorithms,
          these subsystems replace the traditional TCP/IP stack.
          {% endtrans %}
        </p>
@@ -73,7 +38,7 @@
          {% trans %}
          GNUnet is implemented using a multi-process architecture.
          Each subsystem runs as a separate process, providing
-          fault-isolation and enabling tight permissions to be
+          fault isolation and enabling tight permissions to be
          granted to each subsystem.  Naturally, the
          implementation is a <a href="https://www.gnu.org/">GNU</a>
          package, and will always remain free software.
@@ -86,13 +51,13 @@
      <div class="col-md">
        <h2>{{ _("System architecture") }}</h2>
        <p>
-        Read more about the system architecure in the respective section of our <a href="https://docs.gnunet.org/handbook/gnunet.html#System-Architecture" target="_blank">handbook</a>.
+        Read more about the system architecture in the corresponding section of our <a href="https://docs.gnunet.org/handbook/gnunet.html#System-Architecture" target="_blank">handbook</a>.
        </p>
      </div>
      <div class="col-md">
        <h2>{{ _("Subsystems") }}</h2>
        <p>
-        Read more about the subsystems (or GNUnet services) in the respective section of our <a href="https://docs.gnunet.org/handbook/gnunet.html#Code-overview" target="_blank">handbook</a>.
+        Read more about the subsystems (or GNUnet services) in the corresponding section of our <a href="https://docs.gnunet.org/handbook/gnunet.html#Code-overview" target="_blank">handbook</a>.
        </p>
      </div>
    </div>
@@ -107,11 +72,53 @@
      <div class="col-md">
        <h2>{{ _("APIs") }}</h2>
        <p>
-        GNUnet offers variaty of APIs for <a href="https://docs.gnunet.org/handbook/gnunet.html#Interprocess-communication-API-_0028IPC_0029" target="_blank">accessing services</a> (using IPC), <a href="https://docs.gnunet.org/handbook/gnunet.html#Service-API">running services</a>, <a href="https://docs.gnunet.org/handbook/gnunet.html#Message-Queue-API">message queues</a>, or <a href="https://docs.gnunet.org/handbook/gnunet.html#Cryptography-API" target="_blank">cryptographic operations</a>.
+        GNUnet offers a variety of APIs for <a href="https://docs.gnunet.org/handbook/gnunet.html#Interprocess-communication-API-_0028IPC_0029" target="_blank">accessing services</a> (using IPC), <a href="https://docs.gnunet.org/handbook/gnunet.html#Service-API">running services</a>, <a href="https://docs.gnunet.org/handbook/gnunet.html#Message-Queue-API">message queues</a>, or <a href="https://docs.gnunet.org/handbook/gnunet.html#Cryptography-API" target="_blank">cryptographic operations</a>.
        </p>
      </div>
    </div>
  </div>
+  <div class="container">
+    <div class="row">
+     <div class="col-10">
+        <img class="img-fluid border rounded" src="../static/images/gnunet-arch-full.svg">
+      </div>
+      <div class="col-2 d-none d-sm-block">
+        <h4>{{ _("Legend") }}:</h4>
+        <dl>
+          <dt>house</dt>
+          <dd>application</dd>
+        </dl>
+        <dl>
+          <dt>circle</dt>
+          <dd>application</dd>
+        </dl>
+        <dl>
+          <dt>box</dt>
+          <dd>daemon</dd>
+        </dl>
+        <dl>
+          <dt>diamond</dt>
+          <dd>library</dd>
+        </dl>
+        <dl>
+          <dt>blackline</dt>
+          <dd>dependency</dd>
+        </dl>
+        <dl>
+          <dt>blue line</dt>
+          <dd>extension via plugin</dd>
+        </dl>
+        <dl>
+          <dt>red line</dt>
+          <dd>possibly useful</dd>
+        </dl>
+        <dl>
+          <dt>dashed</dt>
+          <dd>in planning</dd>
+        </dl>
+      </div>
+    </div>
+  </div>
 </article>
 {% endblock body_content %}
diff --git a/template/engage.html.j2 b/template/engage.html.j2
index 000396ab..5bbaf9f3 100644
--- a/template/engage.html.j2
+++ b/template/engage.html.j2
@@ -26,14 +26,14 @@
      </p>
      <h4>Mumble</h4>
      <p>
-            We have a monthly get-together on mumble where we talk about recent developments, strategies, and politics.<br>
+            We have a monthly get-together on Mumble where we talk about recent developments, strategies, and politics.<br>
            We come together on that day of the month, where n.day==n.month. E.g. we’ll meet on 6th of June, 7th of July, 8th of August, 9th of September, 10th of October and so on. We will usually start around 8 PM CEST, but try to be there earlier and stay longer just to hang around together.<br>
-            To connect just enter "gnunet.org" as server into your mumble client; leave everything else as default. 
+            To connect just enter "gnunet.org" as server into your Mumble client; leave everything else as default.
      </p>
      </p>
      <h4>PSYC</h4>
      <p>
-        You find some of us on PSYC using the following adresses: 
+        You find some of us on PSYC using the following adresses:
        <ul>
          <li>psyc://loupsycedyglgamf.onion/@welcome</li>
          <li>irc://loupsycedyglgamf.onion:67/welcome</li>
@@ -46,7 +46,7 @@
    <div class="col-md">
      <h2>Install GNUnet!</h2>
      <p>
-        Another thing you might want now is your own GNUnet installation. As we haven’t packaged the new versions yet (June 2019) we provide <a href="https://gnunet.org/en/install.html">some tutorials how to install step-by-step</a>.
+        Another thing you might want now is your own GNUnet installation. As we haven’t packaged the new versions yet (as of June 2019) we provide <a href="https://gnunet.org/en/install.html">some tutorials how to install step-by-step</a>.
     </p>
     <h2>Use GNUnet!</h2>
      <p>
@@ -62,8 +62,8 @@
        <li>If you do not want to use the public bug tracker, you can also eMail to bug-gnunet@gnu.org.</li>
        <li>Please inform us if your operating system or package manager applies any vendor changes to GNUnet which you know about (to exclude potential problems introduced by third parties).</li>
        <li>Wait until your bug report is acknowledged/replied to. Note that only volunteers work on this, responses may take a while.</li>
-        <li>Please follow up with eventual questions about the bug. </li>
+        <li>Please follow up on any questions about the bug.</li>
-        <li>Once a fix is there: Check if it&#39;s working as expected, so that we can properly close the bug report and/or give you credits :)</li>
+        <li>Once a fix is there: Check if it&#39;s working as expected, so that we can properly close the bug report and/or give you credit :)</li>
      </ul>
    <h2>Contribute!</h2>
      <p>
diff --git a/template/ev.html.j2 b/template/ev.html.j2
index fac71cab..d35480f4 100644
--- a/template/ev.html.j2
+++ b/template/ev.html.j2
@@ -40,7 +40,7 @@
          to support GNUnet e.V. and in particularly contribute to the
          technical development within their means. For further
          details, we refer to the
-          <a href="https://git.gnunet.org/gnunet-ev.git/">Satzung</a>
+          <a href="https://git.gnunet.org/gnunet-ev.git/">Satzung (Charter)</a>
          (currently only available in German, translations welcome).
        {% endtrans %}
      </p>
@@ -52,18 +52,18 @@
      <h3>{{ _("Governance") }}</h3>
      <p>
        {% trans %}
-          You can find our "Satzung", and the list of members under
+          You can find our charter, and the list of members under
          <a href="https://git.gnunet.org/gnunet-ev.git/tree/satzung.tex">https://git.gnunet.org/gnunet-ev.git/tree/satzung.tex</a>.
          The current board consists of:
          <dl><dt>Vorsitz</dt>
            <dd><a href="https://schanzen.eu">Martin Schanzenbach</a></dd>
            <dt>stellvertretender Vorsitz</dt>
-            <dd><a href="https://grothoff.org/christian/">Christian Grothoff</a></dd>
+            <dd>t3sserakt</dd>
            <dt>Kassenwart</dt>
            <dd>Florian Dold</dd>
            <dt>Beisitzer</dt>
            <dd>
-                Hartmut Goebel, DVN
+              <a href="https://grothoff.org/christian/">Christian Grothoff</a>, ch3
            </dd>
          </dl>
        {% endtrans %}
diff --git a/template/faq.html.j2 b/template/faq.html.j2
index f23a9d7a..67811b52 100644
--- a/template/faq.html.j2
+++ b/template/faq.html.j2
@@ -3,63 +3,1012 @@
 <div class="container-fluid">
  <div class="container text-center">
    <h1>FAQs<h1>
-    <h2><i>This page is a work-in-progress</i></h2>
-  </div>
  </div>
+</div>
 <div class="container">
-  <article>
+  <div class="row">
-    <section>
+    <div class="col-2 d-none d-lg-block"><!-- for large viewports show menu for better orientation -->
-      <h3>{{ _("Is GNUnet ready for use on production systems?") }}</h3>
+      <nav class="nav subnav position-fixed flex-column border-right" style="position:fixed">
-      <p>
+        <a class="nav-link" href="#general">{{ _("General") }}</a>
-        {% trans %}
+        <a class="nav-link" href="#features">{{ _("Features") }}</a>
-        A: GNUnet is still undergoing major development. It is largely not yet ready
+        <a class="nav-link" href="#gns">GNU Name System</a>
-  for usage beyond developers. Your mileage will vary depending on the
+        <a class="nav-link" href="#errors">{{ _("Error messages") }}</a>
-  functionality you use, but you will always likely run into issues with
+        <a class="nav-link" href="#fs">{{ _("File-sharing") }}</a>
-  our current low-level transport system. We are currently in the process of
+        <a class="nav-link" href="#contrib">{{ _("Contributing") }}</a>
-  rewriting it (Project &quot;Transport Next Generation [TNG]&quot;)
+      </nav>
-        {% endtrans %}
+    </div>
-      </p>
-    </section>
+    <div class="col">
-    <section>
+      <article>
-      <h3>{{ _("Is GNUnet build using distributed ledger technologies?") }}</h3>
+        <h2><a name="general" class="subnav-anchor"></a>{{ _("General") }}</h2>
-      <p>
+        General questions about the project.
-        {% trans %}
+        <section>
-        A: No. GNUnet is a new network protocol stack for building secure,
+          <h3>{{ _("What do I do if my question is not answered here?") }}</h3>
-  distributed, and privacy-preserving applications.
+          <p>
-  While a ledger could be built using GNUnet, we currently have no plans in
+          {% trans %}
-  doing so.
+          A: There are many other sources of information. You can read additional
-        {% endtrans %}
+          documentation or ask the question on the help-gnunet@gnu.org mailing list or
-      </p>
+          the #gnunet IRC on irc.freenode.net.
-    </section>
+          {% endtrans %}
-    <section>
+          </p>
-      <h3>{{ _("I receive many &quot;WARNING Calculated flow delay for X at Y for Z&quot;. Should I worry?") }}</h3>
+        </section>
-      <p>
+        <section>
-        {% trans %}
+          <h3>{{ _("When are you going to release the next version?") }}</h3>
-        A: Right now, this is expected and a known cause for high
+          <p>
-        latency in GNUnet.  We have started a major rewrite to address
+          {% trans %}
-        this and other problems, but until the Transport Next
+          A: The general answer is, when it is ready. A better answer may be: earlier
-        Generation (TNG) is ready, these warnings are expected.
+          if you contribute (test, debug, code, document). Every release will be
-        {% endtrans %}
+          anounced on the info-gnunet@gnu.org mailing list and on
-      </p>
+          <a href="https://planet.gnu.org">planet GNU</a>. You can subscribe to the
-    </section>
+          mailing list or the RSS feed of this site to automatically receive a
-    <section>
+          notification.
-      <h3>{{ _("Is there a graphical user interface?") }}</h3>
+          {% endtrans %}
-      <p>
+          </p>
-        {% trans %}
+        </section>
-        A: gnunet-gtk is a separate download. The package
+        <section>
-        contains various GTK+ based graphical interfaces, including a
+          <h3>{{ _("Is the code free?") }}</h3>
-        graphical tool for configuration.
+          <p>
-        {% endtrans %}
+          {% trans %}
-      </p>
+          A: GNUnet is free software, available under the
-    </section>
+          <a href="https://www.gnu.org/licenses/agpl-3.0.en.html">GNU Affero Public License (AGPL)</a>.
-  </article>
+          {% endtrans %}
-<!--
+          </p>
-<h2>{{ ("Q?") }}</h2>
+        </section>
+        <section>
-<h2>{{ ("Q?") }}</h2>
+          <h3>{{ _("Are there any known bugs?") }}</h3>
+          <p>
-<h2>{{ ("Q?") }}</h2>
+          {% trans %}
-->
+          A: We track the list of currently known bugs in the
+          <a href="https://bugs.gnunet.org/">Mantis system</a>.
+          Some bugs are occasionally reported directly to developers or the developer
+          mailing list. This is discouraged since developers often do not have the time
+          to feed these bugs back into the Mantis database. Please report bugs directly
+          to the bug tracking system. If you believe a bug is sensitive, you can set its
+          view status to private (this should be the exception).
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Is there a graphical user interface?") }}</h3>
+          <p>
+          {% trans %}
+          A: gnunet-gtk is a separate download. The package
+          contains various GTK+ based graphical interfaces, including a
+          graphical tool for configuration.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Why does gnunet-service-nse create a high CPU load?") }}</h3>
+          <p>
+          {% trans %}
+          A: The gnunet-service-nse process will initially compute a so-called
+          &quot;proof-of-work&quot; which is used to convince the network that your
+          peer is real (or, rather, make it expensive for an adversary to mount a Sybil
+          attack on the network size estimator). The calculation is expected to take a
+          few days, depending on how fast your CPU is. If the CPU load is creating a
+          problem for you, you can set the value &quot;WORKDELAY&quot; in the
+          &quot;nse&quot; section of
+          your configuration file to a higher value. The default is &quot;5 ms&quot;.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("How does GNUnet compare to Tor?") }}</h3>
+          <p>
+          {% trans %}
+          A: Tor focuses on anonymous communication and censorship-resistance for TCP
+          connections and, with the Tor Browser Bundle, for the Web in particular.
+          GNUnet does not really have one focus; our theme is secure decentralized
+          networking, but that is too broad to be called a focus.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("How does GNUnet compare to I2P?") }}</h3>
+          <p>
+          {% trans %}
+          A: Both GNUnet and I2P want to build a better, more secure, more decentralized
+          Internet. However, on the technical side, there are almost no overlaps.
+          <br><br>
+          I2P is written in Java, and has (asymmetric) tunnels using onion (or garlic)
+          routing as the basis for various (anonymized) applications. I2P is largely used
+          via a Web frontend.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Is GNUnet ready for use on production systems?") }}</h3>
+          <p>
+          {% trans %}
+          A: GNUnet is still undergoing major development. It is largely not yet ready
+          for usage beyond developers. Your mileage will vary depending on the
+          functionality you use, but you will always likely run into issues with
+          our current low-level transport system. We are currently in the process of
+          rewriting it (Project &quot;Transport Next Generation [TNG]&quot;)
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Is GNUnet build using distributed ledger technologies?") }}</h3>
+          <p>
+          {% trans %}
+          A: No. GNUnet is a new network protocol stack for building secure,
+          distributed, and privacy-preserving applications.
+          While a ledger could be built using GNUnet, we currently have no plans in
+          doing so.
+          {% endtrans %}
+          </p>
+        </section>
+        <hr/>
+        <h2><a name="features" class="subnav-anchor"></a>{{ _("Features") }}</h2>
+        <section>
+          <h3>{{ _("What can I do with GNUnet?") }}</h3>
+          <p>
+          {% trans %}
+          A: GNUnet is a peer-to-peer framework, by which we mostly mean that it can do
+          more than just one thing. Naturally, the implementation and documentation of
+          some of the features that exist are more advanced than others.
+          {% endtrans %}
+          </p>
+          <p>
+          {% trans %}
+          For users, GNUnet offers anonymous and non-anonymous file-sharing, a fully
+          decentralized and censorship-resistant replacement for DNS and a mechanism for
+          IPv4-IPv6 protocol translation and tunneling (NAT-PT with DNS-ALG).
+          {% endtrans %}
+          See also: <a href="{{ url_localized('applications.html') }}">Applications</a>.
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Is it possible to surf the WWW anonymously with GNUnet?") }}</h3>
+          <p>
+          {% trans %}
+          A: It is not possible use GNUnet for anonymous browsing at this point.
+          We recommend that you use Tor for anonymous surfing.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Is it possible to access GNUnet via a browser as an anonymous WWW?") }}</h3>
+          <p>
+          {% trans %}
+          A: There is currently no proxy (like fproxy in Freenet) for GNUnet that would
+          make it accessible via a browser. It is possible to build such a proxy and
+          all one needs to know is the protocol used between the browser and the proxy and
+          the GNUnet code for file-sharing.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Is there a graphical user interface?") }}</h3>
+          <p>
+          {% trans %}
+          A: There are actually a few graphical user interfaces for different functions.
+          gnunet-setup is to configure GNUnet, and gnunet-fs-gtk is for file-sharing.
+          There are a few other gnunet-XXX-gtk GUIs of lesser importance.
+          Note that in order to obtain the GUI, you need to install the gnunet-gtk
+          package, which is a separate download.
+          gnunet-gtk is a meta GUI that integrates most of the other GUIs in one window.
+          One exception is gnunet-setup, which must still be run separately at this time
+          (as setup requires the peer to be stopped).
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Which operating systems does GNUnet run on?") }}</h3>
+          <p>
+          {% trans %}
+          A: GNUnet is being developed and tested primarily under Debian GNU/Linux.
+          Furthermore, we regularly build and test GNUnet on Fedora, Ubuntu, Arch,
+          FreeBSD and macOS.
+          We have reports of working versions on many other GNU/Linux distributions;
+          in the past we had reports of working versions on NetBSD, OpenBSD and Solaris.
+          However, not all of those reports are recent, so if you cannot get GNUnet to
+          work on those systems please let us know.
+          {% endtrans %}
+          </p>
+        </section>
+        <hr/>
+        <h2><a name="gns" class="subnav-anchor"></a>GNU Name System</h2>
+        <section>
+          <h3>{{ _("Who runs the GNS root zone?") }}</h3>
+          <p>
+          {% trans %}
+          A: Short answer: you. The long answer is the GNUnet will ship with a
+          default configuration of top-level domains. The governance of this default
+          configuration is not yet established. In any case, the user will be able
+          to modify this configuration at will. We expect normal users to have
+          no need to edit their own GNS zone(s) unless they host services themselves.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Where is the per-user GNS database kept?") }}</h3>
+          <p>
+          {% trans %}
+          A: The short answer is that the database is kept at the user's GNUnet peer.
+          Now, a user may run multiple GNUnet peers, in which case the database could be
+          kept at each peer (however, we don't have code for convenient replication).
+          Similarly, multiple GNUnet peers can share one instance of the database ---
+          the &quot;gnunet-service-namestore&quot; can be accessed from remote
+          (via TCP). The actual data can be stored in a Postgres database, for which
+          various replication options are again applicable. Ultimately, there are many
+          options for how users can store (and secure) their GNS database.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("What is the expected average size of a GNS namestore database?") }}</h3>
+          <p>
+          {% trans %}
+          A: Pretty small. Based on our user study where we looked at browser histories
+          and the number of domains visited, we expect that GNS databases will only
+          grow to a few tens of thousands of entries, small enough to fit even on mobile
+          devices.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Is GNS resistant to the attacks on DNS used by the US?") }}</h3>
+          <p>
+          {% trans %}
+          A: We believe so, as there is no entity that any government could force to
+          change the mapping for a name except for each individual user (and then the
+          changes would only apply to the names that this user is the authority for).
+          So if everyone used GNS, the only practical attack of a government would be to
+          force the operator of a server to change the GNS records for his server to
+          point elsewhere. However, if the owner of the private key for a zone is
+          unavailable for enforcement, the respective zone cannot be changed and any
+          other zone delegating to this zone will achieve proper resolution.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("How does GNS compare to other name systems?") }}</h3>
+          <p>
+          {% trans %}
+          A: A scientific paper on this topic 
+          <a href="https://grothoff.org/christian/ns2018.pdf">has been published
+          </a> and below is a table from the publication.
+          For detailed descriptions please refer to the paper.
+          {% endtrans %}
+          <table>
+            <thead>
+              <td></td>
+              <td>MitM manipulation</td>
+              <td>Zone walk</td>
+              <td>Client observation (network)</td>
+              <td>Client observation (operator)</td>
+              <td>Traffic amplification</td>
+              <td>Censorship/legal attacks</td>
+              <td>Ease of migration</td>
+            <thead>
+            <tbody>
+              <tr>
+              <td>DNS</td>
+              <td><i class="fa fa-times"></i></td>
+              <td><i class="fa fa-check"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td>+++</td>
+              </tr>
+              <tr>
+              <td>DNSSEC</td>
+              <td><i class="fa fa-check"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td>+</td>
+              </tr>
+              <tr>
+              <td>DNSCurve</td>
+              <td><i class="fa fa-check"></i></td>
+              <td><i class="fa fa-check"></i></td>
+              <td><i class="fa fa-check"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td>+</td>
+              </tr>
+              <tr>
+              <td>DoT/DoH</td>
+              <td><i class="fa fa-check"></i></td>
+              <td>n/a</td>
+              <td><i class="fa fa-check"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td><i class="fa fa-check"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td>+</td>
+              </tr>
+              <tr>
+              <td>Confid. DNS</td>
+              <td><i class="fa fa-times"></i></td>
+              <td>n/a</td>
+              <td><i class="fa fa-check"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td>++</td>
+              </tr>
+              <tr>
+              <td>Namecoin</td>
+              <td><i class="fa fa-check"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td><i class="fa fa-check"></i></td>
+              <td><i class="fa fa-check"></i></td>
+              <td><i class="fa fa-check"></i></td>
+              <td><i class="fa fa-check"></i></td>
+              <td>-</td>
+              </tr>
+              <tr>
+              <td>GNS</td>
+              <td><i class="fa fa-check"></i></td>
+              <td><i class="fa fa-check"></i></td>
+              <td><i class="fa fa-check"></i></td>
+              <td><i class="fa fa-check"></i></td>
+              <td><i class="fa fa-check"></i></td>
+              <td><i class="fa fa-check"></i></td>
+              <td>--</td>
+              </tr>
+              <tr>
+              <td>RAINS</td>
+              <td><i class="fa fa-check"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td><i class="fa fa-check"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td><i class="fa fa-check"></i></td>
+              <td><i class="fa fa-times"></i></td>
+              <td>--</td>
+              </tr>
+            </tbody>
+          </table>
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("What is the difference between GNS and CoDoNS?") }}</h3>
+          <p>
+          {% trans %}
+          A: CoDoNS decentralizes the DNS database (using a DHT) but preserves the
+          authority structure of DNS. With CoDoNS, IANA/ICANN are still in charge, and
+          there are still registrars that determine who owns a name.
+          <br><br>
+          With GNS, we decentralize the database and also decentralize the
+          responsibility for naming: each user runs their own personal root zone and is
+          thus in complete control of the names they use. GNS also has many additional
+          features (to keep names short and enable migration) which don't even make
+          sense in the context of CoDoNS.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("What is the difference between GNS and SocialDNS?") }}</h3>
+          <p>
+          {% trans %}
+          A: Like GNS, SocialDNS allows each user to create DNS mappings. However, with
+          SocialDNS the mappings are shared through the social network and subjected to
+          ranking. As the social relationships evolve, names can thus change in
+          surprising ways.
+          <br><br>
+          With GNS, names are primarily shared via delegation, and thus mappings will
+          only change if the user responsible for the name (the authority) manually
+          changes the record.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("What is the difference between GNS and ODDNS?") }}</h3>
+          <p>
+          {% trans %}
+          A: ODDNS is primarily designed to bypass the DNS root zone and the TLD
+          registries (such as those for ".com" and ".org"). Instead of using those,
+          each user is expected to maintain a database of (second-level) domains
+          (like "gnu.org") and the IP addresses of the respective name servers.
+          Resolution will fail if the target name servers change IPs.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("What is the difference between GNS and Handshake?") }}</h3>
+          <p>
+          {% trans %}
+          A: Handshake is a blockchain-based method for root zone governance.
+          Hence, it does not address the name resolution process itself but
+          delegates resolution into DNS after the initial TLD resolution.
+          Not taking sustainablility considerations into account, Handshake
+          could be used as an additional supporting GNS root zone governance
+          model, but we currently do not have such plans in mind.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("What is the difference between GNS and TrickleDNS?") }}</h3>
+          <p>
+          {% trans %}
+          A: TrickleDNS pushes (&quot;critical&quot;) DNS records between DNS resolvers
+          of participating domains to provide &quot;better availability, lower query
+          resolution times, and faster update propagation&quot;. Thus TrickleDNS is
+          focused on defeating attacks on the availability (and performance) of record
+          propagation in DNS, for example via DDoS attacks on DNS root servers.
+          TrickleDNS is thus concerned with how to ensure distribution of authoritative
+          records, and authority remains derived from the DNS hierarchy.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Does GNS require real-world introduction (secure PKEY exchange) in the style of the PGP web of trust?") }}</h3>
+          <p>
+          {% trans %}
+          A: For security, it is well known that an initial trust path between the two
+          parties must exist. However, for applications where this is not required,
+          weaker mechanisms can be used. For example, we have implemented a
+          first-come-first-served (FCFS) authority which allows arbitrary users to
+          register arbitrary names. The key of this authority is included with every
+          GNUnet installation. Thus, any name registered with FCFS is in fact global and
+          requires no further introduction. However, the security of these names
+          depends entirely on the trustworthiness of the FCFS authority.
+          The authority can be queried under the &quot;.pin&quot; TLD.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("How can a legitimate domain owner tell other people to not use his name in GNS?") }}</h3>
+          <p>
+          {% trans %}
+          A: Names have no owners in GNS, so there cannot be a &quot;legitimate&quot;
+          domain owner. Any user can claim any name (as his preferred name or
+          &quot;pseudonym&quot;) in his NICK record. Similarly, all other users can
+          choose to ignore this preference and use a name of their choice (or even
+          assign no name) for this user.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Did you consider the privacy implications of making your personal GNS zone visible?") }}</h3>
+          <p>
+          {% trans %}
+          A: Each record in GNS has a flag &quot;private&quot;. Records are shared with
+          other users (via DHT or zone transfers) only if this flag is not set.
+          Thus, users have full control over what information about their zones is made
+          public.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Are \"Legacy Host\" (LEHO) records not going to be obsolete with IPv6?") }}</h3>
+          <p>
+          {% trans %}
+          A: The question presumes that (a) virtual hosting is only necessary because of
+          IPv4 address scarcity, and (b) that LEHOs are only useful in the context of
+          virtual hosting. However, LEHOs are also useful to help with X.509 certificate
+          validation (as they specify for which legacy hostname the certificate should
+          be valid). Also, even with IPv6 fully deployed and &quot;infinite&quot; IP
+          addresses being available, we're not sure that virtual hosting would
+          disappear. Finally, we don't want to have to wait for IPv6 to become
+          commonplace, GNS should work with today's networks.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Why does GNS not use a trust metric or consensus to determine globally unique names?") }}</h3>
+          <p>
+          {% trans %}
+          A: Trust metrics have the fundamental problem that they have thresholds.
+          As trust relationships evolve, mappings would change their meaning as they
+          cross each others thresholds. We decided that the resulting unpredictability
+          of the resolution process was not acceptable. Furthermore, trust and consensus
+          might be easy to manipulate by adversaries.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("How do you handle compromised zone keys in GNS?") }}</h3>
+          <p>
+          {% trans %}
+          A: The owner of a private key can create a revocation message. This one can
+          then be flooded throughout the overlay network, creating a copy at all peers.
+          Before using a public key, peers check if that key has been revoked.
+          All names that involve delegation via a revoked zone will then fail to
+          resolve. Peers always automatically check for the existence of a revocation
+          message when resolving names.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Could the signing algorithm of GNS be upgraded in the future?") }}</h3>
+          <p>
+          {% trans %}
+          A: Yes. In our efforts to standardize GNS, we have already modified the protocol
+          to support alternative delegation records.
+          <br>
+          <br>
+          Naturally, deployed GNS implementations would have to be updated to support
+          the new signature scheme. The new scheme can then be run in parallel with
+          the existing system by using a new record type to indicate the use of a
+          different cipher system.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("How can a GNS zone maintain several name servers, e.g. for load balancing?") }}</h3>
+          <p>
+          {% trans %}
+          A: We don't expect this to be necessary, as GNS records are stored (and
+          replicated) in the R5N DHT. Thus the authority will typically not be contacted
+          whenever clients perform a lookup. Even if the authority goes (temporarily)
+          off-line, the DHT will cache the records for some time. However, should having
+          multiple servers for a zone be considered truly necessary, the owner of the
+          zone can simply run multiple peers (and share the zone's key and database
+          among them).
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Why do you believe it is worth giving up unique names for censorship resistance?") }}</h3>
+          <p>
+          {% trans %}
+          A: The GNU Name system offers an alternative to DNS that is censorship
+          resistant. As with any security mechanism, this comes at a cost (names are not
+          globally unique). To draw a parallel, HTTPS connections use more bandwidth and
+          have higher latency than HTTP connections. Depending on your application,
+          HTTPS may not be worth the cost. However, for users that are experiencing
+          censorship (or are concerned about it), giving up globally unique names may
+          very well be worth the cost. After all, what is a &quot;globally&quot; unique
+          name worth, if it does not resolve?
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Why do you say that DNS is 'centralized' and 'distributed'?") }}</h3>
+          <p>
+          {% trans %}
+          A: We say that DNS is 'centralized' because it has a central component /
+          central point of failure --- the root zone and its management by IANA/ICANN.
+          This centralization creates vulnerabilities. For example, the US government
+          was able to reassign the management of the country-TLDs of Afganistan and Iraq
+          during the wars at the beginning of the 21st century.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("How does GNS protect against layer-3 censorship?") }}</h3>
+          <p>
+          {% trans %}
+          A: GNS does not directly help with layer-3 censorship, but it does help
+          indirectly in two ways:
+          <ol>
+            <li> Many websites today use virtual hosting, so blocking a particular IP
+              address causes much more collateral damage than blocking a DNS name.
+              It thus raises the cost of censorship.</li>
+            <li> Existing layer-3 circumvention solutions (such as Tor) would benefit from
+              a censorship resistant naming system. Accessing Tor's &quot;.onion&quot;
+              namespace currently requires users to use unmemorable cryptographic
+              identifiers. With nicer names, Tor and tor2web-like services would be even
+              easier to use.
+          </ol>
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Does GNS work with search engines?") }}</h3>
+          <p>
+          {% trans %}
+          A: GNS creates no significant problems for search engines, as they can use GNS
+          to perform name resolution as well as any normal user. Naturally, while we
+          typically expect normal users to install custom software for name resolution,
+          this is unlikely to work for search engines today. However, the DNS2GNS
+          gateway allows search engines to use DNS to resolve GNS names, so they can
+          still index GNS resources. However, as using DNS2GNS gateways breaks the
+          cryptographic chain of trust, legacy search engines will obviously not obtain
+          censorship-resistant names.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("How does GNS compare to the Unmanaged Internet Architecture (UIA)?") }}</h3>
+          <p>
+          {% trans %}
+          A: UIA and GNS both share the same basic naming model, which actually
+          originated with Rivest's SDSI. However, UIA is not concerned about integration
+          with legacy applications and instead focuses on universal connectivity between
+          a user's many machines. In contrast, GNS was designed to interoperate with DNS
+          as much as possible, and to also work as much as possible with the existing
+          Web infrastructure. UIA is not at all concerned about legacy systems (clean
+          slate).
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Doesn't GNS increase the trusted-computing base compared to DNS(SEC)?") }}</h3>
+          <p>
+          {% trans %}
+          A: First of all, in GNS you can explicitly see the trust chain, so you know if
+          a name you are resolving belongs to a friend, or a friend-of-a-friend, and can
+          thus decide how much you trust the result. Naturally, the trusted-computing
+          base (TCB) can become arbitrarily large this way --- however, given the name
+          length restriction, for an individual name it is always less than about 128
+          entities.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("How does GNS handle SRV/TLSA records where service and protocol are part of the domain name?") }}</h3>
+          <p>
+          {% trans %}
+          A: When GNS splits a domain name into labels for resolution, it detects the
+          &quot;_Service._Proto&quot; syntax, converts &quot;Service&quot; to the
+          corresponding port number and &quot;Proto&quot; to the corresponding protocol
+          number. The rest of the name is resolved as usual. Then, when the result is
+          presented, GNS looks for the GNS-specific &quot;BOX&quot; record type.
+          A BOX record is a record that contains another record (such as SRV or TLSA
+          records) and adds a service and protocol number (and the original boxed record
+          type) to it.
+          {% endtrans %}
+          </p>
+        </section>
+        <hr/>
+        <h2><a name="errors" class="subnav-anchor"></a>{{ _("Error messages") }}</h2>
+        <section>
+          <h3>{{ _("I receive many &quot;WARNING Calculated flow delay for X at Y for Z&quot;. Should I worry?") }}</h3>
+          <p>
+          {% trans %}
+          A: Right now, this is expected and a known cause for high
+          latency in GNUnet.  We have started a major rewrite to address
+          this and other problems, but until the Transport Next
+          Generation (TNG) is ready, these warnings are expected.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Error opening `/dev/net/tun': No such file or directory?") }}</h3>
+          <p>
+          {% trans %}
+          A: If you get this error message, the solution is simple. Issue the following
+          commands (as root) to create the required device file
+          {% endtrans %}
+          <code class="block">
+            # mkdir /dev/net<br>
+            # mknod /dev/net/tun c 10 200<br>
+          </code>
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("'iptables: No chain/target/match by that name.' (when running gnunet-service-dns)?") }}</h3>
+          <p>
+          {% trans %}
+          A: For GNUnet DNS, your iptables needs to have &quot;owner&quot; match
+          support.
+          This is accomplished by having the correct kernel options. Check if your
+          kernel has CONFIG_NETFILTER_XT_MATCH_OWNER set to either 'y' or 'm' (and the
+          module is loaded).
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("'Timeout was reached' when running PT on Fedora (and possibly others)?") }}</h3>
+          <p>
+          {% trans %}
+          A: If you get an error stating that the VPN timeout was reached, check if your
+          firewall is enabled and blocking the connections.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("I'm getting an 'error while loading shared libraries: libgnunetXXX.so.X'") }}</h3>
+          <p>
+          {% trans %}
+          A: This error usually occurs when your linker fails to locate one of GNUnet's
+          libraries. This can have two causes. First, it is theoretically possible that
+          the library is not installed on your system; however, if you compiled GNUnet
+          the normal way and/or used a binary package, that is highly unlikely. The more
+          common cause is that you installed GNUnet to a directory that your linker
+          does not search. There are several ways to fix this that are described below.
+          If you are 'root' and you installed to a system folder (such as /usr/local),
+          you want to add the libraries to the system-wide search path. This is done by
+          adding a line "/usr/local/lib/" to /etc/ld.so.conf and running "ldconfig".
+          If you installed GNUnet to /opt or any other similar path, you obviously have
+          to change "/usr/local" accordingly.
+          If you do not have 'root' rights or if you installed GNUnet to say
+          "/home/$USER/", then you can explicitly tell your linker to search a
+          particular directory for libraries using the "LD_LIBRARY_PATH" environment
+          variable. For example, if you configured GNUnet using a prefix of
+          "$HOME/gnunet/" you want to run:
+          {% endtrans %}
+          </p>
+          <code>
+            $ export LD_LIBRARY_PATH=$HOME/gnunet/lib:$LD_LIBRARY_PATH<br>
+            $ export PATH=$HOME/gnunet/bin:$PATH
+          </code>
+          </p>
+          {% trans %}
+          to ensure GNUnet's binaries and libraries are found. In order to avoid having to do so each time, you can add the above lines (without the "$") to your .bashrc or .profile file. You will have to logout and login again to have this new profile be applied to all shells (including your desktop environment).
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("What error messages can be ignored?") }}</h3>
+          <p>
+          {% trans %}
+          A: Error messages flagged as "DEBUG" should be disabled in binaries
+          built for end-users and can always be ignored.
+          Error messages flagged as "INFO" always refer to harmless events that
+          require no action. For example, GNUnet may use an INFO message to
+          indicate that it is currently performing an expensive operation that
+          will take some time. GNUnet will also use INFO messages to display
+          information about important configuration values.
+          {% endtrans %}
+          </p>
+        </section>
+        <hr/>
+        <h2><a name="fs" class="subnav-anchor"></a>{{ _("File-sharing")}}</h2>
+        <section>
+          <h3>{{ _("How does GNUnet compare to other file-sharing applications?") }}</h3>
+          <p>
+          {% trans %}
+          A: As opposed to Napster, Gnutella, Kazaa, FastTrack, eDonkey and most
+          other P2P networks, GNUnet was designed with security in mind as the
+          highest priority. We intend on producing a network with comprehensive
+          security features. Many other P2P networks are open to a wide variety
+          of attacks, and users have little privacy. GNUnet is also Free
+          Software and thus the source code is available, so you do not have to
+          worry about being spied upon by the software. The following table
+          summarises the main differences between GNUnet and other systems.
+          The information is accurate to the best of our knowledge.
+          The comparison is difficult since there are sometimes differences
+          between various implementations of (almost) the same protocol.
+          In general, we pick a free implementation as the reference
+          implementation since it is possible to inspect the free code. Also,
+          all of these systems are changing over time and thus the data below
+          may not be up-to-date. If you find any flaws, please let us know.
+          Finally, the table is not saying terribly much (it is hard to compare
+          these systems this briefly), so if you want the real differences, read
+          the research papers (and probably the code).
+          {% endtrans %}
+          </p>
+          <table width="90%" border="0" cellpadding="0" cellspacing="0"><tbody><tr><th >Network</th>
+                <th ><a>GNUnet FS</a></th>
+                <th ><a>OneSwarm</th>
+                <th ><a>Napster</th>
+                <th ><a>Direct Connect</th>
+                <th ><a>FastTrack</th>
+                <th ><a>eDonkey</th>
+                <th ><a>Gnutella</th>
+                <th ><a>Freenet</th>
+              </tr><tr><th >Distributed Queries</th>
+                <td >yes</td>
+                <td >yes</td>
+                <td >no</td>
+                <td >hubs</td>
+                <td >super-peers</td>
+                <td >DHT (eMule)</td>
+                <td >yes</td>
+                <td >yes</td>
+              </tr><tr><th >Multisource Download</th>
+                <td >yes</td>
+                <td >yes</td>
+                <td >no</td>
+                <td >no</td>
+                <td >yes</td>
+                <td >yes</td>
+                <td >yes</td>
+                <td >no</td>
+              </tr><tr><th >Economics</th>
+                <td >yes</td>
+                <td >yes</td>
+                <td >no</td>
+                <td >no</td>
+                <td >no</td>
+                <td >yes</td>
+                <td >no</td>
+                <td >no</td>
+              </tr><tr><th >Anonymity</th>
+                <td >yes</td>
+                <td >maybe</td>
+                <td >no</td>
+                <td >no</td>
+                <td >no</td>
+                <td >no</td>
+                <td >no</td>
+                <td >yes</td>
+              </tr><tr><th >Language</th>
+                <td >C</td>
+                <td >Java</td>
+                <td >often C</td>
+                <td >C++</td>
+                <td >C</td>
+                <td >C++</td>
+                <td >often C</td>
+                <td >Java</td>
+              </tr><tr><th >Transport Protocol</th>
+                <td >UDP, TCP, SMTP, HTTP</td>
+                <td >TCP</td>
+                <td >TCP</td>
+                <td >TCP?</td>
+                <td >UDP, TCP</td>
+                <td >UDP, TCP</td>
+                <td >TCP</td>
+                <td >TCP</td>
+              </tr><tr><th >Query Format (UI)</th>
+                <td >keywords / CHK</td>
+                <td >filename / SHA?</td>
+                <td >keywords</td>
+                <td >filename, THEX</td>
+                <td >filename, SHA</td>
+                <td >filename, MD4?</td>
+                <td >filename, SHA</td>
+                <td >secret key, CHK</td>
+              </tr><tr><th >Routing</th>
+                <td >dynamic (indirect, direct)</td>
+                <td >static (indirect, direct)</td>
+                <td >always direct</td>
+                <td >always direct</td>
+                <td >always direct</td>
+                <td >always direct</td>
+                <td >always direct</td>
+                <td >always indirect</td>
+              </tr><tr><th >License</th>
+                <td >GPL</td>
+                <td >GPL</td>
+                <td >GPL (knapster)</td>
+                <td >GPL (Valknut)</td>
+                <td >GPL (giFT)</td>
+                <td >GPL (eMule)</td>
+                <td >GPL (gtk-gnutella)</td>
+                <td >GPL</td>
+              </tr></tbody>
+          </table>
+          <p>
+          {% trans %}
+          Another important point of reference are the various anonymous
+          peer-to-peer networks.
+          Here, there are differences in terms of application domain and how
+          specifically anonymity is achieved.
+          Anonymous routing is a hard research topic, so for a superficial
+          comparison like this one we focus on the latency.
+          Another important factor is the programming language.
+          Type-safe languages may offer certain security benefits; however, this may come at the cost of significant increases in resource consumption which in turn may reduce anonymity.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("Are there any known attacks (on GNUnet's file-sharing application)?") }}</h3>
+          <p>
+          {% trans %}
+          A: Generally, there is the possibility of a known plaintext attack on
+          keywords, but since the user has control over the keywords that are
+          associated with the content he inserts, the user can take advantage of
+          the same techniques used to generate reasonable passwords to defend
+          against such an attack. In any event, we are not trying to hide
+          content; thus, unless the user is trying to insert information into
+          the network that can only be shared with a small group of people,
+          there is no real reason to try to obfuscate the content by choosing a
+          difficult keyword anyway.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("What do you mean by anonymity?") }}</h3>
+          <p>
+          {% trans %}
+          A: Anonymity is the lack of distinction of an individual from a
+          (large) group. A central goal for anonymous file-sharing in GNUnet is
+          to make all users (peers) form a group and to make communications in
+          that group anonymous, that is, nobody (but the initiator) should be
+          able to tell which of the peers in the group originated the message.
+          In other words, it should be difficult to impossible for an adversary
+          to distinguish between the originating peer and all other peers.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("What does my system do when participating in GNUnet file sharing?") }}</h3>
+          <p>
+          {% trans %}
+          A: In GNUnet you set up a node (a peer). It is identified by an ID (hash
+          of its public key) and has a number of addresses it is reachable by
+          (may have no addresses, for instance when it's behind a NAT).
+          You specify bandwidth limits (how much traffic GNUnet is allowed to
+          consume) and datastore quote (how large your on-disk block storage is)
+          . Your node will then proceed to connect to other nodes, becoming
+          part of the network.
+          {% endtrans %}
+          </p>
+        </section>
+        <hr/>
+        <h2><a name="contrib" class="subnav-anchor"></a>{{ _("Contributing")}}</h2>
+        <section>
+          <h3>{{ _("How can I help translate this webpage into other languages?") }}</h3>
+          <p>
+          {% trans %}
+          A: First, you need to register an account with our weblate system.
+          Please send an e-mail with the desired target language to
+          translators@gnunet.org or ask for help on the #gnunet chat on
+          irc.freenode.net. Typically someone with sufficient permissions will
+          then grant you access. Naturally, any abuse will result in the loss
+          of permissions.
+          {% endtrans %}
+          </p>
+        </section>
+        <section>
+          <h3>{{ _("I have some great idea for a new feature, what should I do?") }}</h3>
+          <p>
+          {% trans %}
+          A: Sadly, we have many more feature requests than we can possibly
+          implement. The best way to actually get a new feature implemented is
+          to do it yourself --- and to then send us a patch.
+          {% endtrans %}
+          </p>
+        </section>
+      </article>
+    </div> <!-- col -->
+  </div> <!-- row-->
+  <!--
+    <h2>{{ ("Q?") }}</h2>
+    <h2>{{ ("Q?") }}</h2>
+    <h2>{{ ("Q?") }}</h2>
+  -->
 </div>
 {% endblock body_content %}
diff --git a/template/gnurl.html.j2 b/template/gnurl.html.j2
index c9c5d8ba..5556bd17 100644
--- a/template/gnurl.html.j2
+++ b/template/gnurl.html.j2
@@ -395,9 +395,9 @@
          <h2>{{ _("Maintainer and Cryptographic signatures") }}</h3>
          <p>
            {% trans %}
-              gnurl/libgnurl is maintained by Nikita.
+              gnurl/libgnurl is looking for a new maintainer.
-              Releases after version 7.69.1 are signed with the OpenPGP Key
+              Releases after version 7.69.1 and up to version 7.72.0 were signed with the OpenPGP Key
-              <b>0xD6B570842F7E7F8D</b> (<a href="https://keys.openpgp.org/search?q=6115012DEA3026F62A98A556D6B570842F7E7F8D">keys.openpgp.org</a>, <a href="https://n0.is/pubkey.asc">n0.is</a>), with the key fingerprint
+              <b>0xD6B570842F7E7F8D</b> (<a href="https://keys.openpgp.org/search?q=6115012DEA3026F62A98A556D6B570842F7E7F8D">keys.openpgp.org</a>), with the key fingerprint
              <b>6115 012D EA30 26F6 2A98  A556 D6B5 7084 2F7E 7F8D</b>.
            {% endtrans %}
          </p>
diff --git a/template/gsoc.html.j2 b/template/gsoc.html.j2
index 5a8066f4..6fdc58be 100644
--- a/template/gsoc.html.j2
+++ b/template/gsoc.html.j2
@@ -9,8 +9,8 @@
  <div class="row">
    <div class="col-2 d-none d-lg-block"><!-- for large viewports show menu for better orientation -->
      <nav class="nav subnav position-fixed flex-column border-right" style="position:fixed">
-      <a class="nav-link" href="#current">{{ _("Ideas 2020") }}</a>
+      <a class="nav-link" href="#current">{{ _("Ideas 2021") }}</a>
-      <a class="nav-link" href="#past">{{ _("Past projects") }}</a>
+      <!--<a class="nav-link" href="#past">{{ _("Past projects") }}</a>-->
      <a class="nav-link" href="#finished">{{ _("Finished projects") }}</a>
      </nav>
    </div>
@@ -26,7 +26,85 @@
      </section>
-      <h2><a name="current" class="subnav-anchor"></a>{{ _("Ideas 2020") }}</h2>
+      <h2><a name="current" class="subnav-anchor"></a>{{ _("Ideas 2021") }}</h2>
+      <section>
+        <h4>Transport Next Generation (TNG): Communicator plugins</h4>
+        <p>
+          {% trans %}
+            The GNUnet team is currently working on a transport layer rewrite
+            in order to fix core issues with connectivity.
+            This new component is currently developed under the name "TNG".
+            What is currently known as "transport plugins" will in the TNG
+            be represented as "communicators".
+            Communicators are processes with a well defined API that allow
+            to connect peers over a specific protocol.
+            The primary protocol which are already implemented are UNIX sockets,
+            UDP sockets, and TCP sockets.
+            For a truly resilient network, other connectivity options such as
+            WiFi mesh, Bluetooth, HTTP(S), QUIC or even more obscure alternatives
+            such as radio are required.
+            In this project, the goal is to select, implement and test new
+            communicators.
+            While TNG is not yet ready, communicators can, by design, be developed
+            and tested against the current API.
+            We expect that this project can be worked on by multiple students
+            as there are a lot of protocols to choose from.
+            The tasks would consist of:
+            <ol>
+              <li>Deciding which communicators to implement.</li>
+              <li>Test the communicators.</li>
+              <li>Documentation.</li>
+            </ol>
+            Advantageous skills/languages/frameworks:
+            <ol>
+              <li>C</li>
+              <li>Knowledge of HTTPS, QUIC, Bluetooth or WiFi.</li>
+            </ol>
+            <br/>
+            <strong>Difficulty:</strong> Average, but depends on selected protocols.
+            <br/>
+            <strong>Mentors:</strong> Martin Schanzenbach, t3sserakt
+          {% endtrans %}
+        </p>
+      </section>
+      <section>
+        <h4>REST: Multi-user support</h4>
+        <p>
+          {% trans %}
+            The REST API currently only supports a single user system.
+            This is an issue as on multi-user systems, access control
+            must be enfoced on a per-user basis.
+            In this project, the REST service must be extended to
+            support user authentication.
+            This includes the correct handling of user context switches.
+            <ol>
+              <li>Implement user authentication.</li>
+              <li>Test the access control.</li>
+              <li>Document the changes to the REST API.</li>
+            </ol>
+            Advantageous skills/languages/frameworks:
+            <ol>
+              <li>C</li>
+              <li>Knowledge of user authentication subsystems on Linux/Unix.</li>
+              <li>REST/HTTP Authentication methods</li>
+            </ol>
+            <br/>
+            <strong>Difficulty:</strong> Beginner
+            <br/>
+            <strong>Mentors:</strong> Martin Schanzenbach
+          {% endtrans %}
+        </p>
+      </section>
      <section>
        <h4>re:claimID/GNUnet Browser Plugin</h4>
        <p>
@@ -103,8 +181,38 @@
        </p>
      </section>
+      <section>
+        <h4>Rust templates for GNUnet services</h4>
+        <p>
+          {% trans %}
+          The goal is to either build upon the (outdated) <a href="https://github.com/canndrew/gnunet-rs">GNUnet Rust
+          bindings</a> or to follow the path of <a href="GNUnet Go">https://github.com/bfix/gnunet-go</a>
+          which tries to reimplement most of the GNUnet stack.
+          The end result should be an extension template for GNUnet in the form
+          of the existing <a href="https://git.gnunet.org/gnunet-ext.git/">C template</a>
+          which allows to quickly start implementing services and libraries
+          for GNUnet.
+          {% endtrans %}
+        </p>
+        <p>
+          {% trans %}
+            <strong>Mentors:</strong> Martin Schanzenbach
+          {% endtrans %}
+        </p>
+        <p>
+          {% trans %}
+            Required Skills: Solid knowledge of Rust and ideally asynchronuous IO.
+          {% endtrans %}
+        </p>
+        <p>
+          {% trans %}
+            Difficulty level: medium
+          {% endtrans %}
+        </p>
+      </section>
      <!-- Past projects: Previously proposed, but left unfinished. Inspiration for students. -->
-      <h2><a name="past" class="subnav-anchor"></a>{{ _("Past projects") }}</h2>
+      <!--<h2><a name="past" class="subnav-anchor"></a>{{ _("Past projects") }}</h2>
      <p>
        Past projects: Previously proposed, but left unfinished. Inspiration for students.
      </p>
@@ -183,42 +291,6 @@
        </p>
      </section>
      <section>
-        <h4>Rust APIs for GNUnet services</h4>
-        <p>
-          {% trans %}
-            There are a variety of GNUNet APIs that should be
-            exposed in the Rust wrappers.  Implementing these will
-            require extending the port of GNUNet utils written by
-            Andrew Cann and Kelong Cong.
-          {% endtrans %}
-        </p>
-        <p>
-          {% trans %}
-            As an introduction to the code base, we suggest that the
-            student and Jeff Burdges together update the
-            asynchronous IO system from gjio to futures-rs or
-            another layer built upon it.  Jeff Burdges is expected
-            to concurrently be implementing a GNUNet API for his own
-            mix network work.
-          {% endtrans %}
-        </p>
-        <p>
-          {% trans %}
-            <strong>Mentors:</strong> Jeff Burdges
-          {% endtrans %}
-        </p>
-        <p>
-          {% trans %}
-            Required Skills: Rust
-          {% endtrans %}
-        </p>
-        <p>
-          {% trans %}
-            Difficulty level: low
-          {% endtrans %}
-        </p>
-      </section>
-      <section>
        <h4>Tor compatibility for GNUnet</h4>
        <p>
          {% trans %}
@@ -520,6 +592,7 @@
          {% endtrans %}
        </p>
      </section>
+      -->
      <h2><a name="finished" class="subnav-anchor"></a>{{ _("Finished projects") }}</h2>
      <!-- Commentary: Finished projects, descriptions and Links to write-ups about them. -->
      <h3>2019</h3>
diff --git a/template/index.html.j2 b/template/index.html.j2
index 52d6a252..4114785f 100644
--- a/template/index.html.j2
+++ b/template/index.html.j2
@@ -2,25 +2,42 @@
 {% block body_content %}
 <!-- Jumbotron -->
 <div>
-  <div class="container text-center">
+  <div class="container">
    <div class="row">
      <div class="container text-center">
        <h1>{{ _("The Internet of tomorrow needs GNUnet today") }}</h1>
      </div>
    </div>
-      <div>
+    <div class="container text-center">
-        <img src="{{ url_static('images/gnunet-logo-dark-text.png') }}"  alt="GNUnet" />
+      <img src="{{ url_static('images/gnunet-logo-dark-text.png') }}"  alt="GNUnet" />
+    </div>
+  </div>
+</div>
+<div class="container-fluid">
+  <div class="container">
+      <div class="row">
+      <div class="col-lg-2 homepageicon">
+        <span class="fa fa-bullhorn"></span>
      </div>
-    <div class="row">
+      <div class="col-lg-6">
-      <div class="container text-center">
+      <section>
-        <a class="link" href="news/{{newsdata[0]['page']}}">{{ newsdata[0]['date'] }}: {{ newsdata[0]['title'] }}</a>
+        <h2>{{ _("Latest news") }}</h2>
+        <p>
+        {% for item in newsdata[:3] %}
+        <a class="link" href="{{ url_localized(item['page']) }}" title="{{ item['date']}}">{{ item['date'] }}: {{ item['title'] }}</a><br/>
+        {% endfor %}
+        <br/>
+        <a class="link" href="{{ url_localized('news/index.html')}}">{{ _("Older news entries") }}</a>
+        </p>
+        </section>
      </div>
    </div>
  </div>
 </div>
 <div class="container-fluid greybox">
  <div class="container">
    <div class="row">
@@ -259,6 +276,7 @@
      </div>
    </div>
  </div>
 </div>
 <hr style="padding: 2em;"/>
 <div class="container-fluid">
@@ -279,31 +297,4 @@
    </div>
  </div>
 </div>
-<!--<div class="container-fluid">
-  <div class="container">
-    <div class="row">
-      <div class="container text-center">
-        <h1>{{ _("News") }}<a name="news"></a></h1>
-      </div>
-    </div>
-    {% for item in newsdata[:4] %}
-    <div class="row">
-        <div class="col-lg-12">
-          <a href="news/{{ item['page'] }}" title="{{ item['date']}}">{{ item['date'] }}: {{ item['title'] }}</a>
-        </div>
-    </div>
-    {% endfor %}
-    <div class="row">
-      <div class="container text-center">
-        <p>
-          <a class="btn btn-primary btn-lg" href="{{ url_localized('news') }}">{{ _("News Archive") }}</a>
-        </p>
-      </div>
-    </div>
-  </div>
-</div>
-->
 {% endblock body_content %}
diff --git a/template/install-on-debian9.html.j2 b/template/install-on-debian9.html.j2
index 2e3ee95f..2a3cde03 100644
--- a/template/install-on-debian9.html.j2
+++ b/template/install-on-debian9.html.j2
@@ -35,7 +35,7 @@
  </p>
  <code>
-      $ sudo apt install git libtool autoconf autopoint libargon2-dev\<br>
+      $ sudo apt install git libtool autoconf autopoint libargon2-dev \<br>
      build-essential libgcrypt-dev libidn11-dev zlib1g-dev \<br>
      libunistring-dev libglpk-dev miniupnpc libextractor-dev \<br>
      libjansson-dev libcurl4-gnutls-dev gnutls-bin libsqlite3-dev \<br>
diff --git a/template/install-on-macos.html.j2 b/template/install-on-macos.html.j2
index e97efd75..b5c61cfb 100644
--- a/template/install-on-macos.html.j2
+++ b/template/install-on-macos.html.j2
@@ -164,7 +164,7 @@ vpn (gnunet-service-vpn)
  <p>
  You might see configure failing telling you that it ``cannot run C compiled programs.''.
  In this case, you might need to open/run Xcode once and you will be prompted to
-  install additonal packages.
+  install additional packages.
  Then, you might have to manually install the command line tools from here https://developer.apple.com/download/more/ (you need an Apple ID for this).
  Install those and execute
  </p>
diff --git a/template/install.html.j2 b/template/install.html.j2
index 2fccfd3c..588525ac 100644
--- a/template/install.html.j2
+++ b/template/install.html.j2
@@ -7,13 +7,11 @@
  </header>
  <div class="row container justify-content-center">
-    <div class="alert" style="background-color: #419edb;">
+    <div class="alert alert-info">
-      <div class="alert-content">
 {% trans %}
          Notice: GNUnet is still undergoing major development. It is
          largely <i>not yet ready</i> for usage beyond developers.
 {% endtrans %}
-      </div>
    </div>
 {% trans %}
 <p>Please be aware that this project is still in an early alpha
@@ -32,12 +30,12 @@ If you have any queries about the installation or the usage, please <a href="eng
    within your Operating System. GNUnet is reportedly available for at least:
    <ul>
      <li><a href="https://pkgs.alpinelinux.org/package/edge/testing/x86_64/gnunet">Alpine</a></li>
-      <li><a href="https://www.archlinux.org/packages/community/x86_64/gnunet/">Arch</a></li>
+      <li><a href="https://aur.archlinux.org/packages/gnunet/">Arch (AUR)</a></li>
      <li><a href="https://packages.debian.org/search?keywords=gnunet">Debian</a></li>
      <li><a href="https://copr.fedorainfracloud.org/coprs/yosl/gnunet/">Fedora (Copr)</a></li>
      <li><a href="https://guix.gnu.org/en/packages/G/">Guix</a></li>
      <li><a href="https://github.com/Homebrew/homebrew-core/blob/master/Formula/gnunet.rb">Homebrew</a></li>
-      <li><a href="https://nixos.org/nixos/packages.html?attr=gnunet&channel=nixpkgs-unstable&query=gnunet">NixOS</a></li>
+      <li><a href="https://search.nixos.org/packages?from=0&size=50&sort=relevance&query=gnunet">NixOS</a></li>
      <li><a href="install-on-openwrt.html">OpenWrt</a></li>
    </ul>
    If GNUnet is available for your Operating System and it is missing,
@@ -46,12 +44,12 @@ If you have any queries about the installation or the usage, please <a href="eng
    get in touch with us at gnunet-developers@gnu.org if you require
    help with this job.
-    If you were using an Operating System with the Alpine package manager,
+    If you were using an Operating System with the APT package manager,
    GNUnet could be installed as simple as:
    {% endtrans %}
  </p>
  <code class="block">
-    $ apk add gnunet
+    $ apt-get install gnunet
  </code>
  <p>
   Please beware that some distributions may include outdated GNUnet packages!
@@ -96,7 +94,7 @@ If you have any queries about the installation or the usage, please <a href="eng
  </div>
  <p>
   {% trans %}
-   Alternatively, get the sources from git by entering:
+   To compile gnunet from the git source you can do so by entering:
   {% endtrans %}
  </p>
  <code class="block">
@@ -153,15 +151,15 @@ If you have any queries about the installation or the usage, please <a href="eng
 <!--
  <div class="row container justify-content-center text-center">
    <div class="col-md">
-      <p><a href="install-on-ubuntu1804.html"><img src="{{ url('static/images/ubuntu-logo32.png') }}" class="distro-logo"></a></p>
+      <p><a href="install-on-ubuntu1804.html"><img src="{{ url('images/ubuntu-logo32.png') }}" class="distro-logo"></a></p>
      <h3>Ubuntu 18.04</h3>
    </div>
    <div class="col-md">
-      <p><a href="install-on-debian9.html"><img src="{{ url('static/images/debian-logo.svg') }}" class="distro-logo"></a></p>
+      <p><a href="install-on-debian9.html"><img src="{{ url('images/debian-logo.svg') }}" class="distro-logo"></a></p>
      <h3>Debian 9</h3>
    </div>
    <div class="col-md">
-      <p><a href="install-on-netbsd.html"><img src="{{ url('static/images/NetBSD_Logo.svg') }}" class="distro-logo"></a></p>
+      <p><a href="install-on-netbsd.html"><img src="{{ url('images/NetBSD_Logo.svg') }}" class="distro-logo"></a></p>
      <h3>NetBSD</h3>
    </div>
  </div>
@@ -171,15 +169,15 @@ If you have any queries about the installation or the usage, please <a href="eng
      <h1><a href="install-on-macos.html">Apple<br/>macOS</a></h1>
    </div>
    <div class="col-md">
-      <p><a href="install-on-archpi.html"><img src="{{ url('static/images/archlinux-logo.svg') }}" class="distro-logo" style="width:300px;height:auto"></a></p>
+      <p><a href="install-on-archpi.html"><img src="{{ url('images/archlinux-logo.svg') }}" class="distro-logo" style="width:300px;height:auto"></a></p>
      <h3>Arch Linux/Arch-Pi</h3>
    </div>
    <div class="col-md">
-      <p><a href="install-on-openwrt.html"><img src ="{{ url('static/images/openwrt-logo.svg') }}" class="distro-logo" style="width:300px;height:auto"></a></p>
+      <p><a href="install-on-openwrt.html"><img src ="{{ url('images/openwrt-logo.svg') }}" class="distro-logo" style="width:300px;height:auto"></a></p>
      <h3>OpenWrt</h3>
    </div>
    <div class="col-md">
-      <p><a href="https://wiki.gentoo.org/wiki/Overlay:Youbroketheinternet"><img alt="gentoo linux" src ="{{ url('static/images/gentoo-logo.svg') }}" class="distro-logo" style="width:170px;height:auto"></a></p>
+      <p><a href="https://wiki.gentoo.org/wiki/Overlay:Youbroketheinternet"><img alt="gentoo linux" src ="{{ url('images/gentoo-logo.svg') }}" class="distro-logo" style="width:170px;height:auto"></a></p>
    </div>
  </div>
 -->
diff --git a/template/livingstandards.html.j2 b/template/livingstandards.html.j2
new file mode 100644
index 00000000..86ceabd3
--- /dev/null
+++ b/template/livingstandards.html.j2
@@ -0,0 +1,27 @@
+{% extends "common/base.j2" %}
+{% block body_content %}
+  <div class="container-fluid">
+    <div class="container">
+      <article>
+        <div class="row">
+          <div class="container text-center">
+            <h1>Living Standards</h1>
+            <section>
+              <p>
+                {% trans %}
+                On this page you can find links to our technical specifications.
+                {% endtrans %}
+              </p>
+            </section>
+          </div>
+        </div>
+        <ul>
+          <li><b>LSD0000</b>: The Distributed Hash Table</li>
+          <li><b>LSD0001</b>: <a href="https://lsd.gnunet.org/lsd0001">The GNU Name System</a></li>
+          <li><b>LSD0002</b>: <a href="https://lsd.gnunet.org/lsd0002">re:claimID</a></li>
+          <li><b>LSD0003</b>: <a href="https://lsd.gnunet.org/lsd0003">Byzantine Fault Tolerant Set Reconciliation</a></li>
+        </ul>
+      </article>
+    </div>
+  </div>
+{% endblock body_content %}
diff --git a/template/news/2011-11-24-archived-vfork.html.j2 b/template/news/2011-11-24-archived-vfork.html.j2
new file mode 100644
index 00000000..61249c38
--- /dev/null
+++ b/template/news/2011-11-24-archived-vfork.html.j2
@@ -0,0 +1,62 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>vfork and the signal race</h1>
+<p>
+  <b>This is an imported news item from the old Drupal GNUnet homepage.</b>
+</p>
+<p>
+Many articles uniformly claim that using vfork should be
+<a href="https://web.archive.org/web/20150924082249/http://tldp.org/HOWTO/Secure-Programs-HOWTO/avoid-vfork.html">avoided</a>
+and that the only difference between vfork and fork is (or used-to-be)
+<a href="https://web.archive.org/web/20150924082249/http://www.unixguide.net/unix/programming/1.1.2.shtml">performance</a>
+and that thus vfork is
+<a href="https://web.archive.org/web/20150924082249/http://stackoverflow.com/questions/4856255/the-difference-between-fork-vfork-exec-and-clone">obsolete</a>.
+Here, I wanted to document a technical case where vfork is actually required and where using fork instead of vfork (or operating system implementors implementing vfork as an alias for fork) causes a hard-to-find data race.
+</p>
+<p>
+GNUnet uses a hypervisor process (gnunet-service-arm) to control the peer's service processes. Services are started (vfork+exec) on-demand. The hypervisor is also responsible for stopping the services and sends a SIGTERM signal to the services to stop them. SIGTERM must be used to allow the services to shutdown gracefully. Naturally, after shutting down a service with a signal, the hypervisor waits for SIGCHILD and then cleans up with waitpid. Once all services processes have completed, the hypervisor can exit as well. It should also be noted that the hypervisor handles SIGTERM (by shutting down all services), so a signal handler is installed for that signal.
+</p>
+<p>
+The reason why we must use vfork is the following. After the hypervisor has started the service, it might be asked to stop the service at any time. We've actually managed (by scripting it) to reliably trigger a case where the hypervisor would start a service (fork) and then receive a request to terminate the service and issues the SIGTERM signal to the child before the child process had a chance to call exec. As a result, the SIGTERM would go to the (existing) handler of the hypervisor's code, then the child process would be exec'ed and essentially the signal was thereby lost in the race between kill and exec:
+</p>
+<p>
+If exec wins, the signal either kills the process hard during the service startup phase, which is fine, or the service process might handle it normally and terminate --- also fine).
+</p>
+<p>
+If kill wins the race, the signal would be lost and the hypervisor would wait 'forever' for the child to terminate.
+</p>
+<p>
+The solution with vfork is elegant and simple: by blocking the parent, vexec guarantees that the parent's signal handler is no longer active (and replaced by default handlers or the child's custom handlers) by the time the parent is able to issue a 'kill'.
+</p>
+<p>
+In conclusion, with parents that issue 'kill' on child processes, the use of vfork can make an important semantic difference and not only (possibly) offer performance advantages. The situation above cannot be easily fixed by other means and thus vfork is an important POSIX call that should be supported properly by all quality implementations. A possible hack to work around a lack of vfork would be to create a pipe in the parent, set it to close-on-exec, fork the child, close the write end and then do a blocking read from the read end. Once you get a read error, the child has exec'ed. Rather ugly in my opinion.
+</p>
+<p>
+Currently, gnunet-service-arm can hang indefinitely on systems that do not provide a correct implementation of vfork (however, in practice normal users should never encounter this).
+</p>
+<p>
+<b>better suggestion from Thomas Bushnell</b>
+<br>
+I just got an alternative suggestion to using either a pipe and vfork from Thomas Bushnell, which I like and will use:
+"The hypervisor at start creates a global variable hypervisor_pid, initialized from getpid().
+The signal handler in the hypervisor then does this:
+<br>
+<code class="block">
+if getpid() == hypervisor_pid<br>
+  kill_all_children_and_exit();<br>
+else<br>
+  exit();<br>
+</code>
+In this way, if the child is between fork and exec when the parent gets its kill, and then it tries to kill the child, and the kill happens before the child execs (the problematic case you describe), then the child simply enters the hypervisor's signal handler, notices that it's not the hypervisor, and exits.
+<br>
+Thomas"
+<br>
+Thanks for the suggestion!
+</p>
+<p>
+Thomas's suggestion is all fine and well, except that it doesn't work on OS X. As the attached simple program "killing-child-kills-parent.c" demonstrates, OS X manages to sometimes either deliver the signal to the wrong process (?) or not update getpid() between fork+exec or is otherwise generally broken. The program simply installs a signal handler in the parent with the guard suggested by Thomas, then forks + exec's "sleep" and then immediately kills the child. So we expect the signal to either reach our signal handler (child between fork+exec), causing the child to 'exit', or to reach 'sleep' which should also die. Somehow instead the "Should NEVER get this signal!" message is printed. Well, OS X is known to be a pile of crap, so no surprise. Using 'vfork' instead of fork gets us the desired behavor -- howver, this is clearly just a hack. So vfork is back (on OS X) as of SVN 25495.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2013-11-15-special-use-gns.html.j2 b/template/news/2013-11-15-special-use-gns.html.j2
new file mode 100644
index 00000000..329e74d3
--- /dev/null
+++ b/template/news/2013-11-15-special-use-gns.html.j2
@@ -0,0 +1,14 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>Special-Use Domain Names of Peer-to-Peer Name Systems</h1>
+<p>
+  <b>This is an imported news item from the old Drupal GNUnet homepage.</b>
+</p>
+<p>
+We just submitted our draft for
+<a href="https://web.archive.org/web/20140901155643/https://datatracker.ietf.org/doc/draft-grothoff-iesg-special-use-p2p-names/">Special-Use Domain Names of Peer-to-Peer Name Systems</a> to IETF.
+The intention is to reserve the TLDs ".exit", ".i2p", ".gnu",
+".onion" and ".zkey" for use by the GNUnet, I2P and Tor peer-to-peer overlay
+networks.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2013-12-28-archived-typos-pkeys.html.j2 b/template/news/2013-12-28-archived-typos-pkeys.html.j2
new file mode 100644
index 00000000..a541ef94
--- /dev/null
+++ b/template/news/2013-12-28-archived-typos-pkeys.html.j2
@@ -0,0 +1,16 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>Typo-Protected Public Keys</h1>
+<p>
+  <b>This is an imported news item from the old Drupal GNUnet homepage.</b>
+</p>
+<p>
+When users type in public keys (such as the 53-characters of a GNS zone), they might make typos. The usual way to fix typos is to add a checksum, further increasing the length of the sequence that has to be typed in.
+<br>
+We can fix this by including the checksum of the public key in the public key itself, simply by trying new private keys until the corresponding public key happens to have a checksum (over the other bits) in the bits designated for the checksum. If a checksum is 16 bits, we would only need to try 216 keys. The basic idea of brute-forcing keys to match a particular pattern <a href="https://web.archive.org/web/20141008173738/https://bitcointalk.org/index.php?topic=84569.0">was proposed before</a> for creating "vanity" public keys, but this might be another practical variant.
+</p>
+<p>
+<b>Acknowledgements</b><br/>
+The idea popped up in a discussion on the need for short public keys for GNS with Dan Bernstein and Tanja Lange at 30c3.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2018-06.html.j2 b/template/news/2018-06.html.j2
new file mode 100644
index 00000000..08428466
--- /dev/null
+++ b/template/news/2018-06.html.j2
@@ -0,0 +1,108 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNUnet 0.11.0pre66</h1>
+<p>
+  We are pleased to announce the release of GNUnet 0.11.0pre66.<br>
+  This is a pre-release to assist developers and downstream packagers to test the package before the final release after four years of development.
+</p>
+<p>
+  In terms of usability, users should be aware that there are still a very large number of known open issues in particular with respect to ease of use, but also some critical privacy issues especially for mobile users. Also, the nascent network is tiny (~200 peers) and thus unlikely to provide good anonymity or extensive amounts of interesting information. As a result, the 0.11.0 release and especially this pre-release are only suitable for early adopters with some reasonable pain tolerance. 
+</p>
+<h4 class="western">License change</h4>
+<p>
+  GNUnet 0.11.0pre66 is the first release that will be made under the GNU Affero General Public License v3+. After a significant amount of internal discussion lead constructively by lynX (thanks!), the conclusion has been that the IPC and REST APIs should be extended with support for an GNUNET_MESSAGE_TYPE_AGPL or /agpl request that enables users of these client/service-style APIs to download the source code.
+</p>
+<p>
+  Naturally, the discussion on licensing may not necessarily end here, but at this point we are not aware of any dissent in the community and this release seems to be the right time to make such a change. While the final decision was not subjected to a broad feedback round, this was done simply on the grounds that this placement of the AGPL API seems to addresses all concerns that were raised. Finally, thanks to the copyright assignment all developers are participating in, the community will be able to revise this decision later if necessary.
+</p>
+<p>
+  It should also be noted that this change does not impose additional restrictions on the licensing models of GNU Taler or pEp: both projects have agreements with GNUnet e.V. that ensure that they can make decisions that fit these applications (not to mention significant parts of GNU Taler are already AGPLv3+ already).
+</p>
+<h4 class="western">About GNUnet</h4>
+<p>
+  GNUnet is a framework for secure peer-to-peer networking. GNUnet&#39;s primary design goals are to protect the privacy of its users and to guard itself against attacks or abuse. At this point, GNUnet offers four primary applications on top of the framework:
+</p>
+<p>
+  The file-sharing service allows anonymous censorship-resistant file-sharing. Files, searches and search results are encrypted to make it hard to control, track or censor users. GNUnet&#39;s anonymity protocol (gap) is designed to make it difficult to link users to their file-sharing activities. Users can also individually trade-off between performance and anonymity. Despite providing anonymity, GNUnet&#39;s excess-based economy rewards contributing users with better performance.
+</p>
+<p>
+  The VPN service allows offering of services within GNUnet (using the .gnu TLD) and can be used to tunnel IPv4 and IPv6 traffic over the P2P network. The VPN can also be used for IP protocol translation (6-to-4, 4-to-6) and it is possible to tunnel IP traffic over GNUnet (6-over-4, 4-over-6). Note that at this stage, it is possible for peers to determine the IP address at which services are hosted, so the VPN does not offer anonymity.
+</p>
+<p>
+  The GNU Name System (GNS) provides a fully-decentralized and censorship resistant replacement for DNS. GNS can be used alongside DNS and can be integrated with legacy applications (such as traditional browsers) with moderate effort. GNS provides censorship-resistance, memorable names and cryptographic integrity protection for the records. Note that at this stage, it is possible for a strong adversary to determine which peer is responsible for a particular zone, GNS does not offer strong anonymity. However, GNS offers query privacy, that is other participants can typically not decrypt queries or replies.
+</p>
+<p>
+  Conversation allows voice calls to be made over GNUnet. Users are identified using GNS and voice data is encrypted. However, Conversation does not provide anonymity at this stage --- other peers may observe a connection between the two endpoints and it is possible to determine the IP address associated with a phone.
+</p>
+<p>
+  Other applications, including in particular the SecuShare social networking application, are still strictly experimental.
+</p>
+<p>
+  For developers, GNUnet offers:
+</p>
+<ul>
+  <li>Access to all subsystems via clean C APIs</li>
+  <li>Mostly written in C, but extensions possible in other languages</li>
+  <li>Multi-process architecture for fault-isolation between components</li>
+  <li>Use of event loop and processes instead of threads for ease of development</li>
+  <li>Extensive logging and statistics facilities</li>
+  <li>Integrated testing library for automatic deployment of large-scale experiments with tens of thousands of peers</li>
+</ul>
+<h4 class="western">Noteworthy improvements in 0.11.0pre66</h4>
+<ul>
+  <li>Improved documentation, converting Drupal handbook to Texinfo (thanks ng0!)</li>
+  <li>GNU Name System now can take over arbitrary TLDs, and support for conversion from DNS zones to GNS exists</li>
+  <li>Critical bugfixes in CORE, DHT and CADET subsystems</li>
+</ul>
+<p>
+  The above is just the short list, our bugtracker lists over 350 individual issues that were resolved (see <a href="https://gnunet.org/bugs/changelog_page.php">Changelog</a>)
+</p>
+<h4 class="western">Known Issues</h4>
+<p>
+  We have a few issues that are most likely not resolved in the final release. Users should be aware of these issues, which we hope to address shortly.
+</p>
+<ul>
+  <li>There are known major design issues in TRANSPORT, ATS and CORE which will need to be addressed for usability, performance and security.</li>
+  <li>There are known moderate implementation limitations in CADET that impact performance.</li>
+  <li>There are known moderate design issues in FS that also impact usability and performance.</li>
+  <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
+  <li>The Web site and manuals still need significant rework.</li>
+  <li>Subsystems related to SecuShare and RPS remain experimental.</li>
+</ul>
+<p>
+  In addition to this list, you may also want to consult our bug tracker at https://gnunet.org/bugs/ which lists about 200 more specific issues.
+</p>
+<h4>Availability</h4>
+<p>
+  The GNUnet 0.11.0pre66 source code is available from all GNU FTP mirrors. The GTK frontends (which includes the gnunet-setup tool) are a separate download. Please note that some mirrors might still be synchronizing.
+</p>
+<ul>
+  <li>GNUnet on a FTP mirror near you http://ftpmirror.gnu.org/gnunet/gnunet-0.11.0pre66.tar.gz</li>
+  <li>GNUnet GTK on an FTP mirror near you http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0pre66.tar.gz</li>
+  <li>GNUnet FUSE on an FTP mirror near you http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0pre66.tar.gz</li>
+  <li>GNUnet on the primary GNU FTP server ftp://ftp.gnu.org/pub/gnu/gnunet/gnunet-0.11.0pre66.tar.gz</li>
+  <li>GNUnet GTK on the primary GNU FTP server ftp://ftp.gnu.org/pub/gnu/gnunet/gnunet-gtk-0.11.0pre66.tar.gz</li>
+  <li>GNUnet FUSE on the primary GNU FTP server ftp://ftp.gnu.org/pub/gnu/gnunet/gnunet-fuse-0.11.0pre66.tar.gz</li>
+</ul>
+<p>
+  Note that GNUnet is now started using &quot;gnunet-arm -s&quot;. GNUnet should be stopped using &quot;gnunet-arm -e&quot;.
+</p>
+<h4 class="western">Thanks</h4>
+<p>
+  This release was the work of many people. The following people contributed code and were thus easily identified:
+  Christian Grothoff,
+  Matthias Wachs, Bart Polot, Sree Harsha Totakura, Nathan S. Evans,
+  Martin Schanzenbach, Julius B&uuml;nger, Nils Gillmann, Philipp
+  T&ouml;lke, Florian Dold, &#1056;&#1091;&#1089;&#1083;&#1072;&#1085;
+  &#1048;&#1078;&#1073;&#1091;&#1083;&#1072;&#1090;&#1086;&#1074;,
+  tg(x), David Barksdale, Christian Fuchs, Nils Durner, Omar Tarabai,
+  Maximilian Szengel, Supriti Singh, lurchi, David Brodski, xrs, Fabian
+  Oehlmann, Carlo von lynX, Christophe Genevey Metat, Jeffrey Burdges,
+  Safey A.Halim, Daniel Golle, Phil, Bruno Cabral, Ji Lu, Heikki
+  Lindholm, Markus Teich, t3sserakt, Claudiu Olteanu, Marcello
+  Stanisci, Moon, anryko, Arthur Dewarumez, Julien Morvan, Adnan H, Lin
+  Tong, Andreas Fuchs, Christian Rupp, jah, Alejandra Morales, Matthias
+  Kolja Miehl, Andrew Cann, Antonio Ojea, Pascal Mainini, amirouche and
+  hark. 
+</p>
+{% endblock body_content %}
diff --git a/template/news/2018-07.html.j2 b/template/news/2018-07.html.j2
new file mode 100644
index 00000000..e8c14fea
--- /dev/null
+++ b/template/news/2018-07.html.j2
@@ -0,0 +1,7 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>Second GNUnet Hacker Meeting 2018 at La D&#233;centrale, Switzerland</h1>
+  <p>
+    The GNUnet hackers met for the second time this year. The primary goal was to squash bugs to bring out a new release. Aside from this we worked hard on improving the documentation and to launch this new website.
+  </p>
+{% endblock body_content %}
diff --git a/template/news/2019-0.11.0.html.j2 b/template/news/2019-0.11.0.html.j2
new file mode 100644
index 00000000..ddf04623
--- /dev/null
+++ b/template/news/2019-0.11.0.html.j2
@@ -0,0 +1,72 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNUnet 0.11.0 released</h1>
+  <p>
+    We are pleased to announce the release of GNUnet 0.11.0.<br>
+  This is a major release after about five years of development.  In terms of usability, users should be aware that there are still a large number of known open issues in particular with respect to ease of use, but also some critical privacy issues especially for mobile users. Also, the nascent network is tiny (about 200 peers) and thus unlikely to provide good anonymity or extensive amounts of interesting information.  As a result, the 0.11.0 release is still only suitable for early adopters with some reasonable pain tolerance.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.0.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig</a></li>
+</ul>
+<p>
+  Note that due to mirror synchronization, not all links might be functional early after the release. For direct access try <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<p>
+  Note that GNUnet is now started using <tt>gnunet-arm -s</tt>. GNUnet should be stopped using <tt>gnunet-arm -e</tt>.
+</p>
+<h4>Noteworthy changes in 0.11.0</h4>
+<ul>
+  <li>The Web site and manuals have undergone significant rework. You can find an archive of the old Web site at <a href="http://web.archive.org/web/*/gnunet.org">archive.org</a>.</li>
+  <li>The code now builds again on macOS. GNUnet on macOS is <i>experimental</i>. While it builds and seems to run fine, some tests are known to fail.</li>
+  <li>Build process now works properly with libidn2</li>
+  <li>Except for <tt>gnunet-qr</tt>, all Python code was migrated to Python 3.7.</li>
+  <li>Fixed security issues in secret sharing cryptography logic</li>
+  <li>Services running out of file descriptors on <tt>accept()</tt> no longer busy wait</li>
+  <li>Fixed crash in gnunet-gns2dns proxy</li>
+  <li>GNS responses are now padded to minimize information disclosure from the size</li>
+  <li>Fixed API issues and (rare) crash bugs in CADET</li>
+  <li>The experimental SecuShare code is not included in the release, you can now find it in the <a href="https://git.gnunet.org/gnunet-secushare.git/">gnunet-secushare</a> Git repository.</li>
+  <li>The Ascension tool (separate download) now allows importing DNS zones into GNS via AXFR.</li>
+  <li>GNUnet now includes a decentralised identity attribute sharing service: reclaimID. A ready-to-use client can be found in an <a href="https://gitlab.com/reclaimid/client">external repo</a>.</li>
+  <li>The code now builds again on NetBSD. GNUnet on NetBSD is <i>experimental</i>. While it builds and seems to run fine, full support requires more changes in the core of GNUnet It will soon be available via pkgsrc.</li>
+  <li>Many things changed on the build system side. If you package GNUnet for an operating system or otherwise package manager, make sure that you read the README.</li>
+</ul>
+<p>
+  The above is just the short list, our bugtracker lists <a href="https://bugs.gnunet.org/changelog_page.php?version_id=258">over 100 individual issues</a> that were resolved since 0.11.0pre66.
+</p>
+  <h4>Known Issues</h4>
+  <ul>
+    <li>There are known major design issues in the TRANSPORT, ATS and CORE subsystems which will need to be addressed in the future to achieve acceptable usability, performance and security.</li>
+    <li>There are known moderate implementation limitations in CADET that negatively impact performance. Also CADET may unexpectedly deliver messages out-of-order.</li>
+    <li>There are known moderate design issues in FS that also impact usability and performance.</li>
+    <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
+    <li>The RPS subsystem remains experimental.</li>
+    <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
+  </ul>
+<p>
+  In addition to this list, you may also want to consult our bug tracker at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a> which lists about 150 more specific issues.
+</p>
+<h4>Thanks</h4>
+<p>
+  This release was the work of many people. The following people
+  contributed code and were thus easily identified:
+  Christian Grothoff, Matthias Wachs, Bart Polot, Sree Harsha Totakura,
+  Nathan S. Evans, Martin Schanzenbach, Julius B&#xFC;nger, ng0,
+  Philipp T&#xF6;lke, Florian Dold, &#x420;&#x443;&#x441;&#x43B;&#x430;&#x43D; &#x418;&#x436;&#x431;&#x443;&#x43B;&#x430;&#x442;&#x43E;&#x432;, tg(x), David Barksdale,
+  Christian Fuchs, Nils Durner, Omar Tarabai, Maximilian Szengel, Supriti
+  Singh, lurchi, David Brodski, xrs, Fabian Oehlmann, Carlo von lynX,
+  Christophe Genevey Metat, Jeffrey Burdges, Safey A.Halim, Daniel Golle,
+  Phil, Bruno Cabral, Ji Lu, Heikki Lindholm, Markus Teich, t3sserakt,
+  Claudiu Olteanu, Marcello Stanisci, Moon, Hernani Marques, anryko, Arthur Dewarumez,
+  Julien Morvan, Adnan H, rexxnor, Lin Tong, Andreas Fuchs, Christian Rupp, jah,
+  Alejandra Morales, Bernd Fix, Feideus, Matthias Kolja Miehl, Andrew Cann, Antonio Ojea,
+  Pascal Mainini, amirouche and hark.
+  <a href="https://bugs.gnunet.org/view.php?id=5569">Special thanks</a> to Florian Weimer.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2019-0.11.1.html.j2 b/template/news/2019-0.11.1.html.j2
new file mode 100644
index 00000000..82f27c85
--- /dev/null
+++ b/template/news/2019-0.11.1.html.j2
@@ -0,0 +1,55 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNUnet 0.11.1 released</h1>
+<p>
+  We are pleased to announce the release of GNUnet 0.11.1.
+  <br>
+  This is a bugfix release for 0.11.0, mostly fixing minor bugs, improving documentation and fixing various build issues. In terms of usability, users should be aware that there are still a large number of known open issues in particular with respect to ease of use, but also some critical privacy issues especially for mobile users. Also, the nascent network is tiny (about 200 peers) and thus unlikely to provide good anonymity or extensive amounts of interesting information.  As a result, the 0.11.1 release is still only suitable for early adopters with some reasonable pain tolerance.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.1.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.1.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.1.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.1.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig</a></li>
+</ul>
+<p>
+  (gnunet-gtk and gnunet-fuse were not released again, as there were no changes and the 0.11.0 versions are expected to continue to work fine with gnunet-0.11.1.)
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional early after the release. For direct access try <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<p>
+  Note that GNUnet is now started using <tt>gnunet-arm -s</tt>. GNUnet should be stopped using <tt>gnunet-arm -e</tt>.
+</p>
+<h4>Noteworthy changes in 0.11.1</h4>
+<ul>
+  <li>gnunet-qr was rewritten in C, removing our last dependency on Python 2.x</li>
+  <li>REST and GNS proxy configuration options for address binding were added</li>
+  <li>gnunet-publish by default no longer includes creation time</li>
+  <li>Unreliable message ordering logic in CADET was fixed</li>
+  <li>Various improvements to build system and documentation</li>
+</ul>
+<p>
+  The above is just the short list, our bugtracker lists <a href="https://bugs.gnunet.org/changelog_page.php?version_id=312"> 14 individual issues</a> that were resolved since 0.11.0.
+</p>
+<h4>Known Issues</h4>
+<ul>
+  <li>There are known major design issues in the TRANSPORT, ATS and CORE subsystems which will need to be addressed in the future to achieve acceptable usability, performance and security.</li>
+  <li>There are known moderate implementation limitations in CADET that negatively impact performance. Also CADET may unexpectedly deliver messages out-of-order.</li>
+  <li>There are known moderate design issues in FS that also impact usability and performance.</li>
+  <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
+  <li>The RPS subsystem remains experimental.</li>
+  <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
+</ul>
+<p>
+  In addition to this list, you may also want to consult our bug tracker at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a> which lists about 190 more specific issues.
+</p>
+<h4>Thanks</h4>
+<p>
+  This release was the work of many people. The following people contributed code and were thus easily identified:
+  ng0, Christian Grothoff, Hartmut Goebel, Martin Schanzenbach, Devan Carpenter, Naomi Phillips and Julius B&#xFC;nger.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2019-0.11.2.html.j2 b/template/news/2019-0.11.2.html.j2
new file mode 100644
index 00000000..504a203c
--- /dev/null
+++ b/template/news/2019-0.11.2.html.j2
@@ -0,0 +1,55 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNUnet 0.11.2 released</h1>
+<p>
+  We are pleased to announce the release of GNUnet 0.11.2.
+<br>
+  This is a bugfix release for 0.11.0, mostly fixing minor bugs, improving documentation and fixing various build issues. In terms of usability, users should be aware that there are still a large number of known open issues in particular with respect to ease of use, but also some critical privacy issues especially for mobile users. Also, the nascent network is tiny (about 200 peers) and thus unlikely to provide good anonymity or extensive amounts of interesting information.  As a result, the 0.11.2 release is still only suitable for early adopters with some reasonable pain tolerance.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.2.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.2.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.2.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.2.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig</a></li>
+</ul>
+<p>
+  (gnunet-gtk and gnunet-fuse were not released again, as there were no changes and the 0.11.0 versions are expected to continue to work fine with gnunet-0.11.2.)
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional early after the release. For direct access try <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<p>
+  Note that GNUnet is now started using <tt>gnunet-arm -s</tt>. GNUnet should be stopped using <tt>gnunet-arm -e</tt>.
+</p>
+<h4>Noteworthy changes in 0.11.2</h4>
+<ul>
+  <li>gnunet-qr was rewritten in C, removing our last dependency on Python 2.x</li>
+  <li>REST and GNS proxy configuration options for address binding were added</li>
+  <li>gnunet-publish by default no longer includes creation time</li>
+  <li>Unreliable message ordering logic in CADET was fixed</li>
+  <li>Various improvements to build system and documentation</li>
+</ul>
+<p>
+  The above is just the short list, our bugtracker lists <a href="https://bugs.gnunet.org/changelog_page.php?version_id=312">14 individual issues</a> that were resolved since 0.11.0.
+</p>
+<h4>Known Issues</h4>
+<ul>
+  <li>There are known major design issues in the TRANSPORT, ATS and CORE subsystems which will need to be addressed in the future to achieve acceptable usability, performance and security.</li>
+  <li>There are known moderate implementation limitations in CADET that negatively impact performance. Also CADET may unexpectedly deliver messages out-of-order.</li>
+  <li>There are known moderate design issues in FS that also impact usability and performance.</li>
+  <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
+  <li>The RPS subsystem remains experimental.</li>
+  <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
+</ul>
+<p>
+  In addition to this list, you may also want to consult our bug tracker at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a> which lists about 190 more specific issues.
+</p>
+<h4>Thanks</h4>
+<p>
+  This release was the work of many people. The following people contributed code and were thus easily identified:
+  ng0, Christian Grothoff, Hartmut Goebel, Martin Schanzenbach, Devan Carpenter, Naomi Phillips and Julius B&#xFC;nger.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2019-0.11.3.html.j2 b/template/news/2019-0.11.3.html.j2
new file mode 100644
index 00000000..50b207a1
--- /dev/null
+++ b/template/news/2019-0.11.3.html.j2
@@ -0,0 +1,52 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNUnet 0.11.3 released</h1>
+<p>
+  We are pleased to announce the release of GNUnet 0.11.3.
+<br>
+  This is a bugfix release for 0.11.2, mostly fixing a few build issues. In terms of usability, users should be aware that there are still a large number of known open issues in particular with respect to ease of use, but also some critical privacy issues especially for mobile users. Also, the nascent network is tiny (about 200 peers) and thus unlikely to provide good anonymity or extensive amounts of interesting information.  As a result, the 0.11.3 release is still only suitable for early adopters with some reasonable pain tolerance.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.3.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.3.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.3.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.3.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig</a></li>
+</ul>
+<p>
+  (gnunet-gtk and gnunet-fuse were not released again, as there were no changes and the 0.11.0 versions are expected to continue to work fine with gnunet-0.11.3.)
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional early after the release. For direct access try <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<p>
+  Note that GNUnet is now started using <tt>gnunet-arm -s</tt>. GNUnet should be stopped using <tt>gnunet-arm -e</tt>.
+</p>
+<h4>Noteworthy changes in 0.11.3 (since 0.11.2)</h4>
+<ul>
+  <li>gnunet-zoneimport now handles <tt>-h</tt> correctly</li>
+  <li><tt>iptables</tt> and other similar binaries are no longer hard-coded but detected at configure time (with hard-coded fallback locations).</li>
+  <li><tt>make uninstall</tt> now properly uninstalls all files</li>
+  <li>Passing the no longer available <tt>--with-nssdir</tt> configuration option now results in a hard error.</li>
+  <li><tt>GNUNET_memcmp()</tt> and <tt>GNUNET_is_zero()</tt> macros introduced for improved type safety (but not yet used consistently).</li>
+</ul>
+<h4>Known Issues</h4>
+<ul>
+  <li>There are known major design issues in the TRANSPORT, ATS and CORE subsystems which will need to be addressed in the future to achieve acceptable usability, performance and security.</li>
+  <li>There are known moderate implementation limitations in CADET that negatively impact performance. Also CADET may unexpectedly deliver messages out-of-order.</li>
+  <li>There are known moderate design issues in FS that also impact usability and performance.</li>
+  <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
+  <li>The RPS subsystem remains experimental.</li>
+  <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
+</ul>
+<p>
+  In addition to this list, you may also want to consult our bug tracker at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a> which lists about 190 more specific issues.
+</p>
+<h4>Thanks</h4>
+<p>
+  This release was the work of many people. The following people contributed code and were thus easily identified:
+  ng0, Christian Grothoff, Daniel Golle, Martin Schanzenbach and Julius B&#xFC;nger.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2019-0.11.4.html.j2 b/template/news/2019-0.11.4.html.j2
new file mode 100644
index 00000000..9aad565f
--- /dev/null
+++ b/template/news/2019-0.11.4.html.j2
@@ -0,0 +1,50 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNUnet 0.11.4 released</h1>
+<p>
+  We are pleased to announce the release of GNUnet 0.11.4.
+<br>
+  This is a bugfix release for 0.11.3, mostly fixing a few build issues. In terms of usability, users should be aware that there are still a large number of known open issues in particular with respect to ease of use, but also some critical privacy issues especially for mobile users. Also, the nascent network is tiny (about 200 peers) and thus unlikely to provide good anonymity or extensive amounts of interesting information.  As a result, the 0.11.4 release is still only suitable for early adopters with some reasonable pain tolerance.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.4.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.4.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.4.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.4.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.0.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig</a></li>
+</ul>
+<p>
+  (gnunet-gtk and gnunet-fuse were not released again, as there were no changes and the 0.11.0 versions are expected to continue to work fine with gnunet-0.11.4.)
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional early after the release. For direct access try <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.11.4 (since 0.11.3)</h4>
+<ul>
+  <li><tt>gnunet-arm -s </tt> no longer logs into the console by default and instead into a logfile (in $GNUNET_HOME).</li>
+  <li>The reclaim subsystem is no longer experimental. See also <a href="https://reclaim-identity.io">re:claimID</a>. Further, the internal encryption scheme moved from ABE to GNS-style encryption.</li>
+  <li>GNUnet now depends on a more recent version of libmicrohttpd.</li>
+  <li>The REST API now includes read-only access to the configuration.</li>
+  <li>All manpages are now in mdocml format.</li>
+  <li><tt>gnunet-download-manager.scm</tt> removed.</li>
+</ul>
+<h4>Known Issues</h4>
+<ul>
+  <li>There are known major design issues in the TRANSPORT, ATS and CORE subsystems which will need to be addressed in the future to achieve acceptable usability, performance and security.</li>
+  <li>There are known moderate implementation limitations in CADET that negatively impact performance. Also CADET may unexpectedly deliver messages out-of-order.</li>
+  <li>There are known moderate design issues in FS that also impact usability and performance.</li>
+  <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
+  <li>The RPS subsystem remains experimental.</li>
+  <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
+</ul>
+<p>
+  In addition to this list, you may also want to consult our bug tracker at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a> which lists about 190 more specific issues.
+</p>
+<h4>Thanks</h4>
+<p>
+  This release was the work of many people. The following people contributed code and were thus easily identified:
+  ng0, Christian Grothoff, Daniel Golle, Martin Schanzenbach and Julius B&#xFC;nger.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2019-0.11.5.html.j2 b/template/news/2019-0.11.5.html.j2
new file mode 100644
index 00000000..049aa8b5
--- /dev/null
+++ b/template/news/2019-0.11.5.html.j2
@@ -0,0 +1,47 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNUnet 0.11.5 released</h1>
+<p>
+  We are pleased to announce the release of GNUnet 0.11.5.
+<br>
+  This is a bugfix release for 0.11.4, mostly fixing a few minor bugs and improving performance, in particular for identity management with a large number of egos. In the wake of this release, we also launched the <a href="https://rest.gnunet.org">REST API documentation</a>. In terms of usability, users should be aware that there are still a large number of known open issues in particular with respect to ease of use, but also some critical privacy issues especially for mobile users. Also, the nascent network is tiny (about 200 peers) and thus unlikely to provide good anonymity or extensive amounts of interesting information.  As a result, the 0.11.5 release is still only suitable for early adopters with some reasonable pain tolerance.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.5.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.5.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.5.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.5.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.5.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.5.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.5.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.5.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig</a></li>
+</ul>
+<p>
+  gnunet-gtk saw some minor changes to adopt it to API changes in the main code related to the identity improvements. gnunet-fuse was not released again, as there were no changes and the 0.11.0 version is expected to continue to work fine with gnunet-0.11.5.
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional early after the release. For direct access try <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.11.5 (since 0.11.4)</h4>
+<ul>
+  <li><tt>gnunet-identity</tt> is much faster when creating or deleting egos given a large number of existing egos.</li>
+  <li>GNS now supports CAA records.</li>
+  <li>Documentation, comments and code quality was improved.</li>
+</ul>
+<h4>Known Issues</h4>
+<ul>
+  <li>There are known major design issues in the TRANSPORT, ATS and CORE subsystems which will need to be addressed in the future to achieve acceptable usability, performance and security.</li>
+  <li>There are known moderate implementation limitations in CADET that negatively impact performance. Also CADET may unexpectedly deliver messages out-of-order.</li>
+  <li>There are known moderate design issues in FS that also impact usability and performance.</li>
+  <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
+  <li>The RPS subsystem remains experimental.</li>
+  <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
+</ul>
+<p>
+  In addition to this list, you may also want to consult our bug tracker at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a> which lists about 190 more specific issues.
+</p>
+<h4>Thanks</h4>
+<p>
+  This release was the work of many people. The following people contributed code and were thus easily identified:
+  Christian Grothoff, Florian Dold, Marcello Stanisci, ng0, Martin Schanzenbach and Bernd Fix.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2019-0.11.6.html.j2 b/template/news/2019-0.11.6.html.j2
new file mode 100644
index 00000000..3ee063b3
--- /dev/null
+++ b/template/news/2019-0.11.6.html.j2
@@ -0,0 +1,52 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNUnet 0.11.6 released</h1>
+<p>
+  We are pleased to announce the release of GNUnet 0.11.6.
+<br>
+  This is a bugfix release for 0.11.5, fixing a lot of minor bugs, improving stability and code quality. Further, our videos are back on the homepage. In this release, we again improved the webpage in general and updated our documentation. <i>As always:</i> In terms of usability, users should be aware that there are still <b>a large number of known open issues</b> in particular with respect to ease of use, but also some critical privacy issues especially for mobile users. Also, the nascent network is tiny (about 200 peers) and thus unlikely to provide good anonymity or extensive amounts of interesting information.  As a result, the 0.11.6 release is still <b>only suitable for early adopters with some reasonable pain tolerance</b>.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.6.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.6.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.6.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.6.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.6.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.6.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.6.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.6.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig</a></li>
+</ul>
+<p>
+  gnunet-fuse was not released again, as there were no changes and the 0.11.0 versions are expected to continue to work fine with gnunet-0.11.6.
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional early after the release. For direct access try <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.11.6 (since 0.11.5)</h4>
+<ul>
+  <li><tt>gnunet-identity</tt> can now print private keys.</li>
+  <li>The <tt>REST</tt> service can be configured to echo the HTTP Origin header value for Cross-Origin-Resource-Sharing (CORS) when it is called by a browser plugin. Optionally, a CORS Origin to echo can be also be directly configured.</li>
+  <li><tt>re:claimID</tt> tickets are now re-used whenever possible.</li>
+  <li>SUID binary detection mechanisms implemented to improve compatiblity with some distributions.</li>
+  <li><tt>TRANSPORT</tt>, <tt>TESTBED</tt> and <tt>CADET</tt> tests now pass again on macOS.</li>
+  <li><tt>CADET</tt>: Replaced enum <tt>GNUNET_CADET_ChannelOption</tt> with <tt>GNUNET_MQ_PriorityPreferences</tt> in preparation of API changed in the future.</li>
+  <li>The GNS proxy Certification Authority is now generated using gnutls-certtool, if available, with opennssl/certtool as fallback.</li>
+  <li>Documentation, comments and code quality was improved.</li>
+</ul>
+<h4>Known Issues</h4>
+<ul>
+  <li>There are known major design issues in the TRANSPORT, ATS and CORE subsystems which will need to be addressed in the future to achieve acceptable usability, performance and security.</li>
+  <li>There are known moderate implementation limitations in CADET that negatively impact performance.</li>
+  <li>There are known moderate design issues in FS that also impact usability and performance.</li>
+  <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
+  <li>The RPS subsystem remains experimental.</li>
+  <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
+</ul>
+<p>
+  In addition to this list, you may also want to consult our bug tracker at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a> which lists about 190 more specific issues.
+</p>
+<h4>Thanks</h4>
+<p>
+  This release was the work of many people. The following people contributed code and were thus easily identified:
+  Martin Schanzenbach, Julius B&uuml;nger, ng0, Christian Grothoff, Alexia Pagkopoulou, rexxnor, xrs, lurchi and t3sserakt.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2019-0.11.7.html.j2 b/template/news/2019-0.11.7.html.j2
new file mode 100644
index 00000000..f2b38231
--- /dev/null
+++ b/template/news/2019-0.11.7.html.j2
@@ -0,0 +1,56 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNUnet 0.11.7 released</h1>
+<p>
+  We are pleased to announce the release of GNUnet 0.11.7.
+<br>
+  This is a bugfix release for 0.11.6, fixing a lot of minor bugs, improving stability and code quality. Further, win32 support was removed for reasons you may read below. In this release, we again improved the webpage in general and updated our documentation. <i>As always:</i> In terms of usability, users should be aware that there are still <b>a large number of known open issues</b> in particular with respect to ease of use, but also some critical privacy issues especially for mobile users. Also, the nascent network is tiny (about 200 peers) and thus unlikely to provide good anonymity or extensive amounts of interesting information.  As a result, the 0.11.7 release is still <b>only suitable for early adopters with some reasonable pain tolerance</b>.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.7.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.7.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.7.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.7.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.7.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.7.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.7.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.7.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig</a></li>
+</ul>
+<p>
+  gnunet-fuse is not released again, as there were no changes and the 0.11.0 versions are expected to continue to work fine with gnunet-0.11.7. The GPG key used to sign is: <tt>A88C8ADD129828D7EAC02E52E22F9BBFEE348588</tt>
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional early after the release. For direct access try <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.11.7 (since 0.11.6)</h4>
+<ul>
+  <li><tt>ARM</tt>: GNUnet CLI tools are now able to detect if gnunet(-arm) is not running and will exit with a warning (before the command would just hang and wait for GNUnet to be started). #5906</li>
+  <li>win32 and mingw support were dropped, which resulted in a significant number of lines of code to be gone. The code has been unmaintained in our code base for many years and there are no known users. For details and further reasons refer to the discussion <a href="https://lists.gnu.org/archive/html/gnunet-developers/2019-09/msg00002.html">in our archives</a>.</li>
+  <li>Removal of plibc, win32 and mingw support means you can now compile gnunet without requiring a Cxx compiler (you just need a C compiler). #5877</li>
+  <li><tt>REST</tt>: The new config endpoints can now be used to read and write the GNUnet config. #5808</li>
+  <li><tt>REST</tt>: The service is not started per user in multiuser setups.</li>
+  <li><tt>REST</tt>: Added tests for namestore and GNS. #5638</li>
+  <li><tt>re:claimID / OIDC</tt>: Now supports <a href="https://tools.ietf.org/html/rfc7636">PKCE</a>. #5807</li>
+  <li>SUID binary detection mechanisms implemented to improve compatiblity with some distributions.</li>
+  <li><tt>CREDENTIAL</tt> subsystem reworked and renamed to <tt>ABD</tt> (attribute-based delegation).</li>
+  <li><a href="https://lists.gnu.org/archive/html/gnunet-developers/2019-10/msg00023.html">Minor TRANSPORT fixes</a> and <a href="https://lists.gnu.org/archive/html/gnunet-developers/2019-10/msg00022.html">NAT changes</a>.</li>
+  <li><tt>GNS</tt> prepared code for <a href="https://git.gnunet.org/lsd0001.git/tree/draft-schanzen-gns.txt">LSD001 changes</a>. #5920</li>
+  <li>Documentation, comments and code quality was improved.</li>
+</ul>
+<h4>Known Issues</h4>
+<ul>
+  <li>There are known major design issues in the TRANSPORT, ATS and CORE subsystems which will need to be addressed in the future to achieve acceptable usability, performance and security.</li>
+  <li>There are known moderate implementation limitations in CADET that negatively impact performance.</li>
+  <li>There are known moderate design issues in FS that also impact usability and performance.</li>
+  <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
+  <li>The RPS subsystem remains experimental.</li>
+  <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
+</ul>
+<p>
+  In addition to this list, you may also want to consult our bug tracker at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a> which lists about 190 more specific issues.
+</p>
+<h4>Thanks</h4>
+<p>
+  This release was the work of many people. The following people contributed code and were thus easily identified:
+  Martin Schanzenbach, ng0, Christian Grothoff, Alexia Pagkopoulou, Andreas Ebner, Corvus Corax, xrs and t3sserakt.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2019-0.11.8.html.j2 b/template/news/2019-0.11.8.html.j2
new file mode 100644
index 00000000..9a92eaac
--- /dev/null
+++ b/template/news/2019-0.11.8.html.j2
@@ -0,0 +1,47 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNUnet 0.11.8 released</h1>
+<p>
+  We are pleased to announce the release of GNUnet 0.11.8.
+<br>
+  This is a hotfix release for 0.11.7. <i>As always:</i> In terms of usability, users should be aware that there are still <b>a large number of known open issues</b> in particular with respect to ease of use, but also some critical privacy issues especially for mobile users. Also, the nascent network is tiny (about 200 peers) and thus unlikely to provide good anonymity or extensive amounts of interesting information.  As a result, the 0.11.8 release is still <b>only suitable for early adopters with some reasonable pain tolerance</b>.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.8.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.8.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.11.8.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.11.8.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.7.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.7.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.7.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.11.7.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.11.0.tar.gz.sig</a></li>
+</ul>
+<p>
+  gnunet-fuse and gnunet-gtk were not released again, as there were no changes and the 0.11.0/0.11.7 versions are expected to continue to work fine with gnunet-0.11.8. The GPG key used to sign is: <tt>A88C8ADD129828D7EAC02E52E22F9BBFEE348588</tt>
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional early after the release. For direct access try <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.11.8 (since 0.11.7)</h4>
+<ul>
+  <li><tt>GNS</tt> Portability fixes.</li>
+  <li><tt>PQ</tt>: Fixed build with postgresql plugin. (Regression introduces as part of #5733)</li>
+</ul>
+<h4>Known Issues</h4>
+<ul>
+  <li>There are known major design issues in the TRANSPORT, ATS and CORE subsystems which will need to be addressed in the future to achieve acceptable usability, performance and security.</li>
+  <li>There are known moderate implementation limitations in CADET that negatively impact performance.</li>
+  <li>There are known moderate design issues in FS that also impact usability and performance.</li>
+  <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
+  <li>The RPS subsystem remains experimental.</li>
+  <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
+</ul>
+<p>
+  In addition to this list, you may also want to consult our bug tracker at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a> which lists about 190 more specific issues.
+</p>
+<h4>Thanks</h4>
+<p>
+  This release was the work of many people. The following people contributed code and were thus easily identified:
+  ng0, Daniel Golle.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2019-0.12.0.html.j2 b/template/news/2019-0.12.0.html.j2
new file mode 100644
index 00000000..6cf68160
--- /dev/null
+++ b/template/news/2019-0.12.0.html.j2
@@ -0,0 +1,85 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNUnet 0.12.0 released</h1>
+<p>
+  We are pleased to announce the release of GNUnet 0.12.0.
+<br>
+  This is a new major release. It breaks protocol compatibility with the 0.11.x versions.
+  Please be aware that Git master is thus henceforth <b>INCOMPATIBLE</b> with
+  the 0.11.x GNUnet network, and interactions between old and new peers
+  will result in signature verification failures.  0.11.x peers will <b>NOT</b>
+  be able to communicate with Git master or 0.12.x peers.<br/>
+  In terms of usability, users should be aware that there are still
+  <b>a large number of known open issues</b> in particular with respect to ease
+  of use, but also some critical privacy issues especially for mobile users.
+  Also, the nascent network is tiny and thus unlikely to
+  provide good anonymity or extensive amounts of interesting information.
+  As a result, the 0.12.0 release is still <b>only suitable for early adopters
+  with some reasonable pain tolerance</b>.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.12.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.12.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.12.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.12.0.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.12.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.12.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.12.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.12.0.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.12.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.12.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.12.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.12.0.tar.gz.sig</a></li>
+</ul>
+<p>
+  The GPG key used to sign is: <tt>3D11063C10F98D14BD24D1470B0998EF86F59B6A</tt>
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional
+  early after the release. For direct access try
+  <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.12.0 (since 0.11.8)</h4>
+<ul>
+  <li><tt>GNS</tt>:
+    <ul>
+      <li>Changed key derivation protocols to adhere with <a href="https://git.gnunet.org/lsd0001.git/tree/draft-schanzen-gns.txt">LSD001</a>. <a href="https://bugs.gnunet.org/view.php?id=5921">#5921</a></li>
+      <li>Names are not expected to be UTF-8 (as opposed to IDNA). <a href="https://bugs.gnunet.org/view.php?id=5922">#5922</a></li>
+      <li>NSS plugin now properly handles non-standard IDNA names. <a href="https://bugs.gnunet.org/view.php?id=5927">#5927</a></li>
+      <li>NSS plugin will refuse to process requests from root (as GNUnet code should never run as root). <a href="https://bugs.gnunet.org/view.php?id=5927">#5907</a></li>
+      <li>Fixed BOX service/protocol label parsing (for TLSA et al)</li>
+    </ul>
+  </li>
+  <li><tt>GNS/NSE</tt>: Zone revocation proof of work algorithm changed to be less susceptible to specialized ASIC hardware.
+  <a href="https://bugs.gnunet.org/view.php?id=3795">#3795</a></li>
+  <li><tt>TRANSPORT</tt>: UDP plugin moved to experimental as it is known to be unstable.</li>
+  <li><tt>UTIL</tt>:
+    <ul>
+      <li>Improved and documented RSA binary format. <a href="https://bugs.gnunet.org/view.php?id=5968">#5968</a></li>
+      <li>Removed redundant hashing in EdDSA signatures. <a href="https://bugs.gnunet.org/view.php?id=5398">#5398</a></li>
+      <li>The <tt>gnunet-logread</tt> script for log auditing (requires perl) can now be installed.</li>
+      <li>Now using <a href="https://tweetnacl.cr.yp.to/">TweetNaCl</a> for ECDH implementation.</li>
+    </ul>
+  </li>
+  <li><tt>Buildsystem</tt>: A significant number of build system issued have been fixed and improvements implemented, including:
+    <ul>
+      <li>GLPK dependency dropped.</li>
+      <li>Fixed guix package definition.</li>
+    </ul>
+  </li>
+  <li><tt>Documentation</tt>: Improvements to the handbook and documentation.</li>
+</ul>
+<h4>Known Issues</h4>
+<ul>
+  <li>There are known major design issues in the TRANSPORT, ATS and CORE subsystems which will need to be addressed in the future to achieve acceptable usability, performance and security.</li>
+  <li>There are known moderate implementation limitations in CADET that negatively impact performance.</li>
+  <li>There are known moderate design issues in FS that also impact usability and performance.</li>
+  <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
+  <li>The RPS subsystem remains experimental.</li>
+  <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
+</ul>
+<p>
+  In addition to this list, you may also want to consult our bug tracker at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a> which lists about 190 more specific issues.
+</p>
+<h4>Thanks</h4>
+<p>
+  This release was the work of many people. The following people contributed code and were thus easily identified:
+  ng0, Christian Grothoff, Florian Dold, xrs, Naomi Phillips and Martin Schanzenbach.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2019-0.12.1.html.j2 b/template/news/2019-0.12.1.html.j2
new file mode 100644
index 00000000..7911fcd1
--- /dev/null
+++ b/template/news/2019-0.12.1.html.j2
@@ -0,0 +1,26 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNUnet 0.12.1 released</h1>
+<p>
+  We are pleased to announce the release of GNUnet 0.12.1.
+<br>
+  This is a very minor release. It largely fixes one function that is
+  needed by GNU Taler 0.6.0.  Please read the release notes
+  for GNUnet 0.12.0, as they still apply. Updating is only recommended
+  for those using GNUnet in combination with GNU Taler.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.12.1.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.12.1.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.12.1.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.12.1.tar.gz.sig</a></li>
+</ul>
+<p>
+  The GPG key used to sign is: <tt>D8423BCB326C7907033929C7939E6BE1E29FC3CC</tt>
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional
+  early after the release. For direct access try
+  <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+{% endblock body_content %}
diff --git a/template/news/2019-02.html.j2 b/template/news/2019-02.html.j2
new file mode 100644
index 00000000..0925eb75
--- /dev/null
+++ b/template/news/2019-02.html.j2
@@ -0,0 +1,75 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>2019-02: Topics for GSoC 2019</h1>
+<p>
+  GNUnet is participating in the Google Summer of Code again through GNU. If you are interested in any of these projects, reach out to us!
+</p>
+<section>
+  <h4>Android Port</h4>
+  <p>
+    It is time for GNUnet to run properly on Android.  Note that GNUnet is written in C, and this is not about rewriting GNUnet in Java, but about getting the C code to run on Android.<br>
+    Mentor: <a href="https://www.goebel-consult.de/">Hartmut Goebel</a>
+  </p>
+</section>
+<section>
+  <h4>Help with Continuous Integration setup</h4>
+  <p>
+    There is a push for migrating our CI to Gitlab.  The CI should eventually not just run "make check" on various platforms, but also perform tests with multiple peers running in different VMs with specific network topologies (i.e. NAT) between them being simulated. The CI should also be integrated with Gauger for performance regression analysis.  Running jobs only when dependencies have changed and scripting more granular triggers or ideally automatic dependency discovery (as done by the autotools) is also important.<br>
+    Mentor: TBD
+  </p>
+</section>
+<section>
+  <h4>Migrate gnunet-qr from Python 2.7 to C using libzbar</h4>
+  <p>
+    Python 2.7 is reaching its end-of-life, and we want to get rid of the dependency on Python. The existing gnunet-qr tool is a rather simple wrapper around python-zbar, which itself wraps  libzbar. The goal of this project is to directly use libzbar to scan QR codes for GNUnet / the GNU Name System (see also <a href="https://bugs.gnunet.org/view.php?id=5562">#5562</a>).<br>
+    Mentor: Christian Grothoff
+  </p>
+</section>
+<section>
+  <h4>re:claimID OpenID Connect performance improvements</h4>
+  <p>
+    reclaimID is a decentralized identity system build on top of the GNU Name System. Upon authorization, the user provides a requesting party (RP) such as a website with an authorization ticket (e.g. piggybacked in an OpenID authorization code). The RP uses information contained in this ticket to
+  </p>
+  <ol>
+    <li> Retrieve the decryption key from GNS</li>
+    <li> Retrieve the user attributes from GNS</li>
+  </ol>
+  <p>
+    The GNS lookups ensure that the RP receives up-to-date attributes and functional decryption keys. However, in particular the RP-specific encryption key resolution can be slow and even fail depending on the network topology. We propose that in an initial exchange, in particular OpenID authorization code flows, we try to incorporate key and maybe even an attribute set in the ticket exchange. In order to mitigate this issue, this project is meant to investigate and implement how...
+  </p>
+  <ol>
+    <li> ... decryption keys can be added to an initial exchange in OpenID.</li>
+    <li> ... initial set(s) of attributes can be piggybacked in OpenID.</li>
+  </ol>
+  <p>
+    Mentor: Martin Schanzenbach
+  </p>
+</section>
+<section>
+  <h4>re:claimID alternative GNS-based encryption</h4>
+  <p>
+    re:claimID is a decentralized identity system build on top of the GNU Name System. The initial design and implementation of re:claimID includes an attribute-based encryption module in order to prevent unauthorized access to attributes in the name system. Our motivation for re:claimID was for it to be name system agnostic, which means the design theoretically also works for other name systems such as namecoin. Other name systems often do not have built-in mechanisms in order to do this. Hence, we implemented an ABE access control layer. Our ABE implementation requires two third party libraries: libpbc and libgabe. While we could merge libgabe into the gnunet service implementation of re:claimID, libpbc is a rather large, third party library which lacks packaging in distributions and for platforms. On the other hand, GNS supports record data encryption using symmetric keys as labels. If we make the access control layer of re:claimID more generic in order to support both ABE and GNS encryption, we could reduce the required depenencies. This would result in gnunet packages to include re:claimID by default. In short, the goals are to...
+  </p>
+  <ol>
+    <li> ... improve performance by reducing encryption overhead.</li>
+    <li> ... reduce dependencies.</li>
+  </ol>
+  <p>
+    Mentor: Martin Schanzenbach
+  </p>
+</section>
+<section>
+  <h4>Enable all networking applications to run over GNUnet out of the box</h4>
+  <p>
+    One great problem of the current Internet is the lack of disintermediation. When people want to talk they need a chat service. When they want to share files they need a file transfer service. Although GNUnet already possesses quite advanced integration into Linux networking, a little extra work is needed for existing applications like irc, www, ftp, rsh, nntpd to run over it in a peer-to-peer way, simply by using a GNS hostname like friend.gnu. Once people have added a person to their GNS they can immediately message, exchange files and suchlike directly, with nothing but the GNUnet in the middle, using applications that have been distributed with unix systems ever since the 1980&#39;s. We can produce an OS distribution where these things work out of the box with the nicknames of people instead of cloud services. For more information and context, read <a href="https://bugs.gnunet.org/view.php?id=4625">bug id 4625</a>.
+  </p>
+  <p>
+    Mentors: lynX &amp; dvn
+  </p>
+</section>
+{% endblock body_content %}
diff --git a/template/news/2019-06-DSTJ.html.j2 b/template/news/2019-06-DSTJ.html.j2
new file mode 100644
index 00000000..0d1d3c67
--- /dev/null
+++ b/template/news/2019-06-DSTJ.html.j2
@@ -0,0 +1,14 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>Peer DSTJ is dead, long live peer Y924</h1>
+<p>
+  After some issues with our infrastructure we needed to replace our bootstrapping peer. To avoid problems when connecting to GNUnet the operator of a peer needs to update its node by removing the peer ID <i>DSTJBRRKZ8TBW3FGK6B0M5QXWT9WYNZ45H5MCV4HY7ST64Q8T9F0</i> from the system. Here are two strategies to find copies of the respective file:
+</p>
+<ol>
+  <li><tt>$ locate DSTJBRRKZ8TBW3FGK6B0M5QXWT9WYNZ45H5MCV4HY7ST64Q8T9F0</tt></li>
+  <li><tt>$ find / -name DSTJBRRKZ8TBW3FGK6B0M5QXWT9WYNZ45H5MCV4HY7ST64Q8T9F0</tt></li>
+</ol>
+<p>
+  Update: DSTJ has now been blacklisted. Please update your GNUnet peer.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2019-06.html.j2 b/template/news/2019-06.html.j2
new file mode 100644
index 00000000..295138b9
--- /dev/null
+++ b/template/news/2019-06.html.j2
@@ -0,0 +1,7 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNUnet Hacker Meeting 2019 at La D&#233;centrale, Switzerland</h1>
+  <p>
+    The members of the GNUnet community met again in the wonderful souroundings of St. Imier to hack on GNUnet. New people joined our sessions until late at night. From bug squashing to digging our own dog food, from workshops to theoretical discussions of new services and usecases. And of course, pizza was in the game. 
+  </p>
+{% endblock body_content %}
diff --git a/template/news/2019-07-GHM_Aug_2019.html.j2 b/template/news/2019-07-GHM_Aug_2019.html.j2
new file mode 100644
index 00000000..c846432e
--- /dev/null
+++ b/template/news/2019-07-GHM_Aug_2019.html.j2
@@ -0,0 +1,7 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNUnet Hacker Meeting in August 2019 at Wernsdort (near Berlin)</h1>
+  <p>
+    In August 2019, some of us met in Wernsdorf for focused work on GNUnet.
+  </p>
+{% endblock body_content %}
diff --git a/template/news/2019-10-GNSSpec1.html.j2 b/template/news/2019-10-GNSSpec1.html.j2
new file mode 100644
index 00000000..3941c162
--- /dev/null
+++ b/template/news/2019-10-GNSSpec1.html.j2
@@ -0,0 +1,19 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNS Technical Specification Milestone 1/4</h1>
+<p>
+  We are happy to announce the completion of the first milestone for the GNS Specification. The objective is to provide a detailed and comprehensive guide for implementors of the GNU Name System. The initial milestone consists of documenting the cryptographic principles of GNS data structures. This includes the specification of the GNS record wire and serialization formats as well as internationalization.<br>
+  <i>NOTE: The currently specified protocol is planned to be implemented for GNUnet 0.12. The current GNS implementation (0.11) exhibits minor but compatibility breaking deviations from this specification.</i> The draft specification <b>LSD001</b> can be found at:
+</p>
+<ul>
+  <li>Git: <a href="git://gnunet.org/lsd0001.git">LSD001</a></li>
+  <li><a href="https://git.gnunet.org/lsd0001.git/tree/draft-schanzen-gns.txt">Link to TXT version</a></li>
+  <li><a href="https://git.gnunet.org/lsd0001.git/tree/draft-schanzen-gns.html">Link to HTML version</a></li>
+</ul>
+<p>
+  The next milestone will bring the resolver logic specification.
+</p>
+<p>
+  This work is generously funded by <a href="https://nlnet.nl">NLnet</a> as part of their <a href="https://nlnet.nl/project/GNS/">Search and discovery fund</a>.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2019-10-ICANNPanel.html.j2 b/template/news/2019-10-ICANNPanel.html.j2
new file mode 100644
index 00000000..08885fa6
--- /dev/null
+++ b/template/news/2019-10-ICANNPanel.html.j2
@@ -0,0 +1,13 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNUnet project invited to ICANN66</h1>
+<p>
+  We are delighted to announce that ICANN has invited the GNUnet project to speak at the <a href="https://meetings.icann.org/en/montreal66">next ICANN Annual General Meeting</a>. We have been invited to join a panel discussion on <i>Emerging Internet Identifier Technologies</i> in order to share our ideas and work on the <i>GNU Name System (GNS)</i>. ICANN generously offered to cover travel and accomodation.
+</p>
+<p>
+  The meeting will take place in Montreal between 2 - 7 November. The panel will tentatively be help on November 6th.
+</p>
+<p>
+  <b>UPDATE:</b> The panel is on Tueday, November 5th 13:30 EDT with the possibility of remote participation: <a href="https://66.schedule.icann.org/meetings/1116895">Link</a>
+</p>
+{% endblock body_content %}
diff --git a/template/news/2019-11-ICANNUpdate.html.j2 b/template/news/2019-11-ICANNUpdate.html.j2
new file mode 100644
index 00000000..1edbbb8c
--- /dev/null
+++ b/template/news/2019-11-ICANNUpdate.html.j2
@@ -0,0 +1,10 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNS&#64;ICANN66</h1>
+<p>
+  The <a href="https://meetings.icann.org/en/montreal66">ICANN Annual General Meeting</a> is concluded. We were invited to join a panel discussion on <i>Emerging Internet Identifier Technologies</i> in order to share our ideas and work on the <i>GNU Name System (GNS)</i>.
+</p>
+<p>
+  You can find the presentation on GNS in <a href="{{ url_localized('video.html') }}">our video section</a>. The handshake.org project, which proposes a decentralized, blockchain-based governance of the root zone (as opposed to governance by ICANN), joined us on the panel. The full video including questions and answers can be found <a href="https://icann.zoom.us/recording/share/M8N-Duq935XheIZoBedIwmi3VqRUAe2iOPwECiTNLxKwIumekTziMw?startTime=1572978711000">here</a>.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2019-12-UpcomingTalks.html.j2 b/template/news/2019-12-UpcomingTalks.html.j2
new file mode 100644
index 00000000..b92d1cdd
--- /dev/null
+++ b/template/news/2019-12-UpcomingTalks.html.j2
@@ -0,0 +1,73 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>Upcoming GNUnet Talks</h1>
+  <p>There will be various talks in the next few months on GNUnet and related
+  projects on both the Chaos Communication Congress (36C3) as well as FOSDEM.
+  Here is an overview:
+  </p>
+  <h2>Privacy and Decentralization @ 36c3 (YBTI)</h2>
+  <p>
+    We are pleased to have 5 talks to present as part of our
+    "youbroketheinternet/wefixthenet" session, taking place on the
+    <a href="https://oio.social/">OIO (Open
+    Infrastructure Orbit)</a> stage:
+  </p>
+    <ul>
+      <li>
+        "re:claimID - Self-sovereign, Decentralised Identity Management and
+        Personal Data Sharing" by Hendrik Meyer zum Felde
+        will take place at 2019-12-27 18:30 in OIO Stage.
+        <a href="https://talks.oio.social/36c3-oio/talk/XHLTUD/">Info</a>
+      </li>
+      <li>
+        "Buying Snacks via NFC with GNU Taler" by Dominik Hofer
+        will take place at 2019-12-27 21:20 in OIO Stage
+        <a href="https://talks.oio.social/36c3-oio/talk/MMB78C/">Info</a>
+      </li>
+      <li>
+        "CloudCalypse 2: Social network with net2o" by Bernd Paysan
+        will take place at 2019-12-28 21:20 in OIO Stage
+        <a href="https://talks.oio.social/36c3-oio/talk/GUZH7V/">Info</a>
+      </li>
+      <li>
+        "Delta Chat: e-mail based messaging, the Rustocalypse and UX driven
+        approach" by holger krekel
+        will take place at 2019-12-29 17:40 in OIO Stage
+        <a href="https://talks.oio.social/36c3-oio/talk/WSLWVM/">Info</a>
+      </li>
+      <li>
+        "Cryptography of Killing Proof-of-Work" by Jeff Burdges
+        will take place at 2019-12-30 12:00 in OIO Stage
+        <a href="https://talks.oio.social/36c3-oio/talk/GGV8G3/">Info</a>
+      </li>
+    </ul>
+  <p>
+    In addition to these talks, we will be hosting a snack machine which
+    accepts <a href="https://taler.net">Taler</a> for payment.
+    The first of its kind! It will be filled
+    with various goodies, including Swiss chocolates, books, and electronics.
+    The machine will be located somewhere in the OIO assembly, and there
+    will be a station at which you may exchange Euro for digital Euro for
+    immediate use.
+    We welcome all to come try it out. :)
+  </p>
+  <h2>Decentralized Internet and Privacy devroom @FOSDEM 2020</h2>
+  <p>
+    We have 2 GNUnet-related talks at the
+    <a href="https://fosdem.org/2020/schedule/track/decentralized_internet_and_privacy/">
+    Decentralized Internet and Privacy devroom</a> at FOSDEM 2020 in February:
+  </p>
+  <ul>
+    <li>
+      GNUnet: A network protocol stack for building secure, distributed, and
+      privacy-preserving applications
+      <a href="https://fosdem.org/2020/schedule/event/dip_gnunet/">Info</a>
+    </li>
+    <li>
+      Knocking Down the Nest: secushareBOX - p2p, encrypted IoT and beyond...
+      <a href="https://fosdem.org/2020/schedule/event/dip_secusharebox/">Info</a>
+    </li>
+  </ul>
+{% endblock body_content %}
diff --git a/template/news/2020-01-0.12.2.html.j2 b/template/news/2020-01-0.12.2.html.j2
new file mode 100644
index 00000000..21375aa6
--- /dev/null
+++ b/template/news/2020-01-0.12.2.html.j2
@@ -0,0 +1,71 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNUnet 0.12.2 released</h1>
+<p>
+  We are pleased to announce the release of GNUnet 0.12.2.
+<br>
+  This is a new bugfix release.
+  In terms of usability, users should be aware that there are still
+  <b>a large number of known open issues</b> in particular with respect to ease
+  of use, but also some critical privacy issues especially for mobile users.
+  Also, the nascent network is tiny and thus unlikely to
+  provide good anonymity or extensive amounts of interesting information.
+  As a result, the 0.12.2 release is still <b>only suitable for early adopters
+  with some reasonable pain tolerance</b>.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.12.2.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.12.2.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.12.2.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.12.2.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.12.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.12.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.12.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.12.0.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.12.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.12.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.12.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.12.0.tar.gz.sig</a></li>
+</ul>
+<p>
+  The GPG key used to sign is: <tt>3D11063C10F98D14BD24D1470B0998EF86F59B6A</tt>
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional
+  early after the release. For direct access try
+  <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.12.2 (since 0.12.1)</h4>
+<ul>
+  <li>
+    <tt>GNS</tt>: Resolver clients are now able to specify a recursion depth limit.
+  </li>
+  <li>
+    <tt>TRANSPORT/TNG</tt>: The transport rewrite (aka TNG) is underway and
+    various transport components have been worked on, including TCP, UDP and UDS
+    communicators.
+  </li>
+  <li>
+    <tt>RECLAIM</tt>: Added preliminary support for third party attested
+    credentials.
+  </li>
+  <li>
+    <tt>UTIL</tt>: The cryptographic changes introduced in 0.12.0 broke ECDSA
+      ECDH and consequently other components. The offending ECDSA key normalization
+      was dropped.
+  </li>
+</ul>
+<h4>Known Issues</h4>
+<ul>
+  <li>There are known major design issues in the TRANSPORT, ATS and CORE subsystems which will need to be addressed in the future to achieve acceptable usability, performance and security.</li>
+  <li>There are known moderate implementation limitations in CADET that negatively impact performance.</li>
+  <li>There are known moderate design issues in FS that also impact usability and performance.</li>
+  <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
+  <li>The RPS subsystem remains experimental.</li>
+  <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
+</ul>
+<p>
+  In addition to this list, you may also want to consult our bug tracker at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a> which lists about 190 more specific issues.
+</p>
+<h4>Thanks</h4>
+<p>
+  This release was the work of many people. The following people contributed code and were thus easily identified:
+  Christian Grothoff, Florian Dold, Christian Ulrich, dvn, lynx and Martin Schanzenbach.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2020-01-GNSSpec2.html.j2 b/template/news/2020-01-GNSSpec2.html.j2
new file mode 100644
index 00000000..e673d35d
--- /dev/null
+++ b/template/news/2020-01-GNSSpec2.html.j2
@@ -0,0 +1,28 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNS Technical Specification Milestone 2/4</h1>
+<p>
+  We are happy to announce the completion of the second milestone for the GNS
+  Specification. The second milestone consists of documenting the GNS name
+  resolution process and record handling.<br>
+  With the release of GNUnet 0.12.x, the currently specified protocol is
+  implemented according to the specification. As before, the draft specification
+  <b>LSD001</b> can be found at:
+</p>
+<ul>
+  <li>Git: <a href="git://gnunet.org/lsd0001.git">LSD001</a></li>
+  <li><a href="https://lsd.gnunet.org/lsd0001/draft-schanzen-gns.txt">Link to TXT version</a></li>
+  <li><a href="https://lsd.gnunet.org/lsd0001/draft-schanzen-gns.html">Link to HTML version</a></li>
+</ul>
+<p>
+  As already announced on the <a href="https://lists.gnu.org/archive/html/gnunet-developers/2020-01/msg00000.html">mailing list</a>,
+  the Go implementation of GNS is also proceeding as planned and implements the
+  specification.
+</p>
+<p>
+  The next and third milestone will cover namespace revocation.
+</p>
+<p>
+  This work is generously funded by <a href="https://nlnet.nl">NLnet</a> as part of their <a href="https://nlnet.nl/project/GNS/">Search and discovery fund</a>.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2020-05-GHM_Jun_2020.html.j2 b/template/news/2020-05-GHM_Jun_2020.html.j2
new file mode 100644
index 00000000..f270d87d
--- /dev/null
+++ b/template/news/2020-05-GHM_Jun_2020.html.j2
@@ -0,0 +1,8 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>Online GNUnet Hacker Meeting in June 2020</h1>
+  <p>
+    We are happy to announce that we will have a GNUnet
+    Hacker Meeting from 17-21 of June 2020 taking place online. For more information see <a href="https://md.hasi.it/s/gnunet">here</a>.
+  </p>
+{% endblock body_content %}
diff --git a/template/news/2020-06-GNSSpec3.html.j2 b/template/news/2020-06-GNSSpec3.html.j2
new file mode 100644
index 00000000..2e69ccb9
--- /dev/null
+++ b/template/news/2020-06-GNSSpec3.html.j2
@@ -0,0 +1,25 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNS Technical Specification Milestone 3/4</h1>
+<p>
+  We are happy to announce the completion of the third milestone for the GNS
+  Specification. The third milestone consists of documenting the GNS zone
+  revocation process. As part of this, we have reworked the proof-of-work
+  algorithms in GNUnet also used for GNS revocations.<br>
+  The (protocol breaking) changes will be released as part of GNUnet 0.13.0.
+  The specification document <b>LSD001</b> can be found at:
+</p>
+<ul>
+  <li>Git: <a href="git://gnunet.org/lsd0001.git">LSD001</a></li>
+  <li><a href="https://lsd.gnunet.org/lsd0001/draft-schanzen-gns.txt">Link to TXT version</a></li>
+  <li><a href="https://lsd.gnunet.org/lsd0001/draft-schanzen-gns.html">Link to HTML version</a></li>
+</ul>
+<p>
+  In preparation for the fourth and last milestone, we have started the
+  <a href="https://mailarchive.ietf.org/arch/msg/secdispatch/Kj8zXoQssiFLp8bM5l5n1OtXt7s/">IETF process to find a working group</a> and expect to present our
+  work initially at <a href="https://ietf.org/how/meetings/108/">IETF 108</a>.
+</p>
+<p>
+  This work is generously funded by <a href="https://nlnet.nl">NLnet</a> as part of their <a href="https://nlnet.nl/project/GNS/">Search and discovery fund</a>.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2020-07-0.13.0.html.j2 b/template/news/2020-07-0.13.0.html.j2
new file mode 100644
index 00000000..ef8c0d89
--- /dev/null
+++ b/template/news/2020-07-0.13.0.html.j2
@@ -0,0 +1,103 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNUnet 0.13.0 released</h1>
+<p>
+  We are pleased to announce the release of GNUnet 0.13.0.
+<br>
+  This is a new major release. It breaks protocol compatibility with the 0.12.x versions.
+  Please be aware that Git master is thus henceforth <b>INCOMPATIBLE</b> with
+  the 0.12.x GNUnet network, and interactions between old and new peers
+  will result in signature verification failures.  0.12.x peers will <b>NOT</b>
+  be able to communicate with Git master or 0.13.x peers.<br/>
+  In terms of usability, users should be aware that there are still
+  <b>a large number of known open issues</b> in particular with respect to ease
+  of use, but also some critical privacy issues especially for mobile users.
+  Also, the nascent network is tiny and thus unlikely to
+  provide good anonymity or extensive amounts of interesting information.
+  As a result, the 0.13.0 release is still <b>only suitable for early adopters
+  with some reasonable pain tolerance</b>.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.13.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.13.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.13.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.13.0.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.13.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.13.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.13.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.13.0.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.13.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.13.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.13.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.13.0.tar.gz.sig</a></li>
+</ul>
+<p>
+  The GPG key used to sign is: <tt>3D11063C10F98D14BD24D1470B0998EF86F59B6A</tt>
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional
+  early after the release. For direct access try
+  <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.13.0 (since 0.12.2)</h4>
+<ul>
+  <li><tt>GNS</tt>:
+    <ul>
+      <li>Aligned with specification <a href="https://lsd.gnunet.org/lsd0001/">LSD001</a>.
+      <li>NSS plugin "block" fixed. <a href="https://bugs.gnunet.org/view.php?id=5782">#5782</a></li>
+      <li>Broken set NICK API removed.<a href="https://bugs.gnunet.org/view.php?id=6092">#6092</a></li>
+      <li>New record flags: SUPPLEMENTAL. Records which are not explicitly
+       configured/published under a specific label but which are still
+       informational are returned by the resolver and flagged accordingly. <a href="https://bugs.gnunet.org/view.php?id=6103">#6103</a></li>
+      <li><tt>gnunet-namestore</tt> now complains when adding TLSA or SRV records outside of a BOX</li>
+    </ul>
+  </li>
+  <li>
+    <tt>CADET</tt>: Fixed tunnel establishment as well as an outstanding bug regarding tunnel destruction. <a href="https://bugs.gnunet.org/view.php?id=5822">#5822</a>
+  </li>
+  <li><tt>GNS/REVOCATION</tt>: Revocation proof of work has function changed to
+  argon2 and modified to reduce variance.</li>
+  <li><tt>RECLAIM</tt>: Increased ticket length to 256 bit. <a href="https://bugs.gnunet.org/view.php?id=6047">#6047</a></li>
+  <li><tt>TRANSPORT</tt>: UDP plugin moved to experimental as it is known to be unstable.</li>
+  <li><tt>UTIL</tt>:
+    <ul>
+      <li>Serialization / file format of ECDSA private keys harmonized with
+      other libraries. Old private keys will no longer work! <a href="https://bugs.gnunet.org/view.php?id=6070">#6070</a></li>
+      <li>Now using <a href="https://doc.libsodium.org/">libsodium</a> for EC
+      cryptography.</li>
+      <li>Builds against cURL which is not linked against gnutls are now possible but still not recommended.
+      Configure will warn that this will impede the GNS functionality. This change will make hostlist discovery
+      work more reliable for some distributions.</li>
+      <li><tt>GNUNET_free_non_null</tt> removed. <tt>GNUNET_free</tt> changed to not assert that the pointer is not NULL.
+      For reference see the <a href="https://taler.net/papers/codeblau-report-2020-q2.pdf">Taler security audit</a>.</li>
+      <li>AGPL request handlers added GNUnet and extension templates.</li>
+    </ul>
+  </li>
+  <li><b>(NEW) </b><tt>GANA Registry</tt>: We have established a registry to be used for names and numbers in GNUnet.
+  This includes constants for protocols including GNS record types and GNUnet peer-to-peer messages. See <a href="https://gana.gnunet.org">GANA</a>.</li>
+  <li><b>(NEW) </b><tt>Living Standards</tt>: LSD subdomain and LSD0001 website: <a href="https://lsd.gnunet.org/lsd0001">LSD0001</a></li>
+  <li><b>(NEW) </b><tt>Continuous integration</tt>: <a href="https://buildbot.gnunet.org">Buildbot</a> is back.</li>
+  <li><tt>Buildsystem</tt>: A significant number of build system changes:
+    <ul>
+      <li>libmicrohttpd and libjansson are now required dependencies.</li>
+      <li>New dependency: <a href="https://doc.libsodium.org/">libsodium</a>.</li>
+      <li>Fixed an issue with libidn(2) detection.</tt>
+    </ul>
+  </li>
+</ul>
+A detailed list of changes can be found in the <a href="https://git.gnunet.org/gnunet.git/tree/ChangeLog">ChangeLog</a> and
+the <a href="https://bugs.gnunet.org/roadmap_page.php?version_id=338">0.13.0 bugtracker</a>.
+<h4>Known Issues</h4>
+<ul>
+  <li>There are known major design issues in the TRANSPORT, ATS and CORE subsystems which will need to be addressed in the future to achieve acceptable usability, performance and security.</li>
+  <li>There are known moderate implementation limitations in CADET that negatively impact performance.</li>
+  <li>There are known moderate design issues in FS that also impact usability and performance.</li>
+  <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
+  <li>The RPS subsystem remains experimental.</li>
+  <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
+</ul>
+<p>
+  In addition to this list, you may also want to consult our bug tracker at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a> which lists about 190 more specific issues.
+</p>
+<h4>Thanks</h4>
+<p>
+  This release was the work of many people. The following people contributed code and were thus easily identified:
+  Christian Grothoff, Florian Dold, Jonathan Buchanan, t3sserakt, nikita and Martin Schanzenbach.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2020-07-0.13.1.html.j2 b/template/news/2020-07-0.13.1.html.j2
new file mode 100644
index 00000000..b7670242
--- /dev/null
+++ b/template/news/2020-07-0.13.1.html.j2
@@ -0,0 +1,29 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNUnet 0.13.1 released</h1>
+<p>
+  This is a bugfix release for gnunet and gnunet-gtk specifically.
+  <br>
+  For gnunet, no changes to the source have been made. However,
+  the default configuration had to be modified to support the changes
+  made in 0.13.0.
+  <br>
+  For gnunet-gtk, this fixes a more serious issue where the
+  0.13.0 tarball failed to build.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.13.1.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.13.1.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.13.1.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.13.1.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.13.1.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.13.1.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.13.1.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.13.1.tar.gz.sig</a></li>
+</ul>
+<p>
+  The GPG key used to sign is: <tt>3D11063C10F98D14BD24D1470B0998EF86F59B6A</tt>
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional
+  early after the release. For direct access try
+  <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+{% endblock body_content %}
diff --git a/template/news/2020-08-0.13.2.html.j2 b/template/news/2020-08-0.13.2.html.j2
new file mode 100644
index 00000000..3dfa7e61
--- /dev/null
+++ b/template/news/2020-08-0.13.2.html.j2
@@ -0,0 +1,58 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+<h1>GNUnet 0.13.2 released</h1>
+<p>
+  This is a bugfix release for gnunet 0.13.1.<br/>
+  It fixes some build issues and contains changes to the REST API
+  implmementation (no change in the API itself) as well as OpenID Connect related
+  fixes to re:claimID.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.13.2.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.13.2.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.13.2.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.13.2.tar.gz.sig</a></li>
+</ul>
+<p>
+  The GPG key used to sign is: <tt>3D11063C10F98D14BD24D1470B0998EF86F59B6A</tt>
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional
+  early after the release. For direct access try
+  <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.13.2 (since 0.13.1)</h4>
+<ul>
+  <li><tt>REST</tt>:
+    <ul>
+      <li>Plugins may now handle any namespace. <a href="https://bugs.gnunet.org/view.php?id=6462">#6462</a></li>
+      <li>Fixed incomplete/missing cleanup and teardown of REST plugins.</li>
+    </ul>
+  </li>
+  <li><tt>RECLAIM</tt>:
+    <ul>
+      <li>Support for <tt>/.well-known/openid-configuration</tt>. <a href="https://bugs.gnunet.org/view.php?id=6463">#6463</a></li>
+      <li>Support for standard scope values (<tt>profile, address, email, phone</tt>) and corresponding mapping to standard claim values</li>
+      <li>Correct processing of <tt>claims</tt> parameter for individual claim requests.</li>
+      <li>Support for <tt>POST</tt> token request.</li>
+      <li>Support for public clients (Token request without client secrets).</li>
+      <li>Fixed urlencoding of parameters on redirect</li>
+    </ul>
+  </li>
+  <li><tt>UTIL</tt>: New string API for percent-encode/decode.</li>
+  <li><tt>MYSQL</tt>: Fix version detection and build against mysql-8 and later. <a href="https://bugs.gnunet.org/view.php?id=6465">#6465</a></li>
+  <li><tt>POSTGRESQL</tt>: Ensure postgresql fails hard if there is an error in the SQL. <a href="https://bugs.gnunet.org/view.php?id=6437">#6437</a></li>
+  <li><tt>Extensions</tt>:
+    <ul>
+      <li>Load GNSRECORD plugins within GNUnet's context.</li>
+      <li>Add convenience function to return GNUnet's default configuration.</li>
+    </ul>
+  </li>
+</ul>
+<h4>Thanks</h4>
+<p>
+  This release was the work of many people. The following people contributed code and were thus easily identified:
+  Christian Grothoff, Florian Dold, Alessio Vanni, t3sserakt, Martin Schanzenbach.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2020-09-0.13.3.html.j2 b/template/news/2020-09-0.13.3.html.j2
new file mode 100644
index 00000000..dc9440c3
--- /dev/null
+++ b/template/news/2020-09-0.13.3.html.j2
@@ -0,0 +1,51 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+<h1>GNUnet 0.13.3 released</h1>
+<p>
+  Continuing to "release early / release often", we present
+  GNUnet 0.13.3. This is a bugfix release for gnunet 0.13.2.<br/>
+  It fixes some build issues and contains major changes to
+  the re:claimID API.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.13.3.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.13.3.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.13.3.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.13.3.tar.gz.sig</a></li>
+</ul>
+<p>
+  The GPG key used to sign is: <tt>3D11063C10F98D14BD24D1470B0998EF86F59B6A</tt>
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional
+  early after the release. For direct access try
+  <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.13.3 (since 0.13.2)</h4>
+<ul>
+  <li><tt>REST</tt>:
+    <ul>
+      <li>re:claimID attestation API change reflected in endpoint naming.</li>
+      <li>Fix regression in <tt>NAMESTORE</tt> REST API endpoint processing.</li>
+    </ul>
+  </li>
+  <li><tt>RECLAIM</tt>:
+      "Attestations" renamed to "Credentials". Credentials are now converted to "Presentations" when a ticket is issued in preparation
+      for <a href="https://www.w3.org/TR/vc-data-model/">DID-style VCs</a> and Privacy-ABCs.
+  </li>
+  <li><tt>UTIL</tt>: Fix <tt>gnunet-qr</tt> device parameter.</li>
+  <li><tt>SET</tt>: Separated into set intersection (SETI) and set union subsystems (SETU).</a></li>
+  <li><tt>BUILD</tt>:
+    <ul>
+      <li>Fix build on OpenBSD.</li>
+      <li>Correctly check for required libsodium version. <a href="https://bugs.gnunet.org/view.php?id=6506">#6506</a></li>
+    </ul>
+  </li>
+</ul>
+<h4>Thanks</h4>
+<p>
+  This release was the work of many people. The following people contributed code and were thus easily identified:
+  Christian Grothoff, Jonathan Buchanan, Johannes Späth and Martin Schanzenbach.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2020-11-0.14.0.html.j2 b/template/news/2020-11-0.14.0.html.j2
new file mode 100644
index 00000000..853b4548
--- /dev/null
+++ b/template/news/2020-11-0.14.0.html.j2
@@ -0,0 +1,81 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNUnet 0.14.0 released</h1>
+<p>
+  We are pleased to announce the release of GNUnet 0.14.0.
+<br>
+  This is a new major release. It breaks protocol compatibility with the 0.13.x versions.
+  Please be aware that Git master is thus henceforth <b>INCOMPATIBLE</b> with
+  the 0.13.x GNUnet network, and interactions between old and new peers
+  will result in issues.  0.13.x peers will be able to communicate with Git
+  master or 0.13.x peers, but some services - in particular GNS - will not be compatible.<br/>
+  In terms of usability, users should be aware that there are still
+  <b>a large number of known open issues</b> in particular with respect to ease
+  of use, but also some critical privacy issues especially for mobile users.
+  Also, the nascent network is tiny and thus unlikely to
+  provide good anonymity or extensive amounts of interesting information.
+  As a result, the 0.14.0 release is still <b>only suitable for early adopters
+  with some reasonable pain tolerance</b>.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.14.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.14.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.14.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.14.0.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.14.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.14.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.14.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-gtk-0.14.0.tar.gz.sig</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.14.0.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.14.0.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.14.0.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-fuse-0.14.0.tar.gz.sig</a></li>
+</ul>
+<p>
+  The GPG key used to sign is: <a href="https://gnunet.org/~schanzen/3D11063C10F98D14BD24D1470B0998EF86F59B6A">3D11063C10F98D14BD24D1470B0998EF86F59B6A</a>
+</p>
+<p>
+  Note that due to mirror synchronization, not all links might be functional
+  early after the release. For direct access try
+  <a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.14.0 (since 0.13.3)</h4>
+<ul>
+  <li><tt>GNS</tt>:
+    <ul>
+      <li>Aligned with specification <a href="https://lsd.gnunet.org/lsd0001/">LSD001</a>.
+      <li>Crypto agility: The GNS protocol now supports other zone types besides ECDSA-based PKEYs.
+      However, the alternative EdDSA-based EDKEY crypto is not yet implemented. <a href="https://bugs.gnunet.org/view.php?id=6485">#6485</a></li>
+      <li>PKEY zones: ECDSA zone record sets are now encrypted using AES-CTR. <a href="https://bugs.gnunet.org/view.php?id=6487">#6487</a></li>
+    </ul>
+  </li>
+  <li>
+    <tt>IDENTITY</tt>: Identities can now be created either as ECDSA (default) or EdDSA key pairs.</li>
+  </li>
+  <li>
+    <tt>POSTGRESQL</tt>: Allow NULL value returns and fix test cases. <a href="https://bugs.gnunet.org/view.php?id=6524">#6524</a>
+  </li>
+  <li><tt>UTIL</tt>:
+      String time conversion functions no longer localized to preserve reversibility. <a href="https://bugs.gnunet.org/view.php?id=6615">#6615</a>
+  </li>
+  <li><tt>Buildsystem</tt>: README updates to clarify runtime/compile/optional dependencies</li>
+  <li><b>(NEW)</b> <tt>MESSENGER</tt>: New messenger component (experimental)</li>
+</ul>
+<p>
+  A detailed list of changes can be found in the <a href="https://git.gnunet.org/gnunet.git/tree/ChangeLog">ChangeLog</a> and
+  the <a href="https://bugs.gnunet.org/changelog_page.php?project_id=13">0.14.0 bugtracker</a>.
+</p>
+<h4>Known Issues</h4>
+<ul>
+  <li>There are known major design issues in the TRANSPORT, ATS and CORE subsystems which will need to be addressed in the future to achieve acceptable usability, performance and security.</li>
+  <li>There are known moderate implementation limitations in CADET that negatively impact performance.</li>
+  <li>There are known moderate design issues in FS that also impact usability and performance.</li>
+  <li>There are minor implementation limitations in SET that create unnecessary attack surface for availability.</li>
+  <li>The RPS subsystem remains experimental.</li>
+  <li>Some high-level tests in the test-suite fail non-deterministically due to the low-level TRANSPORT issues.</li>
+</ul>
+<p>
+  In addition to this list, you may also want to consult our bug tracker at <a href="https://bugs.gnunet.org/">bugs.gnunet.org</a> which lists about 190 more specific issues.
+</p>
+<h4>Thanks</h4>
+<p>
+  This release was the work of many people. The following people contributed code and were thus easily identified:
+  Christian Grothoff, Daniel Golle, t3sserakt, TheJackiMonster and Martin Schanzenbach.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2020-11-GNSSpec4.html.j2 b/template/news/2020-11-GNSSpec4.html.j2
new file mode 100644
index 00000000..13e0f28d
--- /dev/null
+++ b/template/news/2020-11-GNSSpec4.html.j2
@@ -0,0 +1,45 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>GNS Technical Specification Milestone 4/4 and Packaging 1+2</h1>
+<p>
+  We are happy to announce the completion of the fourth and last milestone for the GNS
+  Specification. The fourth milestone consists of involving a broader community
+  for feedback and improvements:
+<p>
+<ul>
+  <li><a href="https://news.ycombinator.com/item?id=23766947">Hacker News</a></li>
+  <li><a href="https://datatracker.ietf.org/meeting/108/session/secdispatch">IETF 108 secdispatch</a>
+  (see also associated discussions on the mailinglist)</li>
+  <li><a href="https://centr.org/news/news/alternative-dns.html">Reporting on IETF secdispatch</a></li>
+  <li><a href="https://mailarchive.ietf.org/arch/msg/din/jkbYgEsyuZCknyYQxN-LxDtWpsY/">IRTF DINRG</a></li>
+  <li><a href="https://lists.gnu.org/archive/html/gnunet-developers/2020-07/msg00043.html">Mailing list</a></li>
+</ul>
+<p>
+  Based on this and private feedback received, we updated the draft and
+  the implementation. Most notably, GNS now supports alternative cryptographic
+  schemes for zone keys ("crypto agility") which allows alternative zone types.
+  The (protocol breaking) changes will be released as part of GNUnet 0.14.0.
+  The specification document <b>LSD001</b> can be found at:
+</p>
+<ul>
+  <li>Git: <a href="git://gnunet.org/lsd0001.git">LSD001</a></li>
+  <li><a href="https://lsd.gnunet.org/lsd0001/draft-schanzen-gns.txt">Link to TXT version</a></li>
+  <li><a href="https://lsd.gnunet.org/lsd0001/draft-schanzen-gns.html">Link to HTML version</a></li>
+  <li><a href="https://datatracker.ietf.org/doc/draft-schanzen-gns/">Link to IETF Datatracker (updated less frequently)</a></li>
+</ul>
+<p>
+  Further, work on packaging has been done on Alpine (Packaging 1) and Debian (Packaging 2) packages.
+  The packaging for Alpine is complete, the Debian package is in progress as
+  review and final integration is out of our hands. For reference see also:
+</p>
+<ul>
+  <li><a href="https://pkgs.alpinelinux.org/packages?name=gnunet&branch=edge">Alpine package</a></li>
+  <li><a href="https://salsa.debian.org/debian/gnunet/-/merge_requests/3">Debian package</a></li>
+</ul>
+<p>
+  We will continue to engage with IETF/IRTF as much as possible (online or in-person)
+  including future presentations and discussions at IETF/IRTF.
+  There is still a packaging task open for Fedora (3) which is still work in progress.
+  This work was (and other aspects still are) generously funded by <a href="https://nlnet.nl">NLnet</a> as part of their <a href="https://nlnet.nl/project/GNS/">Search and discovery fund</a>.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2021-03-0.14.1.html.j2 b/template/news/2021-03-0.14.1.html.j2
new file mode 100644
index 00000000..0249b984
--- /dev/null
+++ b/template/news/2021-03-0.14.1.html.j2
@@ -0,0 +1,48 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+<h1>GNUnet 0.14.1</h1>
+<p>
+Continuing to "release early / release often", we present
+GNUnet 0.14.1. This is a bugfix release for gnunet 0.14.0.
+</p>
+<h4>Download links</h4>
+<ul>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.14.1.tar.gz">http://ftpmirror.gnu.org/gnunet/gnunet-0.14.1.tar.gz</a></li>
+  <li><a href="http://ftpmirror.gnu.org/gnunet/gnunet-0.14.1.tar.gz.sig">http://ftpmirror.gnu.org/gnunet/gnunet-0.14.1.tar.gz.sig</a></li>
+</ul>
+<p>
+The GPG key used to sign is: <a href="https://gnunet.org/~schanzen/3D11063C10F98D14BD24D1470B0998EF86F59B6A">3D11063C10F98D14BD24D1470B0998EF86F59B6A</a>
+</p>
+<p>
+Note that due to mirror synchronization, not all links may be functional
+early after the release. For direct access try
+<a href="http://ftp.gnu.org/gnu/gnunet/">http://ftp.gnu.org/gnu/gnunet/</a>
+</p>
+<h4>Noteworthy changes in 0.14.1 (since 0.14.0)</h4>
+<ul>
+  <li><tt>TNG</tt>: Various improvements to communicators. <a href="https://bugs.gnunet.org/view.php?id=6361">#6361</a>,<a href="https://bugs.gnunet.org/view.php?id=5550">#5550</a>
+  </li>
+  <li><tt>GNS</tt>: Use autogenerated records header file from GANA.</li>
+  <li><tt>FS</tt>: Improve modularity of FS structs. <a href="https://bugs.gnunet.org/view.php?id=6743">#6743</a></li>
+  <li><tt>SETU</tt>: Various improvements as part of the ongoing work on <a href="https://lsd.gnunet.org/lsd0003">LSD0003</a>.</li>
+  <li><tt>IDENTITY</tt>: Fix wrong key construction for anonymous ECDSA identity.</li>
+  <li><tt>RPS</tt>: Code cleanup mostly addressing warnings.</li>
+  <li><tt>UTIL</tt>:
+    <ul>
+      <li>Added a Base32 en/decoded CLI <tt>gnunet-base32</tt>.</li>
+      <li>Use timeflakes as UUIDs. <a href="https://bugs.gnunet.org/view.php?id=6716">#6716</a></li>
+    </ul>
+  </li>
+  <li><tt>Buildsystem</tt>: Fix libunistring detection. <a href="https://bugs.gnunet.org/view.php?id=6485">#6485</a></li>
+</ul>
+<p>
+A detailed list of changes can be found in the <a href="https://git.gnunet.org/gnunet.git/tree/ChangeLog">ChangeLog</a> and
+the <a href="https://bugs.gnunet.org/changelog_page.php?project_id=13">0.14.1 bugtracker</a>.
+</p>
+<h4>Thanks</h4>
+<p>
+This release was the work of many people. The following people contributed code and were thus easily identified:
+Christian Grothoff, Florian Dold, t3sserakt, TheJackiMonster, Elias Summermatter, Julius Bünger and Thien-Thi Nguyen.
+</p>
+{% endblock body_content %}
diff --git a/template/news/2021-03-gsoc-update.html.j2 b/template/news/2021-03-gsoc-update.html.j2
new file mode 100644
index 00000000..d638549a
--- /dev/null
+++ b/template/news/2021-03-gsoc-update.html.j2
@@ -0,0 +1,13 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>No GSoC projects in 2021</h1>
+<p>
+  For 2021, <a href="https://lists.gnu.org/archive/html/summer-of-code/2021-03/msg00000.html">GNU has not been selected as a GSoC organization</a>.
+  This also means that <a href="{{ url_localized('gsoc.html')}}">GNUnet GSoC
+  projects</a> will not be offered through the GSoC programme.
+  Thanks to all of those interested in our proposed projects and their efforts
+  in preparing proposals, including preliminary discussions with us.
+  If you are still interested in tackling any of the proposed open issues, you
+  are very welcome to do so.
+<p>
+{% endblock body_content %}
diff --git a/template/news/2021-05-DISSENS.html.j2 b/template/news/2021-05-DISSENS.html.j2
new file mode 100644
index 00000000..d67f33a5
--- /dev/null
+++ b/template/news/2021-05-DISSENS.html.j2
@@ -0,0 +1,67 @@
+{% extends "common/news.j2" %}
+{% block body_content %}
+  <h1>DISSENS: Decentralized Identities for Self-sovereign End-users (NGI TRUST)</h1>
+<p>
+  Since mid 2020, a consortium between <a class="link" href="https://taler.net">Taler Systems S.A.</a>,
+the <a class="link" href="https://bfh.ch">Bern University of Applied Sciences</a> and <a class="link" href="https://aisec.fraunhofer.de">Fraunhofer AISEC</a> has been working
+  on bringing privacy-friendly payments using GNU Taler and self-sovereign
+  identity using GNUnet's <a class="link" href="https://reclaim.gnunet.org">re:claimID</a>
+  together in an e-commerce framework.
+</p>
+<p>
+<img style="width: 100%; border: 1px solid #333" src="{{ url_static('dissens-overview.png')}}"/>
+</p>
+<h2>Content</h2>
+<p>
+  Registrations of accounts prior to receiving services online is the standard process for commercial offerings on the Internet which depend on two corner stones of the Web: Payment processing and digital identities. The use of third-party identity provider services (IdPs) is practical as it delegates the task of verifying and storing personal information. The use of payment processors is convenient for the customer as it provides one-click payments. However, the quasi-oligopoly of services providers in those areas include Google and Facebook for identities and PayPal or Stripe for payment processing. Those corporations are not only based in privacy-unfriendly jurisdictions, but also exploit private data for profit.
+</p>
+<p>
+DISSENS makes the case that what is urgently needed are fundamentally different, user-centric and privacy-friendly alternatives to the above.
+Self-sovereign identity (SSI) management is the way to replace IdPs with a user-centric, decentralized mechanism where data and access control is fully under the control of the data subject.
+In combination with a privacy-friendly payment system, DISSENS aims to achieve the same one-click user experience that is currently achieved by privacy-invasive account-based Web shops, but without the users having to setup accounts.
+</p>
+<p>
+To achieve this, DISSENS integrates re:claimID with the GNU Taler payment system in a pilot in order to demonstrate the practical feasibility and benefits of privacy enhancing technologies for users and commercial service providers.
+DISSENS also implements a reference scenario which includes credentials issued by the partners Fraunhofer AISEC and BFH for employees and students, respectively. Users are able to access and use a pilot service developed by Taler Systems S.A. while being able to claim specific discounts for students and researchers.
+</p>
+<p>
+This approach offers significant benefits over existing solutions built using other SSI systems such as <a class="link" href="https://www.sovrin.org">Sovrin</a> or <a class="link" href="https://www.serto.id">serto</a> (formerly uPort):
+</p>
+<b>No gatekeepers; No vendor lock-in:</b>
+<p>
+The approach is completely open to issuers and does not impose any registration restrictions (such as registration fees) in order to define domain specific credentials. Further, the system does not impose a consortium-based governance model — which tend to eventually be driven by commercial interests and not consumer interests. The design enables all participants in the ecosystem to participate without prior onboarding while at the same time being offered full transparency and control regarding their personal data and processes involved.
+</p>
+<b>Support for non-interactive business processes:</b>
+<p>
+At the same time, unlike the SSI systems cited above, re:claimID offers a way to access user information without online interaction with the user. Offline access of shared identity data is a crucial requirement in almost any business process as such processes often occur after direct interaction with the user. For example, customer information such as billing addresses are required in — possibly recurring — back office billing processes which occur well after interaction with a customer.
+</p>
+<b>Scalability and sustainability:</b>
+<p>
+Finally, both re:claimID as the SSI system as well as Taler do not suffer from the usual predicament Blockchain-based systems find themselves in: Both systems do not require a decentralized, public ledger. This eliminates the need for consensus mechanisms, which do not scale and are ecologically unsustainable. In fact, DISSENS employs decentralization only where it provides the most value and use more efficient technology stacks where needed: re:claimID builds on top of the <a class="link" href="{{ url_localized('gns.html') }}">GNU Name System</a>, which makes use of a DHT, an efficient (O(log n)) peer-to-peer data structure. For payments, GNU Taler uses centralized infrastructure operated by audited and regulated exchange providers and facilitates account-less end-to-end interactions between customers and services where all parties have O(1) transaction costs.
+</p>
+<p>
+The result of DISSENS will provide businesses and credential issuers with ready-to-use and standards-compliant templates to build privacy-friendly services in the Web.
+The aim of the DISSENS project was to design a technology stack which combines privacy-friendly online payments with self-sovereign personal data management. The result enables users to be in complete control over their digital identity and personal information while at the same time being able to selectively share information necessary to use commercial services. The pilot demonstrates a sustainable, user-centric, standard-compliant and accessible use case for public service employees and students in the domain of commercial food delivery.
+It serves as an easy-to-adapt template for the integration of other scenarios and use cases.
+</p>
+<h2>Future work</h2>
+<p>
+GNUnet is working on the underlying components mature to the point that Taler+re:claimID can be recommended to operators to enable for account-less shopping with or without verified credentials. This will also require the continuation of our
+work on the low-level transport rewrite as it is a core component of GNS which
+in turn is what makes re:claimID spin.
+</p>
+<h2>Links</h2>
+<ul>
+  <li>Mid-project <a class="link" href="https://gnunet.org/~schanzen/2021-01-18-reclaimID-Taler-Shopping.webm">demonstration video</a> (~7 MB).</li>
+  <li><a class="link" href="https://git.gnunet.org/bibliography.git/plain/docs/dissens2021.pdf">The paper</a> (also accepted for publication without appendix at the <a class="link" href="https://oid2021.compute.dtu.dk/">Open Identity Summit 2021</a>)</li>
+  <li><a class="link" href="https://wordpress.org/plugins/gnu-taler-payment-for-woocommerce/">Taler WooCommerce plugin</a> (wordpress.org)</li>
+  <li>The privacy credential library <a class="link" href="https://github.com/Fraunhofer-AISEC/libpabc">libpabc</a> (github.com).</li>
+  <li><a class="link" href="https://git.taler.net/woocommerce-taler.git">Setup scripts and installation documentation for a Taler + re:claimID + WooCommerce service</a> (taler.net).</li>
+  <li><a class="link" href="https://git.gnunet.org/gnunet-presentations.git/plain/2021dissens/reclaim.pdf">Slide deck</a>.</li>
+</ul>
+<p>
+</p>
+<p>
+  This work is generously funded by <a class="link" href="https://www.ngi.eu">the EC's Next Generation Internet (NGI) initiative</a> as part of their <a class="link" href="https://www.ngi.eu/ngi-projects/ngi-trust/">NGI TRUST</a> programme.
+</p>
+{% endblock body_content %}
diff --git a/template/news/index.html.j2 b/template/news/index.html.j2
new file mode 100644
index 00000000..abd20092
--- /dev/null
+++ b/template/news/index.html.j2
@@ -0,0 +1,57 @@
+{% extends "common/base.j2" %}
+{% block body_content %}
+  <div class="container-fluid">
+    <div class="container">
+      <article>
+        <div class="row">
+          <div class="container text-center">
+            <h1>{{ _("News") }}<a name="news"></a></h1>
+            <section>
+              <p>
+                {% trans %}
+                News posts about changes related to
+                GNUnet such as releases and events
+                {% endtrans %}
+                &#8211;
+                <a href="{{ url_localized('rss.xml') }}">{{ _("subscribe to our RSS feed") }}</a>
+              </p>
+            </section>
+          </div>
+        </div>
+        <div class="row">
+          {% for year, yitem in newsdata|selectattr('date.year', 'gt', 2019)|groupby('date.year')|reverse %}
+          <b>{{ year }}</b>
+          <ul class="timeline">
+          {% for item in yitem %}
+          <li>
+              <section class="item-preview">
+               <header>
+                  <h3>{{ item['title']|e }}</h3>
+                  <p class="item-date">
+                    {{ item['date'] }}
+                  </p>
+                </header>
+                <p class="item-abstract">
+                  {{ get_abstract(item['page'], 500) }} <br/>
+                  [<a href="{{ url_localized(item['page']) }}" title="{{ item['date']}}">{{ _("read more") }}</a>]
+                </p>
+              </section>
+            </li>
+          {% endfor %}
+          </ul>
+          {% endfor %}
+        </div>
+        <h2>
+          {% trans %}
+          News archives:
+          {% endtrans %}
+        </h2>
+        <ul>
+        {% for year, yitem in newsdata|selectattr('date.year', 'lt', 2020)|groupby('date.year')|reverse %}
+          <li><a href="{{ 'oldnews-' + year|string + '.html' }}">{{ year }} ({{yitem|length}})</a></li>
+        {% endfor %}
+        </ul>
+      </article>
+    </div>
+  </div>
+{% endblock body_content %}
diff --git a/template/news/oldnews-2011.html.j2 b/template/news/oldnews-2011.html.j2
new file mode 100644
index 00000000..39e76a48
--- /dev/null
+++ b/template/news/oldnews-2011.html.j2
@@ -0,0 +1,5 @@
+{% extends "common/base.j2" %}
+{% from "common/old-news.j2.inc" import oldnews with context %}
+{% block body_content %}
+{{ oldnews(2011) }}
+{% endblock body_content %}
diff --git a/template/news/oldnews-2013.html.j2 b/template/news/oldnews-2013.html.j2
new file mode 100644
index 00000000..d725f006
--- /dev/null
+++ b/template/news/oldnews-2013.html.j2
@@ -0,0 +1,5 @@
+{% extends "common/base.j2" %}
+{% from "common/old-news.j2.inc" import oldnews with context %}
+{% block body_content %}
+{{ oldnews(2013) }}
+{% endblock body_content %}
diff --git a/template/news/oldnews-2018.html.j2 b/template/news/oldnews-2018.html.j2
new file mode 100644
index 00000000..3056892c
--- /dev/null
+++ b/template/news/oldnews-2018.html.j2
@@ -0,0 +1,5 @@
+{% extends "common/base.j2" %}
+{% from "common/old-news.j2.inc" import oldnews with context %}
+{% block body_content %}
+{{ oldnews(2018) }}
+{% endblock body_content %}
diff --git a/template/news/oldnews-2019.html.j2 b/template/news/oldnews-2019.html.j2
new file mode 100644
index 00000000..23691b6c
--- /dev/null
+++ b/template/news/oldnews-2019.html.j2
@@ -0,0 +1,5 @@
+{% extends "common/base.j2" %}
+{% from "common/old-news.j2.inc" import oldnews with context %}
+{% block body_content %}
+{{ oldnews(2019) }}
+{% endblock body_content %}
diff --git a/template/reclaim/faq.html.j2 b/template/reclaim/faq.html.j2
new file mode 100644
index 00000000..b49b8f6c
--- /dev/null
+++ b/template/reclaim/faq.html.j2
@@ -0,0 +1,26 @@
+{% extends "common/base.j2" %}
+{% block body_content %}
+<div class="m-3">
+  <a class="mt-2 mb-2" href="{{ url_localized('reclaim/index.html') }}">reclaimID</a> / FAQ
+</div>
+<h2 class="text-center">{{ _("Frequently asked questions") }}</h2>
+<br/>
+<div class="container">
+  <ul class="fa-ul">
+    <li class="mt-4"><i class="fa-li fas fa-question-circle"></i> <b>How is re:claimID different from</b> <i>&lt;insert other identity provider service here&gt; ?</i></li>
+    <li><i class="fa-li fas fa-comment"></i> Unlike most other identity provider services, re:claimID is not operated by a single service provider or even a federated consortium of service providers. Instead, it is a fully decentralised service operated implicitly by its users. Consequently, large-scale data monetisation, mass-surveillance and other (ab)use of personal data is inherently mitigated.</li>
+    <li class="mt-4"><i class="fa-li fas fa-question-circle"></i> <b>How much does re:claimID cost?</b></li>
+    <li><i class="fa-li fas fa-comment"></i> re:claimID is Free Software. We argue that in order for an identity system to be a credible solution for self-sovereign citizens to exercise their right to digital self determination, open and free software as well as services are indispensible.</li>
+    <li class="mt-4"><i class="fa-li fas fa-question-circle"></i> <b>How does re:claimID work?</b></li>
+    <li><i class="fa-li fas fa-comment"></i> re:claimID uses the GNU Name System as identity and attribute directory service. In order to allow the user to enforce access control decisions, we use a cryptographic access control layer. However, the user is not required to manage any cryptographic keys or manage zones in a namespace. This is done under the hood by re:claimID.</li>
+    <li class="mt-4"><i class="fa-li fas fa-question-circle"></i> <b>How does a website know the attribute data share via re:claimID is correct?</b></li>
+    <li><i class="fa-li fas fa-comment"></i> Short answer: It doesn't.
+      Long answer: Identities are initially self-asserted by the user. re:claimID could, however, also be used to share third party attested attributes (e.g. X.509 certificates). Further, have integrated <a href="https://github.com/Fraunhofer-AISEC/libpabc">Privacy-ABCs</a> for <a href="{{ url_localized('news/2021-05-DISSENS.html') }}">this use case</a>.</li>
+    <li class="mt-4"><i class="fa-li fas fa-question-circle"></i> <b>Who is behind re:claimID?</b></li>
+    <li><i class="fa-li fas fa-comment"></i> re:claimID was initially developed at <a href="https://aisec.fraunhofer.de">Fraunhofer AISEC</a> and is part of GNUnet.</li>
+    <li class="mt-4"><i class="fa-li fas fa-question-circle"></i> <b>I found a bug!</b></li>
+    <li><i class="fa-li fas fa-comment"></i> We aim to continuously develop and improve re:claimID. Help us by <a href="https://bugs.gnunet.org">reporting any issues you encounter</a>.</li>
+  </ul>
+</div>
+{% endblock body_content %}
diff --git a/template/reclaim/idps.html.j2 b/template/reclaim/idps.html.j2
new file mode 100644
index 00000000..5101b0d7
--- /dev/null
+++ b/template/reclaim/idps.html.j2
@@ -0,0 +1,30 @@
+{% extends "common/base.j2" %}
+{% block body_content %}
+<div class="m-3">
+  <a class="mt-2 mb-2" href="{{ url_localized('reclaim/index.html') }}">reclaimID</a> / IdPs
+</div>
+<h2 class="text-center">{{ _("For IdPs") }}</h2>
+<br/>
+<div class="container">
+  <h2><b>Step 1:</b> OpenID Service</h2>
+  As an identity provider and credential issuer, you need to setup an OpenID Connect server. There are many servers out there. For a list of servers, check out the <a href="https://openid.net/developers/certified/">OpenID website</a>.
+  One important caveat is that the server should allow you to issue user information inside the signed "ID Token".
+  The configuration regarding what user information goes into the token is of course completely under your discretion.
+  <h2 class="mt-5"><b>Step 2:</b> Configuring the reclaimID client</h2>
+  reclaimID uses special client values which must be registered at the OpenID server. The values are:
+  <ul>
+    <li><b>Client ID</b>: reclaimid</li>
+    <li><b>Client secret</b>: none (public client)</li>
+    <li><b>Redirect URI</b>: https://ui.reclaim</li>
+    <li><b>Grant type</b>: Authorization code</li>
+    <li><b>PKCE</b>: enabled (Optional but highly recommended)</li>
+  </ul>
+  <h2 class="mt-5"><b>Step 3:</b> Configuring a webfinger</h2>
+  You must support the webfinger-based <a href="https://openid.net/specs/openid-connect-discovery-1_0.html">OpenID Connect service discovery</a>.
+  Whenever the user configures an email address for an identity, reclaimID will try to discover the issuing identity provider through the OIDC Discovery protocol. This includes a <a href="https://openid.net/specs/openid-connect-discovery-1_0.html#EmailSyntax">request to the authority part of the email address</a>.
+  The response should point reclaimID to the actual OpenID Connect service <a href="https://openid.net/specs/openid-connect-discovery-1_0.html#ProviderMetadata">serving the issuer medatata</a>. reclaimID will try to request all scopes which are listed in the metadata, but does not expect all of them to be granted.
+</div>
+{% endblock body_content %}
diff --git a/template/reclaim/index.html.j2 b/template/reclaim/index.html.j2
new file mode 100644
index 00000000..c52b9ad6
--- /dev/null
+++ b/template/reclaim/index.html.j2
@@ -0,0 +1,102 @@
+{% extends "common/base.j2" %}
+{% block body_content %}
+<div class="container">
+  <div class="row">
+    <div class="container text-center">
+      <img style="width:50%" src="{{ url_static('images/reclaim_logo.png') }}"  alt="reclaimID" />
+      <br/>
+      <p class="mt-4">{{ _("Self-sovereign, Decentralised Identity Management and Personal Data Sharing") }}</p>
+    </div>
+  </div>
+</div>
+<div class="container-fluid greybox">
+  <div class="container">
+    <div class="row">
+      <div class="col-lg-2"></div>
+      <div class="col-lg-6">
+        <section>
+          <h2>{{ _("Self-sovereign") }}</h2>
+          <p>
+          {% trans %}
+          You manage your identities and attributes locally on your computer. No need to trust a third party service with your data.
+          {% endtrans %}
+          </p>
+        </section>
+      </div>
+      <div class="col-lg-3 homepageicon">
+        <span class="fas fa-fist-raised"></span>
+      </div>
+    </div>
+  </div>
+</div>
+<div class="container-fluid">
+  <div class="container">
+    <div class="row">
+      <div class="col-lg-2 homepageicon">
+        <span class="fas fa-project-diagram"></span>
+      </div>
+      <div class="col-lg-6">
+        <section>
+          <h2>{{ _("Decentralized") }}</h2>
+          <p>
+          {% trans %}
+          You can share your identity attributes securely over a decentralized name system. This allows your friends to access your shared data without the need of a trusted third party.
+          {% endtrans %}
+          </p>
+        </section>
+      </div>
+    </div>
+  </div>
+</div>
+<div class="container-fluid greybox">
+  <div class="container">
+    <div class="row">
+      <div class="col-lg-2"></div>
+      <div class="col-lg-6">
+        <section>
+          <h2>{{ _("Standard-compliant") }}</h2>
+          <p>
+          {% trans %}
+          You can use OpenID Connect to integrate reclaim in your web sites.
+          {% endtrans %}
+          </p>
+        </section>
+      </div>
+      <div class="col-lg-3 homepageicon">
+        <span class="fab fa-openid"></span>
+      </div>
+    </div>
+  </div>
+</div>
+<hr/>
+<div class="container-fluid">
+  <div class="container">
+    <div class="row">
+      <div class="col-md-4 mt-1">
+        <a class="frontpage btn btn-primary btn-lg" href="{{ url_localized('reclaim/tech.html') }}"><i class="fas fa-cubes"></i><br/>{{ _("Technology") }}</a>
+      </div>
+      <div class="col-md-4 mt-1">
+        <a class="frontpage btn btn-primary btn-lg" href="{{ url_localized('reclaim/motivation.html') }}"><i class="fas fa-fire"></i><br/>{{ _("Motivation") }}</a>
+      </div>
+      <div class="col-md-4 mt-1">
+        <a class="frontpage btn btn-primary btn-lg" href="{{ url_localized('reclaim/faq.html') }}"><i class="fas fa-question"></i><br/>{{ _("FAQ") }}</a>
+      </div>
+    </div>
+    <div class="row">
+      <div class="col-md-4 mt-1">
+        <a class="frontpage btn btn-primary btn-lg" href="{{ url_localized('reclaim/users.html') }}"><i class="fas fa-user"></i><br/>{{ _("For users") }}</a>
+      </div>
+      <div class="col-md-4 mt-1">
+        <a class="frontpage btn btn-primary btn-lg" href="{{ url_localized('reclaim/websites.html') }}"><i class="fas fa-globe"></i><br/>{{ _("For websites") }}</a>
+      </div>
+      <div class="col-md-4 mt-1">
+        <a class="frontpage btn btn-primary btn-lg" href="{{ url_localized('reclaim/idps.html') }}"><i class="fas fa-users"></i><br/>{{ _("For IdPs") }}</a>
+      </div>
+    </div>
+  </div>
+</div>
+{% endblock body_content %}
diff --git a/template/reclaim/motivation.html.j2 b/template/reclaim/motivation.html.j2
new file mode 100644
index 00000000..973fbddf
--- /dev/null
+++ b/template/reclaim/motivation.html.j2
@@ -0,0 +1,34 @@
+{% extends "common/base.j2" %}
+{% block body_content %}
+<div class="m-3">
+  <a class="mt-2 mb-2" href="{{ url_localized('reclaim/index.html') }}">reclaimID</a> / Motivation
+</div>
+<h2 class="text-center">{{ _("Motivation") }}</h2>
+<br/>
+<div class="container">
+<p>
+Today, users are often required to share personal data, like email addresses, to use services on the web. As part of normal service operation, such as notifications or billing, services require access to -- ideally fresh and correct -- user data.
+Sharing attributes in the Web today is often done via centralized service providers to reduce data redundancy and to give services access to current, up-to-date information even if the user is currently offline.
+Abuse of this power is theoretically limited by local laws and regulations.
+But, the past has shown that even well-meaning identity providers struggle to keep user data safe as they become major targets for hackers and nation state actors while striving for monetizing anonymized statistics from these data.
+We advocate for a new, decentralized way for users to manage their identities for the following reasons:
+</p>
+<ul class="fa-ul">
+  <li><i class="fa-li fas fa-caret-right"></i> The current state of omniscient identity providers is a significant threat to the users' privacy.</li>
+  <li><i class="fa-li fas fa-caret-right"></i> Users must completely trust the service provider with respect to protecting the integrity and confidentiality of their identity in their interest.</li>
+  <li><i class="fa-li fas fa-caret-right"></i> The service provider itself is facing substantial liability risks given the responsibility of securely managing potentially sensitive personal data of millions of users.</li>
+</ul>
+<p>re:claimID is built as a service on top of the peer-to-peer framework <a href="https://gnunet.org">GNUnet</a>.<br/>
+It emerged from research conducted by the research group "Secure
+Applications and Services" at the <a href="https://www.aisec.fraunhofer.de/de/fields-of-expertise/projekte/reclaim.html">Fraunhofer AISEC</a> research institute.<br/>
+A scientific, peer-reviewed paper on the theoretical foundations of re:claimID
+was published at <a href="https://ieeexplore.ieee.org/document/8456003">TrustCom 2018</a>
+(<a href="https://arxiv.org/abs/1805.06253v1">Arxiv</a>).<br/> re:claimID is
+primarily developed in the
+<a href="https://git.gnunet.org/gnunet.git/tree/src/reclaim">GNUnet source tree</a>.
+Accompanying tools and sources can be found in the
+<a href="https://gitlab.com/reclaimid">Gitlab project</a>.
+</p>
+</div>
+{% endblock body_content %}
diff --git a/template/reclaim/tech.html.j2 b/template/reclaim/tech.html.j2
new file mode 100644
index 00000000..4223cf5b
--- /dev/null
+++ b/template/reclaim/tech.html.j2
@@ -0,0 +1,115 @@
+{% extends "common/base.j2" %}
+{% block body_content %}
+<div class="m-3">
+  <a class="mt-2 mb-2" href="{{ url_localized('reclaim/index.html') }}">reclaimID</a> / Technology
+</div>
+<h2 class="text-center">{{ _("Overview") }}</h2>
+<div style="text-align:center">
+  <img style="width:50%" src="{{ url_static('images/reclaim/reclaim_eq.png') }}"/>
+</div>
+<br/>
+<div class="container">
+  <div class="row">
+    <div class="col-lg-6">
+      <h3>
+        {{ _("Decentralised identity directory") }}
+      </h3>
+      <p>
+      {% trans %}
+      The decentralised GNU Name System (GNS) gives users full and exclusive authority over their attributes by sharing them over user-owned namespaces.
+      {% endtrans %}
+      </p>
+    </div>
+    <div class="col-lg-6">
+      <div>
+        <h3>
+          {{ _("Cryptographic access control") }}
+        </h3>
+      </div>
+      <p>
+      {% trans %}
+Users regularly publish fresh, up-to-date attributes which can be retrieved and
+read only by authorized relying parties parties without direct user interaction -- even if the user is offline!
+      {% endtrans %}
+      </p>
+    </div>
+  </div>
+</div>
+<hr/>
+<h2 class="text-center">{{ _("Principles") }}</h2>
+<div class="container-fluid greybox">
+  <div class="container">
+    <div class="row">
+      <div class="col-lg-1"></div>
+      <div class="col-lg-6">
+        <section>
+        <h2>{{ _("Identity and attribute management") }}</h2>
+        <p>
+        {% trans %}
+      Users regularly publish fresh, up-to-date attributes which can be retrieved by requesting parties without direct user interaction -- even if the user is offline!
+      Access to attributes is controlled through an ecryption based access
+      control layer.
+        {% endtrans %}
+        </p>
+        </section>
+      </div>
+      <div class="col-lg-5 homepageicon">
+        <a href="{{ url_static('images/reclaim/Reclaim-2.png') }}"><img style="width:100%" src="{{ url_static('images/reclaim/Reclaim-2.png') }}"/></a>
+      </div>
+    </div>
+  </div>
+</div>
+<div class="container-fluid">
+  <div class="container">
+      <div class="row">
+      <div class="col-lg-5 homepageicon">
+        <a href="{{ url_static('images/reclaim/Reclaim-3.png') }}"><img style="width:100%" src="{{ url_static('images/reclaim/Reclaim-3.png') }}"/></a>
+      </div>
+      <div class="col-lg-6">
+      <section>
+        <h2>{{ _("Authorization") }}</h2>
+        <p>
+        {% trans %}
+        To access attributes, requesting parties request authorization from the
+        user thrugh the use of OpenID Connect.
+        If access is granted, the relying party is given the necessary decryption
+        key material.
+        The user may at any time revoke this access or modify the authorization decision.
+        {% endtrans %}
+        </p>
+      </section>
+    </div>
+  </div>
+</div>
+<div class="container-fluid greybox">
+  <div class="container">
+    <div class="row">
+      <div class="col-lg-1"></div>
+      <div class="col-lg-6">
+        <section>
+        <h2>{{ _("Attribute retrieval") }}</h2>
+        <p>
+        {% trans %}
+      Relying parties retrieve encrypted identity data from the decentralised
+      directory.
+      It is able to decrypt all those attributes that the user has authorized
+      it to access using the respective key.
+        {% endtrans %}
+        </p>
+        </section>
+      </div>
+      <div class="col-lg-5 homepageicon">
+        <a href="{{ url_static('images/reclaim/Reclaim-4.png') }}"><img style="width:100%" src="{{ url_static('images/reclaim/Reclaim-4.png') }}"/></a>
+      </div>
+    </div>
+  </div>
+</div>
+<hr/>
+<h2 style="text-align:center" class="mt-2">Videos and Talks</h2>
+<ul class="fa-ul">
+  <li><i class="fa-li fas fa-caret-right"></i> <a href="https://youtu.be/PlSX-o36Wus?t=5371">IETF Meeting #104; Privacy Enhancements and Assessments Research Group - March 2019</a> (<a href="https://git.gnunet.org/presentations.git/plain/IETF104/slides-104-pearg-reclaim-00.pdf">Slides</a>)</li>
+  <li><i class="fa-li fas fa-caret-right"></i> <a href="https://media.ccc.de/v/ds19-10383-re_claimid">Datenspuren 2019 - September 2019 (German)</a> (<a href="https://git.gnunet.org/presentations.git/plain/datenspuren2019/datenspuren2019.pdf">Slides</a>, English)</li>
+</ul>
+{% endblock body_content %}
diff --git a/template/reclaim/users.html.j2 b/template/reclaim/users.html.j2
new file mode 100644
index 00000000..8b78dc11
--- /dev/null
+++ b/template/reclaim/users.html.j2
@@ -0,0 +1,40 @@
+{% extends "common/base.j2" %}
+{% block body_content %}
+<div class="m-3">
+  <a class="mt-2 mb-2" href="{{ url_localized('reclaim/index.html') }}">reclaimID</a> / Users
+</div>
+<h2 class="text-center">{{ _("For users") }}</h2>
+<br/>
+<div class="container">
+  <h2><b>Step 1:</b> Installation</h2>
+  <p>
+    Please use the <a href="{{ url_localized('install.html') }}">GNUnet installation guides</a>.
+  </p>
+  <h2 class="mt-5"><b>Step 2:</b> Browser plugin</h2>
+  <p>You also need to install a browser plugin:</p>
+  <div class="centering">
+    <a class="btn btn-primary" target="_blank" rel="noopener noreferrer"
+                                               href="https://addons.mozilla.org/addon/reclaimid/"><i class="fab fa-firefox"></i> Mozilla Firefox</a>
+    <a class="btn btn-primary" target="_blank" rel="noopener noreferrer"
+                                               href="https://chrome.google.com/webstore/detail/reclaimid/jiogompmdejcnacmlnjhnaicgkefcfll"><i class="fab fa-chrome"></i> Chrome / Chromium</a>
+  </div>
+  <br/>
+  <h2 class="mt-5"><b>Step 3:</b> Creating your first identity</h2>
+  <p>Almost there. Now try adding a new identity at <a href="https://ui.reclaim">your local re:claimID instance</a> and add some attributes to it.
+  <br/>
+  <h2 class="mt-5">Websites supporting re:claimID</h2>
+  <p>To test a login with one of your re:claimID identities, you can go to one of the websites supporting it:</p>
+  <ul>
+    <li><a href="https://demo.reclaim-identity.io">Our demo messaging board</a> (<a href="https://gitlab.com/reclaimid/demo">Source</a>)</li>
+    <li><a href="https://eusec.clouditor.io">Clouditor EUSEC project page</a></li>
+  </ul>
+  <h2 class="mt-5">Troubleshooting</h2>
+  In case you encounter any problems, please check for <a href="https://bugs.gnunet.org">known issues and report bugs to help us improve re:claimID!</a>
+</div>
+{% endblock body_content %}
diff --git a/template/reclaim/websites.html.j2 b/template/reclaim/websites.html.j2
new file mode 100644
index 00000000..f4e7fec9
--- /dev/null
+++ b/template/reclaim/websites.html.j2
@@ -0,0 +1,45 @@
+{% extends "common/base.j2" %}
+{% block body_content %}
+<div class="m-3">
+  <a class="mt-2 mb-2" href="{{ url_localized('reclaim/index.html') }}">reclaimID</a> / Websites
+</div>
+<h2 class="text-center">{{ _("For websites") }}</h2>
+<div class="container">
+  <h2><b>Step 1:</b> Installation</h2>
+  <p>
+    Please use the <a href="{{ url_localized('install.html') }}">GNUnet installation guides</a>.
+  </p>
+  <h2 class="mt-5"><b>Step 2:</b> Registering an OpenID Connect client</h2>
+  <p>The easiest way to manage OpenID Connect client is through our CLI tool:</p>
+  <code class="block">$ gem install reclaim-oidc</code>
+  <p>To register an OpenID Connect client, execute:</p>
+  <code class="block">$ reclaim-oidc --add --client-name myclient --redirect-uri https://mywebsite.com/oidc_cb --description "My Client"</code>
+  <p>You can list all registered clients and your local OpenID Connect metadata required to initiate an authorization code flow by executing:</p>
+  <code class="block">$ reclaim-oidc --list </code>
+  <p>The response will look like this</p>
+  <code class="block">OpenID Connect Provider Information:<br/>
+  ------------------------------------<br/>
+  Authorize Endpoint: http://localhost:7776/openid/authorize<br/>
+  Token Endpoint: http://localhost:7776/openid/token<br/>
+  JSON-Web-Token Algorithm: HS512<br/>
+  JSON-Web-Token key: secret<br/>
+  Example Authorization Redirect:<br/>
+  https://api.reclaim/openid/authorize?client_id=&lt;client_id&gt;&amp;redirect_uri=&lt;redirect_uri&gt;&amp;response_type=code&amp;scope=email%20full_name&amp;nonce=1234<br/>
+  <br/>
+  Registered Clients:<br/>
+  -------------------<br/>
+  name: myclient<br/>
+  client_id: &lt;client_id&gt;<br/>
+  client_secret: &lt;client_secret&gt;<br/>
+  description: My Client<br/>
+  redirect_uri: https://mywebsite.com/oidc_cb<br/>
+  ...
+  </code>
+  <div class="alert alert-info"><b>NOTE</b>: The client secrets and JWT token signing keys can be configured. However, due to the fact that re:claimID endpoint are running on your local machine, they are not critical.</div>
+  <h2 class="mt-5"><b>Step 3:</b> Website integration</h2>
+  <p>You can use the information above to integrate re:claimID as a generic <a href="https://openid.net/specs/openid-connect-core-1_0.html">OpenID Connect Identity Provider</a> into the web application of your choice. The integration steps for this part depend on the application you use. Hence, please refer to your respective documentation or the OpenID Connect specifications.
+  </p>
+  <p>The sources of our <a href="https://demo.reclaim-identity.io">demo website</a> can be found in our <a href="https://gitlab.com/reclaimid/demo">gitlab project</a>.</p>
+</div>
+{% endblock body_content %}
diff --git a/template/roadmap.html.j2 b/template/roadmap.html.j2
index 51cc6fcc..7eff2569 100644
--- a/template/roadmap.html.j2
+++ b/template/roadmap.html.j2
@@ -4,25 +4,34 @@
  <div class="row">
    <div class="container text-center">
      <h1>{{ _("Roadmap") }}</h1>
-      <section>
-        <p>
-         This is our roadmap.
-        </p>
-      </section>
    </div>
+    <p>
+      This is our roadmap. We distinguish between short, medium and long term goals.
+      The roadmap is subject to change and its primary purpose it to indicate the current work in progress and future work as well as the path to a stable release. Goals which are currently in active development are marked in <b>bold</b>.
+    </p>
    <ul class="timeline">
      <li>
        <section class="item-preview">
          <header>
            <h3>Short term</h3>
            <p class="item-date">
-            0.13.x
+            &le;0.16
            </p>
            <p class="item-abstract">
-            <ul>
+            <ul class="fa-ul">
-              <li>Setup and use names and numbers registration (GANA) for GNUnet
+              <li><span class="fa-li"><i class="far fa-square"></i></span>DHT:
-              subsystems.</li>
+                <ul class="fa-ul">
-              <li>GNU Name System technical specification.</li>
+                  <li><span class="fa-li"><i class="far fa-square"></i></span>Improvements including signed paths and stability improvements. Technical specification.</li>
+                  <li><span class="fa-li"><i class="far fa-square"></i></span><a href="https://lsd.gnunet.org/lsd0000/">Technical specification</a>.</li>
+                </ul>
+              </li>
+              <li><span class="fa-li"><i class="far fa-minus-square"></i></span><b>SET:</b>
+                <ul class="fa-ul">
+                  <li><span class="fa-li"><i class="far fa-minus-square"></i></span><b>Improvements to code quality and correctness</b>.</li>
+                  <li><span class="fa-li"><i class="far fa-minus-square"></i></span><a href="https://lsd.gnunet.org/lsd0003/"><b>Technical specification</a></b>.</li>
+                </ul>
+              </li>
+              <li><span class="fa-li"><i class="far fa-minus-square"></i></span><b>RECLAIM: <a href="https://lsd.gnunet.org/lsd0002/">Technical specification</a></b>.</li>
             </ul>
            </p>
          </header>
@@ -34,17 +43,23 @@
          <header>
            <h3>Medium term</h3>
            <p class="item-date">
-            0.14 and beyond
+            &gt;0.16
            </p>
            <p class="item-abstract">
-            <ul>
+            <ul class="fa-ul">
-              <li>TNG: Transport rewrite complete including basic service, communicators and NAT.</li>
+              <li><span class="fa-li"><i class="far fa-minus-square"></i></span><b>TNG</b>: Transport rewrite. [<a href="https://bugs.gnunet.org/search.php?tag_string=tng">Open issues</a>]
-              <li>CORE/CADET performance and correctness improvements.</li>
+                <ul class="fa-ul">
-              <li>DHT improvements including signed paths and stability improvements.</li>
+                  <li><span class="fa-li"><i class="far fa-minus-square"></i></span><b>TNG service</b></li>
-              <li>SET improvements to code quality and correctness.</li>
+                  <li><span class="fa-li"><i class="far fa-minus-square"></i></span><b>TCP communicator</b></li>
-              <li>CONVERSATION improvements to performance, latency hiding and usability.</li>
+                  <li><span class="fa-li"><i class="far fa-minus-square"></i></span><b>UDP communicator</b></li>
-              <li>Stable and usable documentation.</li>
+                  <li><span class="fa-li"><i class="far fa-minus-square"></i></span><b>UNIX Domain Socket communicator</b></li>
-              <li>GNUnet packages available and up-to-date in distributions.</li>
+                  <li><span class="fa-li"><i class="far fa-square"></i></span>NAT</li>
+                </ul>
+              </li>
+              <li><span class="fa-li"><i class="far fa-square"></i></span>CORE/CADET: Performance and correctness improvements.</li>
+              <li><span class="fa-li"><i class="far fa-square"></i></span>CONVERSATION improvements to performance, latency hiding and usability.</li>
+              <li><span class="fa-li"><i class="far fa-minus-square"></i></span><b>Stable and usable documentation.</b></li>
+              <li><span class="fa-li"><i class="far fa-minus-square"></i></span><b>GNUnet packages available and up-to-date in distributions.</b></li>
             </ul>
            </p>
          </header>
@@ -59,12 +74,12 @@
            1.x
            </p>
            <p class="item-abstract">
-            <ul>
+            <ul class="fa-ul">
-              <li>Stable release.</li>
+              <li><span class="fa-li"><i class="far fa-square"></i></span>Stable release.</li>
-              <li>Onion routing with RPS</li>
+              <li><span class="fa-li"><i class="far fa-square"></i></span>Onion routing with RPS</li>
-              <li>Mix network, pEp integration on top of mix network</li>
+              <li><span class="fa-li"><i class="far fa-square"></i></span>Mix network, pEp integration on top of mix network</li>
-              <li>Collaborative filtering / news distribution</li>
+              <li><span class="fa-li"><i class="far fa-square"></i></span>Collaborative filtering / news distribution</li>
-              <li>Improved FS design, proper integration with GNS</li>
+              <li><span class="fa-li"><i class="far fa-square"></i></span>Improved FS design, proper integration with GNS</li>
             </ul>
            </p>
          </header>
diff --git a/template/rss.xml.j2 b/template/rss.xml.j2
new file mode 100644
index 00000000..d0197c00
--- /dev/null
+++ b/template/rss.xml.j2
@@ -0,0 +1,46 @@
+{#
+# Copyright (C) 2019, 2020 GNUnet e.V.
+#
+# This code is derived from code contributed to GNUnet eV
+# by nikita <nikita@n0.is>.
+#
+# Permission to use, copy, modify, and/or distribute this software for
+# any purpose with or without fee is hereby granted.
+#
+# THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL
+# WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED
+# WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE
+# AUTHOR BE LIABLE FOR ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL
+# DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR
+# PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
+# TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
+# PERFORMANCE OF THIS SOFTWARE.
+#
+# SPDX-License-Identifier: 0BSD
+#}
+<?xml version="1.0" encoding="UTF-8"?>
+<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
+  <channel>
+    <atom:link href="{{ siteconf['baseurl'] }}{{ lang }}/rss.xml" rel="self" type="application/rss+xml" />
+    <title>{{ siteconf['rsstitle'] }}</title>
+    <language>{{ lang }}</language>
+    <description>{{ siteconf['rssdescr']|e }}</description>
+    <link>{{ siteconf['baseurl'] }}/</link>
+    <lastBuildDate>{{ now }}</lastBuildDate>
+    {% for newspostitem in newsposts %}
+      <item>
+        <guid>{{ siteconf['baseurl'] }}{{ lang }}{{ siteconf['newsloc'] }}{{ newspostitem['page'] }}</guid>
+        <link>{{ siteconf['baseurl'] }}{{ lang }}{{ siteconf['newsloc'] }}{{ newspostitem['page'] }}</link>
+        <pubDate>{{ conv_date_rfc822(newspostitem["date"]) }}</pubDate>
+        <title>{{ newspostitem['title']|e }}</title>
+        <description>
+          <![CDATA[
+             {% filter extract_body %}
+             {% include (newspostitem['page'] + ".j2") %}
+             {% endfilter %}
+           ]]>
+        </description>
+      </item>
+    {% endfor %}
+  </channel>
+</rss>
diff --git a/template/use.html.j2 b/template/use.html.j2
index a049b2a5..8dc7abd5 100644
--- a/template/use.html.j2
+++ b/template/use.html.j2
@@ -206,7 +206,7 @@
        </code>
        </p>
        
-        <p>It's worth nothing that the other peers can be a friend's machine which has GNUnet running, or it can also just be another shell on your own machine.</p>
+        <p>It's worth noting that the other peers can be a friend's machine which has GNUnet running, or it can also just be another shell on your own machine.</p>
        
        <p>
              If you are interested in the details of CADET, please read the <a href="https://docs.gnunet.org/handbook/gnunet.html#CADET-Subsystem">"Cadet-Subsystem" chapter in the GNUnet handbook</a>. 
@@ -573,4 +573,4 @@
    </div>
  </div>
 </article>
-{% endblock body_content %}
-\ No newline at end of file
+{% endblock body_content %}