Inferencium/website
1
0
Fork 0
Code Issues Activity

Update Contact webpage from version 5.1.0.35 to 5.2.0.40.

Browse Source
This commit is contained in:
inference 2023-06-12 15:01:33 +01:00
parent 638b170c20
commit 255e1e8fda
Signed by: inference
SSH Key Fingerprint: SHA256:9Pl0nZ2UJacgm+IeEtLSZ4FOESgP1eKCtRflfPfdX9M
1 changed files with 77 additions and 103 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

180
contact.html
View File

@ -5,17 +5,15 @@
<!-- Copyright 2022 Jake Winters --> <!-- Copyright 2022 Jake Winters -->
<!-- SPDX-License-Identifier: BSD-3-Clause --> <!-- SPDX-License-Identifier: BSD-3-Clause -->
<!-- Version: 5.1.0.35 --> <!-- Version: 5.2.0.40 -->
<html> <html>
<head> <head>
<title>Inferencium - Contact</title> <title>Inferencium - Contact</title>
<link rel="stylesheet" href="inf.css"> <link rel="stylesheet" href="inf.css">
<meta name="viewport" content="width=device-width, initial-scale=1"> <meta name="viewport" content="width=device-width, initial-scale=1">
</head> </head>
<!-- Navigation bar --> <!-- Navigation bar -->
<div class="sidebar"> <div class="sidebar">
<img src="asset/img/logo-inferencium-no_text.png" <img src="asset/img/logo-inferencium-no_text.png"
@ -30,107 +28,83 @@
<div><a href="key.html">Key</a></div> <div><a href="key.html">Key</a></div>
<div><a href="changelog.html">Changelog</a></div> <div><a href="changelog.html">Changelog</a></div>
</div> </div>
<body> <body>
<h1>Contact</h1> <h1>Contact</h1>
<br> <section>
<br> <!-- Table of contents -->
<br> <h2 id="toc"><a href="#toc" class="h2"
>Table of Contents<a/></h2>
<!-- Table of contents --> <ul>
<h2 id="toc"><a href="#toc" class="h2" <li><a href="#notes" class="body-link"
>Table of Contents<a/></h2> >Notes</a></li>
<ul> <li><a href="#e2ee" class="body-link"
<li><a href="#notes" class="body-link" >End-to-end encrypted contact methods</a></li>
>Notes</a></li> <ul>
<li><a href="#e2ee" class="body-link" <li><a href="#e2ee-pref" class="body-link"
>End-to-end encrypted contact methods</a></li> >Preferred</a></li>
<ul> <li><a href="#e2ee-metadata" class="body-link"
<li><a href="#e2ee-pref" class="body-link" >Metadata-free</a></li>
>Preferred</a></li> </ul>
<li><a href="#e2ee-metadata" class="body-link" <!--<li><a href="#non-private" class="body-link">Non-private Contact Methods</a></li>-->
>Metadata-free</a></li> </ul>
</ul> </section>
<li><a href="#non-private" class="body-link" <section>
>Non-private Contact Methods</a></li> <!-- Place end-to-end encrypted contact methods here -->
</ul> <!-- Contacts should be encouraged to use these contact methods -->
<br> <h2 id="notes"><a href="#notes" class="h2"
<br> >Notes</a></h2>
<br> <ul>
<li>I have phased out usage of obsolete, insecure PGP for all contact
<!-- Place end-to-end encrypted contact methods here --> methods</li>
<!-- Contacts should be encouraged to use these contact methods --> <li>I have phased out usage of email, including TLS-encrypted email</li>
<h2 id="notes"><a href="#notes" class="h2" </ul>
>Notes</a></h2> </section>
<ul> <section>
<li>I have phased out usage of obsolete, insecure PGP for all contact <h2 id="e2ee"><a href="#e2ee" class="h2"
methods</li> >End-to-end Encrypted Contact Methods</a></h2>
<li>I have phased out usage of email, including TLS-encrypted email</li> <br>
</ul> <h3 id="e2ee-pref"><a href="#e2ee-pref" class="h3"
<br> >Preferred</a></h3>
<br> <p>Whenever possible, use the following contact methods; they allow verification
<br> to mitigate man-in-the-middle attacks, have high security, and reasonable
privacy.<br>
<h2 id="e2ee"><a href="#e2ee" class="h2" <br>
>End-to-end Encrypted Contact Methods</a></h2> <p><strong>Use the
<br> <a href="key.html" class="body-link"
<h3 id="e2ee-pref"><a href="#e2ee-pref" class="h3" >keys</a> for each contact method to verify my devices.</strong><br>
>Preferred</a></h3> Note: Verification does not verify a person, only their devices, and can be
<p>Whenever possible, use the following contact methods; they allow verification defeated via coercion or other force.</p>
to mitigate man-in-the-middle attacks, have high security, and reasonable <p><img src="asset/img/logo-signal.png" class="logo-small"
privacy.<br> width="40px" height="40px"/> Signal<br>
<br> <br>
<p><strong>Use the +447549902964<p><br>
<a href="key.html" class="body-link" <p><img src="asset/img/logo-xmpp.png" class="logo-small"
>keys</a> for each contact method to verify my devices.</strong><br> width="40px" height="40px"/> XMPP<br>
Note: Verification does not verify a person, only their devices, and can be <br>
defeated via coercion or other force.</p> inference@inferencium.net
<br> (<a href="key/xmpp.html" class="body-link"
<p><img src="asset/img/logo-signal.png" class="logo-small" >Key</a>)<p>
width="40px" height="40px"/> Signal<br> <!-- Place metadata-free contact methods here -->
<br> <!-- Clarify that preferred methods should be used whenever possible -->
+447549902964<p><br> <h3 id="e2ee-metadata"><a href="#e2ee-metadata" class="h3"
<p><img src="asset/img/logo-xmpp.png" class="logo-small" >Metadata-free</a></h3>
width="40px" height="40px"/> XMPP<br> <p>If metadata leakage is an issue for you, you can use the following contact methods.<br>
<br> <br>
inference@inferencium.net Note: These services do not have verification functionality and will be treated
(<a href="key/xmpp.html" class="body-link" as less secure; <strong>unless you really need to use these services, use a
>Key</a>)<p> preferred method instead.</strong></p>
<br> <p><img src="asset/img/logo-briar.png" class="logo-small"
<br> width="40px" height="40px"/> Briar<br>
<!-- Place metadata-free contact methods here --> <br>
<!-- Clarify that preferred methods should be used whenever possible --> Unavailable</p><br>
<h3 id="e2ee-metadata"><a href="#e2ee-metadata" class="h3" </section>
>Metadata-free</a></h3> <!--<section>
<p>If metadata leakage is an issue for you, you can use the following contact methods.<br> Place non-private contact methods here -->
<br> <!-- Clarify that these contact methods are for public contact only -->
Note: These services do not have verification functionality and will be treated <!--<h2 id="non-private"><a href="#non-private" class="h2">Non-private Contact Methods</a></h2>
as less secure; <strong>unless you really need to use these services, use a <p>The following contact methods do not utilise end-to-end encryption, or I do not use
preferred method instead.</strong></p> such functionality; they are suitable for public contact only, including directly and
<br> groups. Do not use these methods if confidentiality and/or privacy is required.</p>
<p><img src="asset/img/logo-briar.png" class="logo-small" </section>-->
width="40px" height="40px"/> Briar<br>
<br>
Unavailable</p><br>
<br>
<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>
<br>
<p><img src="asset/img/logo-pleroma.png" class="logo-small"
width="40px" height="40px"/> Fediverse<br>
<br>
<a href="https://plm.inferencium.net/inference" class="body-link"
>@inference@plm.inferencium.net</a></p>
<br>
<br>
<br>
</body> </body>
</html> </html>