Inferencium/website
1
0
Fork 0
Code Issues Activity

Update Contact webpage to version 4.0.0.26.

Browse Source
This commit is contained in:
inference 2023-04-11 20:19:01 +01:00
parent 275611f49e
commit 3995e6045a
Signed by: inference
SSH Key Fingerprint: SHA256:9Pl0nZ2UJacgm+IeEtLSZ4FOESgP1eKCtRflfPfdX9M
1 changed files with 112 additions and 103 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

215
contact.html
View File

@ -2,118 +2,127 @@
<!-- Inferencium - Website - Contact -->
<!-- Copyright 2022-2023 Jake Winters -->
<!-- Copyright 2022 Jake Winters -->
<!-- SPDX-License-Identifier: BSD-3-Clause-Clear -->
<!-- Version: 3.0.0.19 -->
<!-- Version: 4.0.0.26 -->
<html>
<head>
<title>Inferencium - Contact</title>
<link rel="stylesheet" href="inf.css">
<meta name="viewport" content="width=device-width, initial-scale=1">
</head>
<head>
<title>Inferencium - Contact</title>
<link rel="stylesheet" href="inf.css">
<meta name="viewport" content="width=device-width, initial-scale=1">
</head>
<!-- Navigation bar. -->
<div class="sidebar">
<img src="asset/img/logo-inferencium-no_text.png"
width="110px" height="110px">
<a class="title">Inferencium</a><br>
<br>
<br>
<div><a href="about.html">About</a></div>
<div><a href="contact.html">Contact</a></div>
<div><a href="blog.html">Blog</a></div>
<div><a href="source.html">Source</a></div>
<div><a href="key.html">Key</a></div>
</div>
<!-- Navigation bar -->
<div class="sidebar">
<img src="asset/img/logo-inferencium-no_text.png"
width="110px" height="110px">
<a class="title">Inferencium</a><br>
<br>
<br>
<div><a href="about.html">About</a></div>
<div><a href="contact.html">Contact</a></div>
<div><a href="blog.html">Blog</a></div>
<div><a href="source.html">Source</a></div>
<div><a href="key.html">Key</a></div>
</div>
<body>
<h1>Contact</h1>
<br>
<br>
<br>
<body>
<h1>Contact</h1>
<br>
<br>
<br>
<!-- Table of contents. -->
<h2 id="toc"><a href="#toc" class="h2"
>Table of Contents<a/></h2>
<ul>
<li><a class="body-link" href="#e2ee"
>End-to-end encrypted contact methods</a></li>
<ul>
<li><a class="body-link" href="#e2ee-pref"
>Preferred</a></li>
<li><a class="body-link" href="#e2ee-metadata"
>Metadata-free</a></li>
</ul>
</ul>
<br>
<br>
<br>
<!-- 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>
</ul>
<br>
<br>
<br>
<!-- Place end-to-end encrypted contact methods here. -->
<!-- Contacts should be encouraged to use these contact methods. -->
<strong>Notes:</strong>
<p>- I have phased out usage of obsolete, insecure PGP for all contact methods.</p>
<p>- I have phased out usage of email, including TLS-encrypted email.</p>
<br>
<br>
<br>
<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 class="body-link" 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>
<br>
<p><img class="logo-small" src="asset/img/logo-signal.png"
width="40px" height="40px"/> Signal<br>
<br>
+447549902964<p><br>
<p><img class="logo-small" src="asset/img/logo-xmpp.png"
width="40px" height="40px"/> XMPP<br>
<br>
inference@inferencium.net
(<a class="body-link" href="key/xmpp.html"
>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</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 class="logo-small" src="asset/img/logo-briar.png"
width="40px" height="40px"/> Briar<br>
<br>
Unavailable</p><br>
<p><img class="logo-small" src="asset/img/logo-session.png"
width="40px" height="40px"/> Session<br>
<br>
Unavailable</p>
<br>
<br>
<!-- Place non-private contact methods here. -->
<!-- Clarify that these contact methods are for public contact only. -->
<!--<h2>Non-private Contact Methods</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>
<br>
<br>-->
</body>
<!-- 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>
<br>
<br>
<br>
<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>
<p><img src="asset/img/logo-session.png" class="logo-small"
width="40px" height="40px"/> Session<br>
<br>
Unavailable</p>
<br>
<br>
<!-- Place non-private contact methods here -->
<!-- Clarify that these contact methods are for public contact only -->
<!--<h2>Non-private Contact Methods</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>
<br>
<br>-->
</body>
</html>