Fix code to conform with code style
This commit is contained in:
parent
03f94a2bde
commit
9cc6edd522
30
contact.html
30
contact.html
@ -5,7 +5,7 @@
|
||||
<!-- Copyright 2022 Jake Winters -->
|
||||
<!-- SPDX-License-Identifier: BSD-3-Clause -->
|
||||
|
||||
<!-- Version: 6.2.0-alpha.4 -->
|
||||
<!-- Version: 6.2.0-alpha.5 -->
|
||||
|
||||
|
||||
<html>
|
||||
@ -43,14 +43,15 @@
|
||||
<section id="e2ee">
|
||||
<h2 id="e2ee"><a href="#e2ee">End-to-end Encrypted Contact Methods</a></h2>
|
||||
<h3 id="e2ee-preferred"><a href="#e2ee-preferred">Preferred</a></h3>
|
||||
<p>Whenever possible, use the following contact methods; they allow verification
|
||||
to mitigate man-in-the-middle attacks, have high security, and reasonable
|
||||
privacy.<br>
|
||||
<p>Whenever possible, use the following contact methods; they allow
|
||||
verification to mitigate man-in-the-middle attacks, have high security,
|
||||
and reasonable privacy.<br>
|
||||
<br>
|
||||
<p><strong>Use the
|
||||
<a href="key.html">keys</a> for each contact method to verify my devices.</strong><br>
|
||||
Note: Verification does not verify a person, only their devices, and can be
|
||||
defeated via coercion or other force.</p>
|
||||
<a href="key.html">keys</a>
|
||||
for each contact method to verify my devices.</strong><br>
|
||||
Note: Verification does not verify a person, only their devices, and can
|
||||
be defeated via coercion or other force.</p>
|
||||
<p><img src="asset/img/logo-signal.png" class="logo-small" width="40px" height="40px"/> Signal<br>
|
||||
<br>
|
||||
+447549902964<p><br>
|
||||
@ -63,18 +64,21 @@
|
||||
(<a href="key.html#xmpp-notyourchat">Key</a>)</p>
|
||||
<!--
|
||||
<h3 id="e2ee-metadatafree"><a href="#e2ee-metadatafree">Metadata-free</a></h3>
|
||||
<p>If metadata leakage is an issue for you, you can use the following contact methods.<br>
|
||||
<p>If metadata leakage is an issue for you, you can use the following
|
||||
contact methods.<br>
|
||||
<br>
|
||||
Note: These services do not have verification functionality and will be treated
|
||||
as less secure; <strong>unless you really need to use these services, use a
|
||||
preferred method instead.</strong></p>
|
||||
Note: These services do not have verification functionality and will be
|
||||
treated as less secure; <strong>unless you really need to use these
|
||||
services, use a preferred method instead.</strong></p>
|
||||
-->
|
||||
</section>
|
||||
<!--<section id="non_private">
|
||||
<!--
|
||||
<section id="non_private">
|
||||
<!--<h2 id="non_private"><a href="#non_private" class="h2">Non-private Contact Methods</a></h2>
|
||||
<p>The following contact methods do not utilise end-to-end encryption, or I do not use
|
||||
such functionality; they are suitable for public contact only, including directly and
|
||||
groups. Do not use these methods if confidentiality and/or privacy is required.</p>
|
||||
</section>-->
|
||||
</section>
|
||||
-->
|
||||
</body>
|
||||
</html>
|
||||
|
Loading…
x
Reference in New Issue
Block a user