Update Contact webpage from version 5.3.0.45 to 5.4.0.48
This commit is contained in:
parent
04134752ff
commit
d3f35dd446
47
contact.html
47
contact.html
@ -5,7 +5,7 @@
|
||||
<!-- Copyright 2022 Jake Winters -->
|
||||
<!-- SPDX-License-Identifier: BSD-3-Clause -->
|
||||
|
||||
<!-- Version: 5.3.0.45 -->
|
||||
<!-- Version: 5.4.0.48 -->
|
||||
|
||||
|
||||
<html>
|
||||
@ -31,25 +31,19 @@
|
||||
<h1>Contact</h1>
|
||||
<section id="toc">
|
||||
<!-- Table of contents -->
|
||||
<h2 id="toc"><a href="#toc" class="h2"
|
||||
>Table of Contents<a/></h2>
|
||||
<h2 id="toc"><a href="#toc" class="h2">Table of Contents<a/></h2>
|
||||
<ul>
|
||||
<li><a href="#notes" class="body-link"
|
||||
>Notes</a></li>
|
||||
<li><a href="#e2ee" class="body-link"
|
||||
>End-to-end encrypted contact methods</a></li>
|
||||
<li><a href="#notes" class="body-link">Notes</a></li>
|
||||
<li><a href="#e2ee" class="body-link">End-to-end encrypted contact methods</a></li>
|
||||
<ul>
|
||||
<li><a href="#e2ee-pref" class="body-link"
|
||||
>Preferred</a></li>
|
||||
<li><a href="#e2ee-metadata" class="body-link"
|
||||
>Metadata-free</a></li>
|
||||
<li><a href="#e2ee-pref" class="body-link">Preferred</a></li>
|
||||
<li><a href="#e2ee-metadata" class="body-link">Metadata-free</a></li>
|
||||
</ul>
|
||||
<!--<li><a href="#non-private" class="body-link">Non-private Contact Methods</a></li>-->
|
||||
</ul>
|
||||
</section>
|
||||
<section id="notes">
|
||||
<h2 id="notes"><a href="#notes" class="h2"
|
||||
>Notes</a></h2>
|
||||
<h2 id="notes"><a href="#notes" class="h2">Notes</a></h2>
|
||||
<ul>
|
||||
<li>I have phased out usage of obsolete, insecure PGP for all contact
|
||||
methods</li>
|
||||
@ -57,42 +51,37 @@
|
||||
</ul>
|
||||
</section>
|
||||
<section id="e2ee">
|
||||
<h2 id="e2ee"><a href="#e2ee" class="h2"
|
||||
>End-to-end Encrypted Contact Methods</a></h2>
|
||||
<h2 id="e2ee"><a href="#e2ee" class="h2">End-to-end Encrypted Contact Methods</a></h2>
|
||||
<!-- Place end-to-end encrypted contact methods here -->
|
||||
<!-- Contacts should be encouraged to use these contact methods -->
|
||||
<h3 id="e2ee-pref"><a href="#e2ee-pref" class="h3"
|
||||
>Preferred</a></h3>
|
||||
<h3 id="e2ee-pref"><a href="#e2ee-pref" class="h3">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>
|
||||
<br>
|
||||
<p><strong>Use the
|
||||
<a href="key.html" class="body-link"
|
||||
>keys</a> for each contact method to verify my devices.</strong><br>
|
||||
<a href="key.html" class="body-link">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>
|
||||
<p><img src="asset/img/logo-signal.png" class="logo-small" width="40px" height="40px"/> Signal<br>
|
||||
<br>
|
||||
+447549902964<p><br>
|
||||
<p><img src="asset/img/logo-xmpp.png" class="logo-small"
|
||||
width="40px" height="40px"/> XMPP<br>
|
||||
<p><img src="asset/img/logo-xmpp.png" class="logo-small" width="40px" height="40px"/> XMPP<br>
|
||||
<br>
|
||||
inference@inferencium.net
|
||||
(<a href="key/xmpp.html" class="body-link"
|
||||
>Key</a>)<p>
|
||||
(<a href="key.html#xmpp-inferencium" class="body-link">Key</a>)<br>
|
||||
<br>
|
||||
inference@notyour.chat
|
||||
(<a href="key.html#xmpp-notyourchat" class="body-link">Key</a>)</p>
|
||||
<!-- Place metadata-free contact methods here -->
|
||||
<!-- Clarify that preferred methods should be used whenever possible -->
|
||||
<h3 id="e2ee-metadata"><a href="#e2ee-metadata" class="h3"
|
||||
>Metadata-free</a></h3>
|
||||
<h3 id="e2ee-metadata"><a href="#e2ee-metadata" class="h3">Metadata-free</a></h3>
|
||||
<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>
|
||||
<p><img src="asset/img/logo-briar.png" class="logo-small"
|
||||
width="40px" height="40px"/> Briar<br>
|
||||
<p><img src="asset/img/logo-briar.png" class="logo-small" width="40px" height="40px"/> Briar<br>
|
||||
<br>
|
||||
Unavailable</p><br>
|
||||
</section>
|
||||
|
Loading…
x
Reference in New Issue
Block a user