Inferencium/website
1
0
Fork 0
Code Issues Activity

Add HTML sections.

Browse Source
This commit is contained in:
inference 2023-06-12 13:45:11 +01:00
parent ffbb14211d
commit 2d83468ee2
Signed by: inference
SSH Key Fingerprint: SHA256:9Pl0nZ2UJacgm+IeEtLSZ4FOESgP1eKCtRflfPfdX9M
1 changed files with 81 additions and 73 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

154
contact.html
View File

@ -5,7 +5,7 @@
<!-- Copyright 2022 Jake Winters -->
<!-- SPDX-License-Identifier: BSD-3-Clause -->
<!-- Version: 5.2.0.38 -->
<!-- Version: 5.2.0.39 -->
<html>
@ -30,77 +30,85 @@
</div>
<body>
<h1>Contact</h1>
<!-- Table of contents -->
<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>
<ul>
<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>
<!-- Place end-to-end encrypted contact methods here -->
<!-- Contacts should be encouraged to use these contact methods -->
<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>
<li>I have phased out usage of email, including TLS-encrypted email</li>
</ul>
<h2 id="e2ee"><a href="#e2ee" class="h2"
>End-to-end Encrypted Contact Methods</a></h2>
<br>
<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>
Note: Verification does not verify a person, only their devices, 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>
<br>
+447549902964<p><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>
<br>
<br>
<!-- 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>
<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>
<br>
<p><img src="asset/img/logo-briar.png" class="logo-small"
width="40px" height="40px"/> Briar<br>
<br>
Unavailable</p><br>
<!-- Place non-private contact methods here -->
<!-- Clarify that these contact methods are for public contact only -->
<!--<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>
<!-- Table of contents -->
<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>
<ul>
<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>
<!-- Place end-to-end encrypted contact methods here -->
<!-- Contacts should be encouraged to use these contact methods -->
<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>
<li>I have phased out usage of email, including TLS-encrypted email</li>
</ul>
</section>
<section>
<h2 id="e2ee"><a href="#e2ee" class="h2"
>End-to-end Encrypted Contact Methods</a></h2>
<br>
<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>
Note: Verification does not verify a person, only their devices, 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>
<br>
+447549902964<p><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>
<br>
<br>
<!-- 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>
<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>
<br>
<p><img src="asset/img/logo-briar.png" class="logo-small"
width="40px" height="40px"/> Briar<br>
<br>
Unavailable</p><br>
</section>
<!--<section>
Place non-private contact methods here -->
<!-- Clarify that these contact methods are for public contact only -->
<!--<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>-->
</body>
</html>