Inferencium/website
1
0
Fork 0
Code Issues Activity

feat(contact): remove metadata-free section

Browse Source 
It does not make much sense to have a metadata-free section along with
standard end-to-end-encrypted contact methods due to the varying designs
and threat models. Different configurations within the platforms and/or
apps can also add or remove metadata, so it should be left to the user
to configure that or simply avoid the platform/app if it's a part of
their threat model.
This commit is contained in:
inference 2025-06-25 18:27:52 +00:00
parent a2f0b1a33c
commit d4155305d7
Signed by: inference
SSH Key Fingerprint: SHA256:/O3c09/4f1lh4zrhFs2qvQEDda6dZbTwG9xEcj8OfWo
1 changed files with 24 additions and 39 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
contact.xhtml
View File

@ -1,7 +1,7 @@
<!DOCTYPE html> <!DOCTYPE html>
<!-- Inferencium - Website - Contact --> <!-- Inferencium - Website - Contact -->
<!-- Version: 10.2.0-alpha.1 --> <!-- Version: 10.2.0-alpha.2 -->
<!-- Copyright 2022 Jake Winters --> <!-- Copyright 2022 Jake Winters -->
<!-- SPDX-License-Identifier: BSD-3-Clause --> <!-- SPDX-License-Identifier: BSD-3-Clause -->
@ -35,17 +35,10 @@
<h2><a href="#toc">Table of Contents</a></h2> <h2><a href="#toc">Table of Contents</a></h2>
<ul> <ul>
<li><a href="#e2ee">End-to-end encrypted contact methods</a></li> <li><a href="#e2ee">End-to-end encrypted contact methods</a></li>
<ul>
<li><a href="#e2ee-preferred">Preferred</a></li>
<!--<li><a href="#e2ee-metadatafree">Metadata-free</a></li>-->
</ul>
<!--<li><a href="#non-private" class="body-link">Non-private Contact Methods</a></li>-->
</ul> </ul>
</nav> </nav>
<section id="e2ee"> <section id="e2ee">
<h2><a href="#e2ee">End-to-end Encrypted Contact Methods</a></h2> <h2><a href="#e2ee">End-to-end Encrypted Contact Methods</a></h2>
<section id="e2ee-preferred">
<h3><a href="#e2ee-preferred">Preferred</a></h3>
<p>Whenever possible, use the following contact methods; they allow verification to mitigate <p>Whenever possible, use the following contact methods; they allow verification to mitigate
man-in-the-middle attacks, have high security, and reasonable privacy.</p> man-in-the-middle attacks, have high security, and reasonable privacy.</p>
<p><strong>Use the <p><strong>Use the
@ -63,13 +56,6 @@
</ul> </ul>
</section> </section>
<!-- <!--
<section id="e2ee-metadatafree">
<h3><a href="#e2ee-metadatafree">Metadata-free</a></h3>
<p>If metadata leakage is an issue for you, you can use the following contact methods.</p>
<p>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 id="nonprivate"> <section id="nonprivate">
<h2><a href="#nonprivate" class="h2">Non-private Contact Methods</a></h2> <h2><a href="#nonprivate" 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 <p>The following contact methods do not utilise end-to-end encryption, or I do not use
@ -77,7 +63,6 @@
groups. Do not use these methods if confidentiality and/or privacy is required.</p> groups. Do not use these methods if confidentiality and/or privacy is required.</p>
</section> </section>
--> -->
</section>
<div class="sitemap-small"><a href="sitemap.xhtml">Sitemap</a></div> <div class="sitemap-small"><a href="sitemap.xhtml">Sitemap</a></div>
</body> </body>
</html> </html>