Inferencium/website
1
0
Fork 0
Code Issues Activity

Add section "e2ee-preferred"

Browse Source
This commit is contained in:
inference 2023-11-13 23:34:40 +00:00
parent f429512e5f
commit 87404bef72
Signed by: inference
SSH Key Fingerprint: SHA256:FtEVfx1CmTKMy40VwZvF4k+3TC+QhCWy+EmPRg50Nnc
1 changed files with 32 additions and 29 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

61
contact.html
View File

@ -5,7 +5,7 @@
<!-- Copyright 2022 Jake Winters --> <!-- Copyright 2022 Jake Winters -->
<!-- SPDX-License-Identifier: BSD-3-Clause --> <!-- SPDX-License-Identifier: BSD-3-Clause -->
<!-- Version: 6.2.0-alpha.8 --> <!-- Version: 6.2.0-alpha.9 -->
<html> <html>
@ -42,34 +42,37 @@
</section> </section>
<section id="e2ee"> <section id="e2ee">
<h2 id="e2ee"><a href="#e2ee">End-to-end Encrypted Contact Methods</a></h2> <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> <section id="e2ee-preferred">
<p>Whenever possible, use the following contact methods; they allow <h3 id="e2ee-preferred"><a href="#e2ee-preferred">Preferred</a></h3>
verification to mitigate man-in-the-middle attacks, have high security, <p>Whenever possible, use the following contact methods; they
and reasonable privacy.</p> allow verification to mitigate man-in-the-middle attacks, have
<p><strong>Use the high security, and reasonable privacy.</p>
<a href="key.html">keys</a> <p><strong>Use the
for each contact method to verify my devices.</strong><br> <a href="key.html">keys</a>
Note: Verification does not verify a person, only their devices, and can for each contact method to verify my devices.</strong><br>
be defeated via coercion or other force.</p> Note: Verification does not verify a person, only their devices,
<p><img src="asset/img/logo-signal.png" class="logo-small" width="40px" height="40px"/> Signal<br> and can be defeated via coercion or other force.</p>
<br> <p><img src="asset/img/logo-signal.png" class="logo-small" width="40px" height="40px"/> Signal<br>
+447549902964<p> <br>
<p><img src="asset/img/logo-xmpp.png" class="logo-small" width="40px" height="40px"/> XMPP<br> +447549902964<p>
<br> <p><img src="asset/img/logo-xmpp.png" class="logo-small" width="40px" height="40px"/> XMPP<br>
inference@inferencium.net (Main) - <br>
(<a href="key.html#xmpp-inferencium">Key</a>)<br> inference@inferencium.net (Main) -
<br> (<a href="key.html#xmpp-inferencium">Key</a>)<br>
inference@notyour.chat (Backup) - <br>
(<a href="key.html#xmpp-notyourchat">Key</a>)</p> inference@notyour.chat (Backup) -
<!-- (<a href="key.html#xmpp-notyourchat">Key</a>)</p>
<h3 id="e2ee-metadatafree"><a href="#e2ee-metadatafree">Metadata-free</a></h3> </section>
<p>If metadata leakage is an issue for you, you can use the following <!--
contact methods.<br> <h3 id="e2ee-metadatafree"><a href="#e2ee-metadatafree">Metadata-free</a></h3>
<br> <p>If metadata leakage is an issue for you, you can use the
Note: These services do not have verification functionality and will be following contact methods.<br>
treated as less secure; <strong>unless you really need to use these <br>
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>
<!-- <!--
<section id="non_private"> <section id="non_private">