Fix small errors in minimalisticstandards (#2433)
continuous-integration/drone/push Build is passing
Details
continuous-integration/drone/push Build is passing
Details
This PR adds some fixes for the minimalisticstandards page. Fixes #2411. Reviewed-on: #2433 Co-authored-by: Fabian Baumanis <fbn_bmns@fsfe.org> Co-committed-by: Fabian Baumanis <fbn_bmns@fsfe.org>
This commit is contained in:
parent
622aa9e19e
commit
d404f7ddff
|
@ -217,7 +217,7 @@
|
|||
<li id="fn-complexity">"Complexity is the main enemy of security",
|
||||
Ferguson, Niels, and Schneier, Bruce - Practical Cryptography, Wiley, 2003,
|
||||
ISBN 0-471-22357-3. p146 "9.4.1 Simplicity", pp365- "23 Standards"
|
||||
<a href="http://www.macfergus.com/pc">http://www.macfergus.com/pc</a> [<a href="#ref-complexity">↲</a>]</li>
|
||||
<a href="https://www.schneier.com/books/practical-cryptography">https://www.schneier.com/books/practical-cryptography</a> [<a href="#ref-complexity">↲</a>]</li>
|
||||
</ol>
|
||||
|
||||
</body>
|
||||
|
|
|
@ -28,7 +28,7 @@
|
|||
language to your computer. If a data-format does not allow for the
|
||||
inclusion of pictures, for example, then there is no way to include
|
||||
pictures with it. The choice of data-format dictates the number of years
|
||||
for which may access the content (backwards compatibility) and what I am
|
||||
for which I may access the content (backwards compatibility) and what I am
|
||||
able do with it. </p>
|
||||
|
||||
<p>A single user will probably not feel any effect of her decision when
|
||||
|
@ -39,7 +39,7 @@
|
|||
or pictures electronically, the more important it becomes to secure
|
||||
continued access to the documents. These decisions, directly or indirecty,
|
||||
lead to the funding of the initial development and maintenance of
|
||||
data-formats, wether they be "good or bad" formats. The choices taken at
|
||||
data-formats, whether they be "good or bad" formats. The choices taken at
|
||||
one time naturally affect the available choices in the future: Many
|
||||
software producers intentionally try to influence users to use a
|
||||
data-format that they (the producer) control. For example when technical
|
||||
|
@ -204,7 +204,7 @@ possibilities of Unicode in URLs</a>.</p>
|
|||
this. It just has one rule: Remove everything that is not absolutely
|
||||
necessary. Aim for your design to be <a
|
||||
href="http://www.paulgraham.com/taste.html">simple and elegant</a>. A good
|
||||
solution resembles as set of building blocks where an infinite number of
|
||||
solution resembles a set of building blocks where an infinite number of
|
||||
buildings can be made, just by combining a few types of elements.</p>
|
||||
|
||||
<p>Even though there may be good reasons to choose a data-format which
|
||||
|
@ -216,7 +216,7 @@ possibilities of Unicode in URLs</a>.</p>
|
|||
<li id="fn-complexity">"Complexity is the main enemy of security",
|
||||
Ferguson, Niels, and Schneier, Bruce - Practical Cryptography, Wiley, 2003,
|
||||
ISBN 0-471-22357-3. p146 "9.4.1 Simplicity", pp365- "23 Standards"
|
||||
<a href="http://www.schneier.com/book-practical.html">http://www.schneier.com/book-practical.html</a> [<a href="#ref-complexity">↲</a>]</li>
|
||||
<a href="https://www.schneier.com/book-practical.html">https://www.schneier.com/book-practical.html</a> [<a href="#ref-complexity">↲</a>]</li>
|
||||
</ol>
|
||||
|
||||
Thanks for suggestions, proof reading and translation work to Peter Bubestinger, Philipp Kammerer, the folks from the FSFE DE mailinglist and
|
||||
|
|
Loading…
Reference in New Issue