Remove unnecessary HTML line breaks.

This commit is contained in:
inference 2023-06-21 16:02:14 +01:00
parent 81f7aa6f41
commit ecbd50ff87
Signed by: inference
SSH Key Fingerprint: SHA256:9Pl0nZ2UJacgm+IeEtLSZ4FOESgP1eKCtRflfPfdX9M

View File

@ -5,7 +5,7 @@
<!-- Copyright 2022 Jake Winters -->
<!-- SPDX-License-Identifier: BSD-3-Clause -->
<!-- Version: 4.1.0.22 -->
<!-- Version: 4.1.0.23 -->
<html>
@ -28,15 +28,9 @@
</div>
<body>
<h1>Blog - #0</h1>
<br>
<br>
<br>
<h2>FOSS is Working Against Itself</h2>
<br>
<p class="update_date">Posted: 2022-01-27 (UTC+00:00)</p>
<p class="update_date">Updated: 2022-11-09 (UTC+00:00)</p>
<br>
<br>
<!-- Table of contents -->
<h2 id="toc"><a href="#toc" class="h2"
>Table of Contents<a/></h2>
@ -54,15 +48,12 @@
<li><a href="#conclusion" class="body-link"
>Conclusion</a></li>
</ul>
<br>
<br>
<h2 id=introduction"><a href="#introduction" class="h2"
>Introduction</a></h2>
<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 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>
<br>
<p>The
<a class="body-link" href="https://en.wikipedia.org/wiki/Free_software"
>FOSS</a> movement is an attempt to regain
@ -79,7 +70,6 @@
and allows us to protect ourselves. Without security, we have no protection, and without protection,
we have a lack of certainty of everything else, including privacy and control, which is what the
FOSS movement is seeking.</p>
<br>
<p>FOSS projects rarely take security into account; they simply look at the surface level, rather
than the actual
<a class="body-link" href="https://en.wikipedia.org/wiki/Root_cause_analysis"
@ -90,8 +80,6 @@
<a class="body-link" href="https://en.wikipedia.org/wiki/Ideology"
>ideology</a>, 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>
<br>
<br>
<h2 id="examples"><a href="#examples" class="h2"
>Examples</a></h2>
<h3 id="examples-smartphones"><a href="#examples-smartphones" class="h3"
@ -125,11 +113,9 @@
<a class="body-link" 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
they proclaim to be.</p>
<br>
<p>You may ask "What's so bad about using
<a class="body-link" href="https://lineageos.org/"
>LineageOS</a>?", to which I answer with "What's not bad about it?".<br>
<br>
<ul>
<li>LineageOS uses
<a class="body-link" href="https://github.com/LineageOS/hudson/blob/master/lineage-build-targets"
@ -149,13 +135,10 @@
<a class="body-link" href="https://en.wikipedia.org/wiki/Vulnerability_(computing)"
>security vulnerabilities</a>.</li>
</ul>
<br>
<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
customisation abilities, and a backdoor to your data. They are best suited as a development OS, not
a production OS.</p>
<br>
<br>
<h2 id="solution"><a href="#solution" class="h2">Solution</a></h2>
<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
@ -166,7 +149,6 @@
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
use it tactically.</p>
<br>
<p>The only solution for phone security, privacy, and control, is to use a Google Pixel (currently,
Pixel 4a-series or newer) running
<a class="body-link" href="https://grapheneos.org/"
@ -184,12 +166,8 @@
years for Pixel 6-series and newer), and
<a class="body-link" href="https://source.android.com/docs/security/bulletin/pixel/"
>guaranteed monthly security updates</a> for the entire support timeframe of the devices.</p>
<br>
<br>
<h2 id="conclusion"><a href="#conclusion" class="h2">Conclusion</a></h2>
<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>
<br>
<br>
</body>
</html>