summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorStefan Kügel <skuegel@web.de>2021-03-08 22:53:42 +0100
committerStefan Kügel <skuegel@web.de>2021-03-08 22:53:42 +0100
commitfb122c30a47330a363c72d3c0b1d149a3f404b6e (patch)
treeb743454e10cbe01d5711860d942433105d393689
parent1c9d87b80c82c12d8bd025022781436efbd76745 (diff)
downloadwww-fb122c30a47330a363c72d3c0b1d149a3f404b6e.tar.gz
www-fb122c30a47330a363c72d3c0b1d149a3f404b6e.tar.bz2
www-fb122c30a47330a363c72d3c0b1d149a3f404b6e.zip
Eliminated double blanks
-rw-r--r--template/principles.html.j228
1 files changed, 12 insertions, 16 deletions
diff --git a/template/principles.html.j2 b/template/principles.html.j2
index 81a035a9..683b7449 100644
--- a/template/principles.html.j2
+++ b/template/principles.html.j2
@@ -40,7 +40,7 @@
their payments.
For countries, Free/Libre
software means GNU Taler can not compromise sovereignty by imposing
- restrictions or requirements. And for exchange operators, transparency is crucial to satisfy
+ restrictions or requirements. And for exchange operators, transparency is crucial to satisfy
<a href="https://en.wikipedia.org/wiki/Kerckhoffs's_principle">Kerckhoff's principle</a>
and to establish public confidence.
{% endtrans %}
@@ -63,9 +63,9 @@
<p>
{% trans %}
Privacy is most meaningful when it is guaranteed via technical measures, as opposed to mere
- policies. Without a technical layer providing privacy-by-default, financial transactions
- reveal unnecessary levels of personal or private data. This would be especially true
- when making micropayments for online publications. Thus, GNU Taler must protect
+ policies. Without a technical layer providing privacy-by-default, financial transactions
+ reveal unnecessary levels of personal or private data. This would be especially true
+ when making micropayments for online publications. Thus, GNU Taler must protect
the privacy of buyers to avoid facilitating totalitarian control over the population.
{% endtrans %}
@@ -87,7 +87,7 @@
{% trans %}
As a payment system must comply with local laws in order to operate
legally, GNU Taler must be designed to comply with these
- requirements. GNU Taler must provide an audit trail for investigators
+ requirements. GNU Taler must provide an audit trail for investigators
operating under the law.
Furthermore, we consider levying of taxes as
@@ -144,7 +144,7 @@
other platforms.
GNU Taler must follow best-practices usability guidelines and
- incorporate feedback from experts and users. Free/Libre software also
+ incorporate feedback from experts and users. Free/Libre software also
requires Free/Libre documentation to allow for informed choices.
GNU Taler must provide well-documented Application Programming Interfaces (APIs)
to allow frictionless integrations between GNU Taler and other projects.
@@ -174,13 +174,13 @@
<img style="width:20vw;float:left;padding:15px" src="{{ url_static('images/8-fault-tolerant.png') }}" alt="{{_("Life Safers")}}">
<p>
{% trans %}
- Malicious operators, fat fingers, computer glitches, gremlins. Things
+ Malicious operators, fat fingers, computer glitches, gremlins. Things
go wrong.
GNU Taler must be designed to tolerate failure of individual components and
- systems. Where the system can continue running safely, it will continue
- running safely. Where it must halt an operation, other operations
- must not be needlessly pulled offline. Where systems fail,
+ systems. Where the system can continue running safely, it will continue
+ running safely. Where it must halt an operation, other operations
+ must not be needlessly pulled offline. Where systems fail,
they must fail gracefully.
GNU Taler must have a plan to recover from malicious operators
@@ -199,14 +199,10 @@
barriers for this in traditional financial systems are rather high and outside
of our control. However, GNU Taler must minimize the technical
burden for new competitors to enter the market.
- {% endtrans %}
-
- {% trans %}
+
GNU Taler must enable a diverse set of operators, breaking up the current
system where only a few global companies dominate the market.
- {% endtrans %}
-
- {% trans %}
+
An example for a design choice that supports this is to split the whole system into
smaller components that can be operated, developed and improved upon independently,
instead of having one completely monolithic system.