Inferencium/website
1
0
Fork 0
Code Issues Activity

Update webpage "Blog - #2" from version "6.0.0" to "7.0.0"

Browse Source
This commit is contained in:
inference 2024-01-30 22:07:46 +00:00
parent dbf247d0bd
commit 35757d66dc
Signed by: inference
SSH Key Fingerprint: SHA256:FtEVfx1CmTKMy40VwZvF4k+3TC+QhCWy+EmPRg50Nnc
1 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

22
blog/untrusted_the_issue_with_decentralisation.xhtml
View File

@ -1,7 +1,7 @@
<!DOCTYPE html>
<!-- Inferencium - Website - Blog - #2 -->
<!-- Version: 6.0.0 -->
<!-- Version: 7.0.0 -->
<!-- Copyright 2022 Jake Winters -->
<!-- SPDX-License-Identifier: BSD-3-Clause -->
@ -16,23 +16,23 @@
</head>
<body>
<nav class="navbar">
<div><a href="../index.xhtml"><img src="../asset/img/logo-inferencium-no_text.png" width="110px" height="110px"/></a></div>
<div><a href="../index.xhtml"><img src="../asset/img/logo-inferencium-no_text.png" width="110" height="110" alt="Inferencium logo"/></a></div>
<div><a href="../index.xhtml" class="title">Inferencium</a></div>
<div><a href="../about.xhtml">About</a></div>
<div><a href="../contact.xhtml">Contact</a></div>
<div><a href="../blog.xhtml">Blog</a></div>
<div><a href="../documentation.xhtml">Documentation</a></div>
<div><a href="../source.xhtml">Source</a></div>
<div><a href="../key.xhtml">Key</a></div>
<div><a href="../changelog.xhtml">Changelog</a></div>
<div><a href="../blog.xhtml">Blog</a></div>
<div><a href="../contact.xhtml">Contact</a></div>
<div><a href="../directory.xhtml">Directory</a></div>
<div><a href="../key.xhtml">Key</a></div>
</nav>
<h1>Blog - #2</h1>
<h2>Untrusted: The Issue with Decentralisation</h2>
<p class="update_date">Posted: 2022-06-30 (UTC+00:00)</p>
<p class="update_date">Updated: 2023-11-11 (UTC+00:00)</p>
<nav id="toc">
<h2 id="toc"><a href="#toc">Table of Contents</a></h2>
<h2><a href="#toc">Table of Contents</a></h2>
<ul>
<li><a href="#introduction">Introduction</a></li>
<li><a href="#examples">Examples</a></li>
@ -44,7 +44,7 @@
</ul>
</nav>
<section id="introduction">
<h2 id="introduction"><a href="#introduction">Introduction</a></h2>
<h2><a href="#introduction">Introduction</a></h2>
<p>A recent trend is seeing people move towards decentralised services and
platforms. While this is reasonable and I can understand why they are doing such
a thing, they are seemingly doing it without thinking about the possible
@ -54,9 +54,9 @@
will discuss some of the security issues with the decentralised model.</p>
</section>
<section id="examples">
<h2 id="examples"><a href="#examples">Examples</a></h2>
<h2><a href="#examples">Examples</a></h2>
<section id="examples-messaging">
<h3 id="examples-messaging"><a href="#examples-messaging">Messaging</a></h3>
<h3><a href="#examples-messaging">Messaging</a></h3>
<p>When it comes to messaging your contacts on a centralised
platform, such as Twitter or Facebook, the keys are pinned to
that user account, using the user's password as the method of
@ -94,7 +94,7 @@
</section>
</section>
<section id="solution">
<h2 id="solution"><a href="#solution">Solution</a></h2>
<h2><a href="#solution">Solution</a></h2>
<p>I'll cut to the chase; there isn't a definitive solution. The best way to
handle this situation is to design your threat model and think about your
reasoning for avoiding centralised platforms. Is it lack of trust of a specific
@ -139,7 +139,7 @@
would make this impossible to implement in any form.</p>
</section>
<section id="conclusion">
<h2 id="conclusion"><a href="#conclusion">Conclusion</a></h2>
<h2><a href="#conclusion">Conclusion</a></h2>
<p>Do not demand anonymity; demand privacy and control of your own data.
Complete anonymity makes it impossible to have a root of trust, and is typically
never necessary. It is possible for someone else to hold your keys, without them