Inferencium/website
1
0
Fork 0
Code Issues Activity

Remove redundant CSS classes

Browse Source
This commit is contained in:
inference 2023-09-02 14:22:13 +01:00
parent f2912f22cd
commit 3e59bcc90d
Signed by: inference
SSH Key Fingerprint: SHA256:FtEVfx1CmTKMy40VwZvF4k+3TC+QhCWy+EmPRg50Nnc
4 changed files with 72 additions and 72 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

74
blog/foss_is_working_against_itself.html
View File

@ -5,7 +5,7 @@
<!-- Copyright 2022 Jake Winters --> <!-- Copyright 2022 Jake Winters -->
<!-- SPDX-License-Identifier: BSD-3-Clause --> <!-- SPDX-License-Identifier: BSD-3-Clause -->
<!-- Version: 4.1.1.28 --> <!-- Version: 4.2.0.29 -->
<html> <html>
@ -35,33 +35,33 @@
<p class="update_date">Updated: 2022-11-09 (UTC+00:00)</p> <p class="update_date">Updated: 2022-11-09 (UTC+00:00)</p>
<!-- Table of contents --> <!-- Table of contents -->
<section id="toc"> <section id="toc">
<h2 id="toc"><a href="#toc" class="h2">Table of Contents<a/></h2> <h2 id="toc"><a href="#toc">Table of Contents<a/></h2>
<ul> <ul>
<li><a href="#introduction" class="body-link">Introduction</a></li> <li><a href="#introduction">Introduction</a></li>
<li><a href="#examples" class="body-link">Examples</a></li> <li><a href="#examples">Examples</a></li>
<ul> <ul>
<li><a href="#examples-smartphones" class="body-link">Smartphones</a></li> <li><a href="#examples-smartphones">Smartphones</a></li>
</ul> </ul>
<li><a href="#solution" class="body-link">Solution</a></li> <li><a href="#solution">Solution</a></li>
<li><a href="#conclusion" class="body-link">Conclusion</a></li> <li><a href="#conclusion">Conclusion</a></li>
</ul> </ul>
</section> </section>
<section id="introduction"> <section id="introduction">
<h2 id=introduction"><a href="#introduction" class="h2">Introduction</a></h2> <h2 id=introduction"><a href="#introduction">Introduction</a></h2>
<p>The world has become a dangerous, privacy invading, human rights stripping, totalitarian place; <p>The world has become a dangerous, privacy invading, human rights stripping, totalitarian place;
in order to combat this, people are joining a growing, and dangerous, trend, which I will refer to in order to combat this, people are joining a growing, and dangerous, trend, which I will refer to
in this post as the "Free and Open Source (FOSS) movement". With that stated, I will now debunk the in this post as the "Free and Open Source (FOSS) movement". With that stated, I will now debunk the
misinformation being spread inside of this extremely flawed movement.</p> misinformation being spread inside of this extremely flawed movement.</p>
<p>The <p>The
<a href="https://en.wikipedia.org/wiki/Free_software" class="body-link">FOSS</a> <a href="https://en.wikipedia.org/wiki/Free_software">FOSS</a>
movement is an attempt to regain movement is an attempt to regain
<a href="https://en.wikipedia.org/wiki/Privacy" class="body-link">privacy</a> <a href="https://en.wikipedia.org/wiki/Privacy">privacy</a>
and and
<a href="https://en.wikipedia.org/wiki/Control_(psychology)" class="body-link">control</a> <a href="https://en.wikipedia.org/wiki/Control_(psychology)">control</a>
over our devices and data, but the entire concept of FOSS-only, at the current time, is over our devices and data, but the entire concept of FOSS-only, at the current time, is
severely, and dangerously, flawed. What the FOSS community does not seem to understand is the fact severely, and dangerously, flawed. What the FOSS community does not seem to understand is the fact
that most FOSS software cares not about that most FOSS software cares not about
<a href="https://en.wikipedia.org/wiki/Security" class="body-link">security</a>. <a href="https://en.wikipedia.org/wiki/Security">security</a>.
"Security"; keep that word in mind as you progress through this article. What is security? Security "Security"; keep that word in mind as you progress through this article. What is security? Security
is being safe and secure from adversaries and unwanted consequences; security protects our rights is being safe and secure from adversaries and unwanted consequences; security protects our rights
and allows us to protect ourselves. Without security, we have no protection, and without protection, and allows us to protect ourselves. Without security, we have no protection, and without protection,
@ -69,54 +69,54 @@
FOSS movement is seeking.</p> FOSS movement is seeking.</p>
<p>FOSS projects rarely take security into account; they simply look at the surface level, rather <p>FOSS projects rarely take security into account; they simply look at the surface level, rather
than the actual than the actual
<a href="https://en.wikipedia.org/wiki/Root_cause_analysis" class="body-link">root cause</a> <a href="https://en.wikipedia.org/wiki/Root_cause_analysis">root cause</a>
of the issues they are attempting to fight against. In this case, the focus is on of the issues they are attempting to fight against. In this case, the focus is on
privacy and control. Without security mechanisms to protect the privacy features and the ability to privacy and control. Without security mechanisms to protect the privacy features and the ability to
control your devices and data, it can be stripped away as if it never existed in the first place, control your devices and data, it can be stripped away as if it never existed in the first place,
which, inevitably, leads us back to the beginning, and the cycle repeats. With this which, inevitably, leads us back to the beginning, and the cycle repeats. With this
<a href="https://en.wikipedia.org/wiki/Ideology" class="body-link">ideology</a>, <a href="https://en.wikipedia.org/wiki/Ideology">ideology</a>,
privacy and control will *never* be achieved. There is no foundation to build privacy privacy and control will *never* be achieved. There is no foundation to build privacy
or control upon. It is impossible to build a solid, freedom respecting platform on this model.</p> or control upon. It is impossible to build a solid, freedom respecting platform on this model.</p>
</section> </section>
<section id="examples"> <section id="examples">
<h2 id="examples"><a href="#examples" class="h2">Examples</a></h2> <h2 id="examples"><a href="#examples">Examples</a></h2>
<section id="examples-smartphones"> <section id="examples-smartphones">
<h3 id="examples-smartphones"><a href="#examples-smartphones" class="h3">Smartphones</a></h3> <h3 id="examples-smartphones"><a href="#examples-smartphones">Smartphones</a></h3>
<p>A FOSS phone, especially so-called <p>A FOSS phone, especially so-called
<a href="https://en.wikipedia.org/wiki/Linux_for_mobile_devices#Smartphones" class="body-link">"Linux phones"</a> <a href="https://en.wikipedia.org/wiki/Linux_for_mobile_devices#Smartphones">"Linux phones"</a>
are completely are completely
detrimental to privacy and control, because they do not have the security necessary to enforce that detrimental to privacy and control, because they do not have the security necessary to enforce that
privacy. privacy.
<a href="https://en.wikipedia.org/wiki/Bootloader_unlocking" class="body-link">Unlocked bootloaders</a> <a href="https://en.wikipedia.org/wiki/Bootloader_unlocking">Unlocked bootloaders</a>
prevent the device from prevent the device from
<a href="https://source.android.com/docs/security/features/verifiedboot/" class="body-link">verifying the integrity of the boot chain</a>, <a href="https://source.android.com/docs/security/features/verifiedboot/">verifying the integrity of the boot chain</a>,
including the OS, meaning any adversary, whether a including the OS, meaning any adversary, whether a
stranger who happens to pick up the device, or a big tech or government entity, can simply inject stranger who happens to pick up the device, or a big tech or government entity, can simply inject
malicious code into your software and you wouldn't have any idea it was there. If that's not enough malicious code into your software and you wouldn't have any idea it was there. If that's not enough
of a backdoor for you to reconsider your position, how about the trivial of a backdoor for you to reconsider your position, how about the trivial
<a href="https://en.wikipedia.org/wiki/Evil_maid_attack" class="body-link">evil maid</a> <a href="https://en.wikipedia.org/wiki/Evil_maid_attack">evil maid</a>
and data extraction attacks which could be executed on your device, without coercion? and data extraction attacks which could be executed on your device, without coercion?
With Android phones, this is bad enough to completely break the privacy and control the FOSS With Android phones, this is bad enough to completely break the privacy and control the FOSS
movement seeks, but "Linux phones" take it a step further by implementing barely any security, if movement seeks, but "Linux phones" take it a step further by implementing barely any security, if
any at all. any at all.
<a href="https://en.wikipedia.org/wiki/Privilege_escalation" class="body-link">Privilege escalation</a> <a href="https://en.wikipedia.org/wiki/Privilege_escalation">Privilege escalation</a>
is trivial to achieve on any Linux system, which is the reason Linux is trivial to achieve on any Linux system, which is the reason Linux
<a href="https://en.wikipedia.org/wiki/Hardening_(computing)" class="body-link">hardening</a> <a href="https://en.wikipedia.org/wiki/Hardening_(computing)">hardening</a>
strategies often include restricting access to the root account; if you strategies often include restricting access to the root account; if you
<a href="https://en.wikipedia.org/wiki/Rooting_(Android)" class="body-link">root your Android phone</a>, <a href="https://en.wikipedia.org/wiki/Rooting_(Android)">root your Android phone</a>,
or use a "Linux phone", you've already destroyed the security model, or use a "Linux phone", you've already destroyed the security model,
and thus privacy and control model you were attempting to achieve. Not only are these side effects and thus privacy and control model you were attempting to achieve. Not only are these side effects
of FOSS, so is the absolutely illogical restriction of not being able to, or making it unnecessarily of FOSS, so is the absolutely illogical restriction of not being able to, or making it unnecessarily
difficult to, install and update critical components of the system, such as proprietary difficult to, install and update critical components of the system, such as proprietary
<a href="https://en.wikipedia.org/wiki/Firmware" class="body-link">firmware</a>, <a href="https://en.wikipedia.org/wiki/Firmware">firmware</a>,
which just so happens to be almost all of them. "Linux phones" are not as free as which just so happens to be almost all of them. "Linux phones" are not as free as
they proclaim to be.</p> they proclaim to be.</p>
<p>You may ask "What's so bad about using <p>You may ask "What's so bad about using
<a href="https://lineageos.org/" class="body-link">LineageOS</a>?", <a href="https://lineageos.org/">LineageOS</a>?",
to which I answer with "What's not bad about it?".</p> to which I answer with "What's not bad about it?".</p>
<ul> <ul>
<li>LineageOS uses <li>LineageOS uses
<a href="https://github.com/LineageOS/hudson/blob/master/lineage-build-targets" class="body-link">debug builds</a>, <a href="https://github.com/LineageOS/hudson/blob/master/lineage-build-targets">debug builds</a>,
not safe and secure release builds.</li> not safe and secure release builds.</li>
<li>LineageOS requires an unlocked bootloader. Even when installed on devices which support custom <li>LineageOS requires an unlocked bootloader. Even when installed on devices which support custom
Android Verified Boot (AVB) keys, the bootloader cannot be locked due to lack of the OS being Android Verified Boot (AVB) keys, the bootloader cannot be locked due to lack of the OS being
@ -125,11 +125,11 @@
to perform a second update to install this firmware; this likely causes users to ignore the to perform a second update to install this firmware; this likely causes users to ignore the
notification or miss firmware updates.</li> notification or miss firmware updates.</li>
<li>LineageOS does not implement <li>LineageOS does not implement
<a href="https://source.android.com/docs/security/features/verifiedboot/verified-boot#rollback-protection" class="body-link">rollback protection</a>, <a href="https://source.android.com/docs/security/features/verifiedboot/verified-boot#rollback-protection">rollback protection</a>,
meaning any adversary, from a stranger who physically picks up the device, meaning any adversary, from a stranger who physically picks up the device,
to a goverment entity remotely, can simply downgrade the OS to a previous version in order to to a goverment entity remotely, can simply downgrade the OS to a previous version in order to
exploit known exploit known
<a href="https://en.wikipedia.org/wiki/Vulnerability_(computing)" class="body-link">security vulnerabilities</a>.</li> <a href="https://en.wikipedia.org/wiki/Vulnerability_(computing)">security vulnerabilities</a>.</li>
</ul> </ul>
<p>LineageOS is not the only Android OS (commonly, and incorrectly, referred to as a "ROM") with such <p>LineageOS is not the only Android OS (commonly, and incorrectly, referred to as a "ROM") with such
issues, but it is one of the worst. The only things such insecure OSes can provide you are issues, but it is one of the worst. The only things such insecure OSes can provide you are
@ -138,34 +138,34 @@
</section> </section>
</section> </section>
<section id="solution"> <section id="solution">
<h2 id="solution"><a href="#solution" class="h2">Solution</a></h2> <h2 id="solution"><a href="#solution">Solution</a></h2>
<p>What can you do about this? The answer is simple; however, it does require you to use logic, <p>What can you do about this? The answer is simple; however, it does require you to use logic,
fact, and evidence, not emotion, which is a difficult pill for most people to swallow. Use your fact, and evidence, not emotion, which is a difficult pill for most people to swallow. Use your
adversaries' weapons against them. The only way to effectively combat the privacy invasion and lack adversaries' weapons against them. The only way to effectively combat the privacy invasion and lack
of control of our devices and data is to become a of control of our devices and data is to become a
<a href="https://en.wikipedia.org/wiki/Turncoat" class="body-link">renegade</a> <a href="https://en.wikipedia.org/wiki/Turncoat">renegade</a>
and not take sides. Yes, that means not taking sides with the closed source, and not take sides. Yes, that means not taking sides with the closed source,
proprietary, big tech and government entities, but it also means not taking sides with any proprietary, big tech and government entities, but it also means not taking sides with any
FOSS entities. The only way to win this war is to take *whatever* hardware and software you can, and FOSS entities. The only way to win this war is to take *whatever* hardware and software you can, and
use it tactically.</p> use it tactically.</p>
<p>The only solution for phone security, privacy, and control, is to use a Google Pixel (currently, <p>The only solution for phone security, privacy, and control, is to use a Google Pixel (currently,
Pixel 4a-series or newer) running Pixel 4a-series or newer) running
<a href="https://grapheneos.org/" class="body-link">GrapheneOS</a>. <a href="https://grapheneos.org/">GrapheneOS</a>.
Google Pixel phones allow you complete bootloader freedom, including the Google Pixel phones allow you complete bootloader freedom, including the
<a href="https://android.googlesource.com/platform/external/avb/+/master/README.md#pixel-2-and-later" class="body-link">ability to lock the bootloader after flashing a custom OS</a> <a href="https://android.googlesource.com/platform/external/avb/+/master/README.md#pixel-2-and-later">ability to lock the bootloader after flashing a custom OS</a>
(GrapheneOS includes a custom OS signing key to allow locking the bootloader and enabling verified (GrapheneOS includes a custom OS signing key to allow locking the bootloader and enabling verified
boot to prevent boot to prevent
<a href="https://en.wikipedia.org/wiki/Malware" class="body-link">malware</a> <a href="https://en.wikipedia.org/wiki/Malware">malware</a>
persistence, evil maid attacks, and boot chain persistence, evil maid attacks, and boot chain
<a href="https://en.wikipedia.org/wiki/Data_corruption" class="body-link">corruption</a>), <a href="https://en.wikipedia.org/wiki/Data_corruption">corruption</a>),
<a href="https://support.google.com/nexus/answer/4457705" class="body-link">long device support lifecycles</a> <a href="https://support.google.com/nexus/answer/4457705">long device support lifecycles</a>
(minimum 3 years for Pixel 4a-series to Pixel 5a, minimum 5 (minimum 3 years for Pixel 4a-series to Pixel 5a, minimum 5
years for Pixel 6-series and newer), and years for Pixel 6-series and newer), and
<a href="https://source.android.com/docs/security/bulletin/pixel/" class="body-link">guaranteed monthly security updates</a> <a href="https://source.android.com/docs/security/bulletin/pixel/">guaranteed monthly security updates</a>
for the entire support timeframe of the devices.</p> for the entire support timeframe of the devices.</p>
</section> </section>
<section id="conclusion"> <section id="conclusion">
<h2 id="conclusion"><a href="#conclusion" class="h2">Conclusion</a></h2> <h2 id="conclusion"><a href="#conclusion">Conclusion</a></h2>
<p>Use what you can, and do what you can. By neglecting security, you are, even if unintentionally, <p>Use what you can, and do what you can. By neglecting security, you are, even if unintentionally,
neglecting exactly what you are trying to gain; privacy and control.</p> neglecting exactly what you are trying to gain; privacy and control.</p>
</section> </section>

28
blog/systemd_insecurity.html
View File

@ -5,7 +5,7 @@
<!-- Copyright 2022 Jake Winters --> <!-- Copyright 2022 Jake Winters -->
<!-- SPDX-License-Identifier: BSD-3-Clause --> <!-- SPDX-License-Identifier: BSD-3-Clause -->
<!-- Version: 4.1.1.25 --> <!-- Version: 4.2.0.26 -->
<html> <html>
@ -34,28 +34,28 @@
<p class="update_date">Updated: 2022-11-14 (UTC+00:00)</p> <p class="update_date">Updated: 2022-11-14 (UTC+00:00)</p>
<!-- Table of contents --> <!-- Table of contents -->
<section id="toc"> <section id="toc">
<h2 id="toc"><a href="#toc" class="h2">Table of Contents<a/></h2> <h2 id="toc"><a href="#toc">Table of Contents<a/></h2>
<ul> <ul>
<li><a href="#issue0" class="body-link">Issue #0 - Against CVE Assignment</a></li> <li><a href="#issue0">Issue #0 - Against CVE Assignment</a></li>
<li><a href="#issue1" class="body-link">Issue #1 - CVEs Are Not Useful</a></li> <li><a href="#issue1">Issue #1 - CVEs Are Not Useful</a></li>
<li><a href="#issue2" class="body-link">Issue #2 - Security is a Circus</a></li> <li><a href="#issue2">Issue #2 - Security is a Circus</a></li>
<li><a href="#issue3" class="body-link">Issue #3 - Blaming the User</a></li> <li><a href="#issue3">Issue #3 - Blaming the User</a></li>
</ul> </ul>
</section> </section>
<p>Anyone who cares about security may want to switch from systemd as soon as possible; its lead <p>Anyone who cares about security may want to switch from systemd as soon as possible; its lead
developer doesn't care about your security at all.</p> developer doesn't care about your security at all.</p>
<section id="issue0"> <section id="issue0">
<h2 id="issue0"><a href="#issue0" class="h2">Issue #0 - Against CVE Assignment</a></h2> <h2 id="issue0"><a href="#issue0">Issue #0 - Against CVE Assignment</a></h2>
<br> <br>
<blockquote>"You don't assign CVEs to every single random bugfix we do, do you?"</blockquote> <blockquote>"You don't assign CVEs to every single random bugfix we do, do you?"</blockquote>
<p>- Lennart Poettering, systemd lead developer</p> <p>- Lennart Poettering, systemd lead developer</p>
<p>My thoughts:<br> <p>My thoughts:<br>
Yes, if they're security-related.</p> Yes, if they're security-related.</p>
<p>Source:<br> <p>Source:<br>
<a href="https://github.com/systemd/systemd/pull/5998#issuecomment-303782334" class="body-link">systemd GitHub Issue 5998</a></p> <a href="https://github.com/systemd/systemd/pull/5998#issuecomment-303782334">systemd GitHub Issue 5998</a></p>
</section> </section>
<section id="issue1"> <section id="issue1">
<h2 id="issue1"><a href="#issue1" class="h2">Issue #1 - CVEs Are Not Useful</a></h2> <h2 id="issue1"><a href="#issue1">Issue #1 - CVEs Are Not Useful</a></h2>
<blockquote>"Humpf, I am not convinced this is the right way to announce this. We never did that, and half the <blockquote>"Humpf, I am not convinced this is the right way to announce this. We never did that, and half the
CVEs aren't useful anyway, hence I am not sure we should start with that now, because it is either CVEs aren't useful anyway, hence I am not sure we should start with that now, because it is either
inherently incomplete or blesses the nonsensical part of the CVE circus which we really shouldn't inherently incomplete or blesses the nonsensical part of the CVE circus which we really shouldn't
@ -66,18 +66,18 @@
it *is* the correct way to announce it. It seems as if over 95 security-concious people think the it *is* the correct way to announce it. It seems as if over 95 security-concious people think the
same.</p> same.</p>
<p>Source:<br> <p>Source:<br>
<a href="https://github.com/systemd/systemd/pull/6225#issuecomment-311739869" class="body-link">systemd GitHub Issue 6225</a></p> <a href="https://github.com/systemd/systemd/pull/6225#issuecomment-311739869">systemd GitHub Issue 6225</a></p>
</section> </section>
<section id="issue2"> <section id="issue2">
<h2 id="issue2"><a href="#issue2" class="h2">Issue #2 - Security is a Circus</a></h2> <h2 id="issue2"><a href="#issue2">Issue #2 - Security is a Circus</a></h2>
<blockquote>"I am not sure I buy enough into the security circus to do that though for any minor <blockquote>"I am not sure I buy enough into the security circus to do that though for any minor
issue..."</blockquote> issue..."</blockquote>
<p>- Lennart Poettering, systemd lead developer</p> <p>- Lennart Poettering, systemd lead developer</p>
<p>Source:<br> <p>Source:<br>
<a href="https://github.com/systemd/systemd/issues/5144#issuecomment-276740654" class="body-link">systemd GitHub Issue 5144</a></p> <a href="https://github.com/systemd/systemd/issues/5144#issuecomment-276740654">systemd GitHub Issue 5144</a></p>
</section> </section>
<section id="issue3"> <section id="issue3">
<h2 id="issue3"><a href="#issue3" class="h2">Issue #3 - Blaming the User</a></h2> <h2 id="issue3"><a href="#issue3">Issue #3 - Blaming the User</a></h2>
<blockquote>"Yes, as you found out "0day" is not a valid username. I wonder which tool permitted you to create <blockquote>"Yes, as you found out "0day" is not a valid username. I wonder which tool permitted you to create
it in the first place. Note that not permitting numeric first characters is done on purpose: to it in the first place. Note that not permitting numeric first characters is done on purpose: to
avoid ambiguities between numeric UID and textual user names. avoid ambiguities between numeric UID and textual user names.
@ -93,7 +93,7 @@
systemd was the thing that allowed root access just because a username started with a number, then systemd was the thing that allowed root access just because a username started with a number, then
Poettering blamed the user.</p> Poettering blamed the user.</p>
<p>Source:<br> <p>Source:<br>
<a href="https://github.com/systemd/systemd/issues/6237#issuecomment-311900864" class="body-link">systemd GitHub Issue 6237</a></p> <a href="https://github.com/systemd/systemd/issues/6237#issuecomment-311900864">systemd GitHub Issue 6237</a></p>
</section> </section>
</body> </body>
</html> </html>

18
blog/the_chromium_monopoly.html
View File

@ -5,7 +5,7 @@
<!-- Copyright 2022 Jake Winters --> <!-- Copyright 2022 Jake Winters -->
<!-- SPDX-License-Identifier: BSD-3-Clause --> <!-- SPDX-License-Identifier: BSD-3-Clause -->
<!-- Version: 4.1.0.21 --> <!-- Version: 4.2.0.22 -->
<html> <html>
@ -34,15 +34,15 @@
<p class="update_date">Updated: 2022-12-20 (UTC+00:00)</p> <p class="update_date">Updated: 2022-12-20 (UTC+00:00)</p>
<!-- Table of contents --> <!-- Table of contents -->
<section id="toc"> <section id="toc">
<h2 id="toc"><a href="#toc" class="h2">Table of Contents<a/></h2> <h2 id="toc"><a href="#toc">Table of Contents<a/></h2>
<ul> <ul>
<li><a href="#introduction" class="body-link">Introduction</a></li> <li><a href="#introduction">Introduction</a></li>
<li><a href="#solution" class="body-link">Solution</a></li> <li><a href="#solution">Solution</a></li>
<li><a href="#conclusion" class="body-link">Conclusion</a></li> <li><a href="#conclusion">Conclusion</a></li>
</ul> </ul>
</section> </section>
<section id="introduction"> <section id="introduction">
<h2 id="introduction"><a href="#introduction" class="h2">Introduction</a></h2> <h2 id="introduction"><a href="#introduction">Introduction</a></h2>
<p>It's no secret that I'm an advocate of Chromium and will use it for the foreseeable future. It is <p>It's no secret that I'm an advocate of Chromium and will use it for the foreseeable future. It is
a highly secure web browser which provides strong protection against malicious wesbites and the code a highly secure web browser which provides strong protection against malicious wesbites and the code
they run, and, while I am not too interested in high performance, it is a very performant web they run, and, while I am not too interested in high performance, it is a very performant web
@ -50,7 +50,7 @@
<p>However, the intention of this blog post is not to promote Chromium for any reason, but rather show <p>However, the intention of this blog post is not to promote Chromium for any reason, but rather show
an issue with it; an issue which is larger than may be realised by web-surfing users. That issue is an issue with it; an issue which is larger than may be realised by web-surfing users. That issue is
the large monopoly Chromium has in the web browser market; the large monopoly Chromium has in the web browser market;
<a href="https://en.wikipedia.org/wiki/Usage_share_of_web_browsers#Summary_tables" class="body-link">Chromium's market share is around 65%</a>, <a href="https://en.wikipedia.org/wiki/Usage_share_of_web_browsers#Summary_tables">Chromium's market share is around 65%</a>,
making it the largest slice of the cake. The issue becomes even deeper and more problematic when you making it the largest slice of the cake. The issue becomes even deeper and more problematic when you
realise that the second-place web browser, Safari, has only an 18% market share.</p> realise that the second-place web browser, Safari, has only an 18% market share.</p>
<p>The main issue with this type of monopoly is the large amounts of power and influence it gives <p>The main issue with this type of monopoly is the large amounts of power and influence it gives
@ -59,7 +59,7 @@
a fully working web.</p> a fully working web.</p>
</section> </section>
<section id="solution"> <section id="solution">
<h2 id="solution"><a href="#solution" class="h2">Solution</a></h2> <h2 id="solution"><a href="#solution">Solution</a></h2>
<p>In order to combat the Chromium monopoly, users typically go over to Chromium's classical rival, <p>In order to combat the Chromium monopoly, users typically go over to Chromium's classical rival,
Firefox. However, Firefox is dying and has lost almost all of its userbase over the last 2-3 years; Firefox. However, Firefox is dying and has lost almost all of its userbase over the last 2-3 years;
the reason for this is a tale of selfishness and greed, caused by Firefox's parent company to go off the reason for this is a tale of selfishness and greed, caused by Firefox's parent company to go off
@ -88,7 +88,7 @@
we must be tactical, not emotional.</p> we must be tactical, not emotional.</p>
</section> </section>
<section id="conclusion"> <section id="conclusion">
<h2 id="conclusion"><a href="#conclusion" class="h2">Conclusion</a></h2> <h2 id="conclusion"><a href="#conclusion">Conclusion</a></h2>
<p>Supporting Safari is the first step in supporting WebKit and promoting usage of the independent <p>Supporting Safari is the first step in supporting WebKit and promoting usage of the independent
web engine. Buying time while supporting and contributing to WebKit browser projects is the best and web engine. Buying time while supporting and contributing to WebKit browser projects is the best and
only chance anyone has at competing with Chromium, and preventing it from increasing its dominance only chance anyone has at competing with Chromium, and preventing it from increasing its dominance

24
blog/untrusted_the_issue_with_decentralisation.html
View File

@ -5,7 +5,7 @@
<!-- Copyright 2022 Jake Winters --> <!-- Copyright 2022 Jake Winters -->
<!-- SPDX-License-Identifier: BSD-3-Clause --> <!-- SPDX-License-Identifier: BSD-3-Clause -->
<!-- Version: 4.1.1.24 --> <!-- Version: 4.2.0.25 -->
<html> <html>
@ -34,19 +34,19 @@
<p class="update_date">Updated: 2022-10-29 (UTC+00:00)</p> <p class="update_date">Updated: 2022-10-29 (UTC+00:00)</p>
<!-- Table of contents --> <!-- Table of contents -->
<section id="toc"> <section id="toc">
<h2 id="toc"><a href="#toc" class="h2">Table of Contents<a/></h2> <h2 id="toc"><a href="#toc">Table of Contents<a/></h2>
<ul> <ul>
<li><a href="#introduction" class="body-link">Introduction</a></li> <li><a href="#introduction">Introduction</a></li>
<li><a href="#examples" class="body-link">Examples</a></li> <li><a href="#examples">Examples</a></li>
<ul> <ul>
<li><a href="#examples-messaging" class="body-link">Messaging</a></li> <li><a href="#examples-messaging">Messaging</a></li>
</ul> </ul>
<li><a href="#solution" class="body-link">Solution</a></li> <li><a href="#solution">Solution</a></li>
<li><a href="#conclusion" class="body-link">Conclusion</a></li> <li><a href="#conclusion">Conclusion</a></li>
</ul> </ul>
</section> </section>
<section id="introduction"> <section id="introduction">
<h2 id="introduction"><a href="#introduction" class="h2">Introduction</a></h2> <h2 id="introduction"><a href="#introduction">Introduction</a></h2>
<p>A recent trend is seeing people move towards decentralised services and platforms. While this is <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 reasonable and I can understand why they are doing such a thing, they are seemingly doing it without
thinking about the possible consequences of doing so. The issue with decentralisation is trust; thinking about the possible consequences of doing so. The issue with decentralisation is trust;
@ -55,9 +55,9 @@
security issues with the decentralised model.</p> security issues with the decentralised model.</p>
</section> </section>
<section id="examples"> <section id="examples">
<h2 id="examples"><a href="#examples" class="h2">Examples</a></h2> <h2 id="examples"><a href="#examples">Examples</a></h2>
<section id="examples-messaging"> <section id="examples-messaging">
<h3 id="examples-messaging"><a href="#examples-messaging" class="h3">Messaging</a></h3> <h3 id="examples-messaging"><a href="#examples-messaging">Messaging</a></h3>
<p>When it comes to messaging your contacts on a centralised platform, such as Twitter or Facebook, <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 identification. the keys are pinned to that user account, using the user's password as the method of identification.
This approach makes it impossible to log in as a specific user without their password, should it be This approach makes it impossible to log in as a specific user without their password, should it be
@ -82,7 +82,7 @@
</section> </section>
</section> </section>
<section id="solution"> <section id="solution">
<h2 id="solution"><a href="#solution" class="h2">Solution</a></h2> <h2 id="solution"><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 <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 is to design your threat model and think about your reasoning for avoiding centralised platforms. Is
it lack of trust of a specific company? Is it the possibility of centralised platforms going it lack of trust of a specific company? Is it the possibility of centralised platforms going
@ -118,7 +118,7 @@
form, decentralisation would make this impossible to implement in any form.</p> form, decentralisation would make this impossible to implement in any form.</p>
</section> </section>
<section id="conclusion"> <section id="conclusion">
<h2 id="conclusion"><a href="#conclusion" class="h2">Conclusion</a></h2> <h2 id="conclusion"><a href="#conclusion">Conclusion</a></h2>
<p>Do not demand anonymity; demand privacy and control of your own data. Complete anonymity makes it <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 impossible to have a root of trust, and is typically never necessary. It is possible for someone
else to hold your keys, without them taking control of them and dictating what you can and cannot do else to hold your keys, without them taking control of them and dictating what you can and cannot do