gnunet-svn
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[GNUnet-SVN] [taler-www] branch master updated (625cd04 -> 486ac69)


From: gnunet
Subject: [GNUnet-SVN] [taler-www] branch master updated (625cd04 -> 486ac69)
Date: Thu, 27 Jun 2019 16:22:41 +0200

This is an automated email from the git hooks/post-receive script.

grothoff pushed a change to branch master
in repository www.

    from 625cd04  images
     new 0c166c7  img
     new 486ac69  img

The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 images/life-safer.jpg        | Bin 0 -> 803370 bytes
 images/life-safer.medium.jpg | Bin 0 -> 305571 bytes
 principles.html.j2           |  11 ++++++-----
 3 files changed, 6 insertions(+), 5 deletions(-)
 create mode 100644 images/life-safer.jpg
 create mode 100644 images/life-safer.medium.jpg

diff --git a/images/life-safer.jpg b/images/life-safer.jpg
new file mode 100644
index 0000000..0105be6
Binary files /dev/null and b/images/life-safer.jpg differ
diff --git a/images/life-safer.medium.jpg b/images/life-safer.medium.jpg
new file mode 100644
index 0000000..a5ff931
Binary files /dev/null and b/images/life-safer.medium.jpg differ
diff --git a/principles.html.j2 b/principles.html.j2
index 55e4956..19bec38 100644
--- a/principles.html.j2
+++ b/principles.html.j2
@@ -134,14 +134,15 @@ Approaches such as proof-of-work are ruled out by this 
requirement. Efficiency i
   </div>
   <div class="row">
     <div class="col-lg-6">
-    <!-- IMAGE. -->
+      <p><img style="width:20vw" src="../images/life-safer.medium.png" 
alt="Life Safers"></a></p>
     </div>
     <div class="col-lg-6">
-      <h2>8. Avoid single points of failure</a></h2>
+      <h2>8. Fault-tolerant design</a></h2>
       <p>
-While the design we present later is rather centralized, avoiding single
-points of failure is still a goal. This manifests in architectural choices such
-as the isolation of certain components, and auditing procedures.
+        Taler should tolerate failure of individual components and systems,
+        including malicious operators compromising core secrets.
+        This manifests in architectural choices such
+        as the isolation of certain components, and auditing procedures.
       </p>
     </div>
   </div>

-- 
To stop receiving notification emails like this one, please contact
address@hidden.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]