Inferencium/website
1
0
Fork 0
Code Issues Activity

Update webpage "About" from version "10.1.0-beta.1" to "10.2.0-beta.1"

Browse Source
This commit is contained in:
inference 2024-03-24 10:09:35 +00:00
parent 4b3b477ad7
commit 8d7135159d
Signed by: inference
SSH Key Fingerprint: SHA256:FtEVfx1CmTKMy40VwZvF4k+3TC+QhCWy+EmPRg50Nnc
1 changed files with 170 additions and 78 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

248
about.xhtml
View File

@ -1,7 +1,7 @@
<!DOCTYPE html>
<!-- Inferencium - Website - About -->
<!-- Version: 10.1.0-beta.1 -->
<!-- Version: 10.2.0-beta.1 -->
<!-- Copyright 2022 Jake Winters -->
<!-- SPDX-License-Identifier: BSD-3-Clause -->
@ -179,7 +179,7 @@
<h2><a href="#licensing">Licensing</a></h2>
<p>I care about upstreaming and sharing code, strongly preferring licenses which have high license
compatibility in order to permit sharing code with as many other projects as possible; for this
reason, permissive licenses are mypreferred choice, while avoiding copyleft licenses and other
reason, permissive licenses are my preferred choice, while avoiding copyleft licenses and other
licenses which place restrictions on how my code may be used, and prevent me from including
important proprietary code, such as firmware, which can patch security vulnerabilities, privacy
issues, and stability issues.</p>
@ -201,9 +201,9 @@
<section id="licensing-code-bsd3clause">
<h4><a href="#licensing-code-bsd3clause">BSD 3-Clause License</a></h4>
<p><b>SPDX License Identifier:</b> <code>BSD-3-Clause</code></p>
<p><b>Type: Permissive</b></p>
<p><b>Type:</b> Permissive</p>
<p><a href="https://spdx.org/licenses/BSD-3-Clause.html">BSD 3-Clause License</a>
is a highly permissive license which allows content licensed under it to be used in
is a highly-permissive license which allows content licensed under it to be used in
any way, whether in source or binary form, and allows sublicensing under a different
license, with the only restrictions being the original copyright notice must be kept
in order to attribute the original creator of the licensed content, and the name of
@ -213,7 +213,7 @@
<section id="licensing-code-gpl2.0only">
<h4><a href="#licensing-code-gpl2.0only">GNU General Public License v2.0</a></h4>
<p><b>SPDX License Identifier:</b> <code>GPL-2.0-only</code></p>
<p><b>Type: Copyleft</b></p>
<p><b>Type:</b> Copyleft</p>
<p><a href="https://spdx.org/licenses/GPL-2.0-only.html">GNU General Public License v2.0</a>
is a strong copyleft license which restricts use of content licensed under it by
requiring all source code of the content to be publicly available, making
@ -235,7 +235,7 @@
<section id="licensing-noncode-ccby4.0">
<h4><a href="#licensing-noncode-ccby4.0">Creative Commons Attribution 4.0 International</a></h4>
<p><b>SPDX License Identifier:</b> <code>CC-BY-4.0</code></p>
<p><b>Type: Permissive</b></p>
<p><b>Type:</b> Permissive</p>
<p><a href="https://spdx.org/licenses/CC-BY-4.0.html">Creative Commons Attribution 4.0 International</a>
is a highly-permissive license which allows content licensed under it to be used in
any way, in any medium, with the only restriction being the original copyright
@ -274,39 +274,40 @@
a period, then the version of that phase; for example, <code>-alpha.<var>n</var></code> for
an alpha version, <code>-beta.<var>n</var></code> for a beta version, and
<code>-rc.<var>n</var></code> for a release candidate version, with
<code><var>n</var></code> being a non-negative integer. Stable versions have no suffix.</p>
<code><var>n</var></code> being a positive integer beginning at 1. Stable versions have no
suffix.</p>
</section>
<section id="versioning-phases">
<h3><a href="#versioning-phases">What Are the Phases?</a></h3>
<p>There are 4 phases of development. Each phase typically has its own branch in each source
code repository. The phases are as follows:</p>
<ol>
<li>Alpha: Pre-alpha development and alpha testing occurs in this phase. Features
are added, modified, and/or removed. Fixes and optimisations may also occur if they
are caught during this phase. This is where the majority of changes occur and where
the fine-grained commits can be found. Breakage is highly likely within this phase
as it makes no attempt to be stable or usable due to being where the most rapid
development occurs. Code is tested internally in a fine-grained manner and is moved
to the next phase only when it is deemed feature-complete and reasonably stable for
broader public testing. If you would like to assist in testing code in this phase,
you must use the code and/or tags from the source code repositories due to it not
being available publicly outside of them.</li>
<li>Beta: Feature-complete testing occurs in this phase. Only bug fixes and
<li><b>Alpha:</b> Pre-alpha development and alpha-testing occurs in this phase.
Features are added, modified, and/or removed. Fixes and optimisations may also occur
if they are caught during this phase. This is where the majority of changes occur
and where the fine-grained commits can be found. Breakage is highly likely within
this phase as it makes no attempt to be stable or usable due to being where the most
rapid development occurs. Code is tested internally in a fine-grained manner and is
moved to the next phase only when it is deemed feature-complete and reasonably
stable for broader public testing. If you would like to assist in testing code in
this phase, you must use the code and/or tags from the source code repositories due
to it not being available publicly outside of them.</li>
<li><b>Beta:</b> Feature-complete testing occurs in this phase. Only bug fixes and
optimisations occur in this phase, such as stability and security fixes. This phase
is classified as stable enough for broad public testing and is made available
publicly in many cases without having to use the source code repositories. Since
this phase contains only feature-complete code, no features will be added, modified,
or removed in this phase.</li>
<li>Release candidate (RC): Feature-complete testing occurs in this phase. Code in
the RC phase is often stable enough for production usage, but is not yet completely
acceptable to be classified as stable by my standards. This phase is often skipped
due to most bugs being caught in the beta phase, but will be used should the need
arise for finer-grained testing beyond what the beta phase can provide. Like the
beta phase, code in this phase is available publicly without requiring usage of the
source code repositories.</li>
<li>Stable: Feature-complete and well-tested code is moved to this phase. Code in
this phase is deemed to be stable enough for production usage and full support is
provided.</li>
<li><b>Release candidate (RC):</b> Feature-complete testing occurs in this phase.
Code in the RC phase is often stable enough for production usage, but is not yet
completely acceptable to be classified as stable by my standards. This phase is
often skipped due to most bugs being caught in the beta phase, but will be used
should the need arise for finer-grained testing beyond what the beta phase can
provide. Like the beta phase, code in this phase is available publicly without
requiring usage of the source code repositories.</li>
<li><b>Stable:</b> Feature-complete and well-tested code is moved to this phase.
Code in this phase is deemed to be stable enough for production usage and full
support is provided.</li>
</ol>
<p>When development of a new version has begun, the code within the alpha phase is rebased
onto the most recent code from the stable phase before work commences. This cycle continues
@ -316,8 +317,9 @@
<section id="services">
<h2><a href="#services">Services</a></h2>
<p>This list contains the policies and practices of my services.</p>
<p>My policies and practices are heavily security- and privacy-focused, with improvements made on an
ongoing basis as new technologies, protocols, and software become available.</p>
<p>My policies and practices are heavily security-focused and privacy-focused, with improvements
made on an ongoing basis as new technologies, hardware, software, and protocols become
available.</p>
<h3 id="services-websites"><a href="#services-websites">Websites</a></h3>
<ul>
<li>Unnecessary logging avoided (only logs required for security and debugging
@ -332,8 +334,8 @@
ciphers are used, along with
<a href="https://en.wikipedia.org/wiki/Forward_secrecy">forward secrecy</a></li>
<li>All connections made via high-security AEAD ciphers, preferring AES-256-GCM for
devices with AES hardware acceleration, and ChaCha20-Poly1305 for devices without AES
hardware acceleration, with AES-128-GCM as a fallback (AES-128-GCM is mandated for TLS
devices with AES hardware-acceleration, and ChaCha20-Poly1305 for devices without AES
hardware-acceleration, with AES-128-GCM as a fallback (AES-128-GCM is mandated for TLS
1.3 by
<a href="https://datatracker.ietf.org/doc/rfc8446#section-9.1">IETF RFC8446 section 9.1</a>)</li>
<li>All connections are made via high-security key exchange protocols, preferring
@ -377,16 +379,19 @@
<th id="hardware-smartphone-type">Type</th>
<th id="hardware-smartphone">Hardware</th>
<th id="hardware-smartphone-description">Description</th>
<th id="hardware-smartphone-source_model">Source model<br/>
(License)</th>
<th id="hardware-smartphone-source_model">
<p>Source model</p>
<p>(SPDX License Identifier)</p>
</th>
</tr>
</thead>
<tbody>
<tr>
<th id="hardware-smartphone-smartphone">Smartphone</th>
<th id ="google-pixel" headers="hardware hardware-smartphone-smartphone">
<img src="asset/img/google-pixel_8_pro.png" width="100" height="100" alt="Front and rear view of a Google Pixel 8 Pro in Obsidian colour"/><br/>
Google Pixel</th>
<img src="asset/img/google-pixel_8_pro.png" width="100" height="100" alt="Front and rear view of a Google Pixel 8 Pro in Obsidian colour"/>
Google Pixel
</th>
<td class="desc" headers="hardware-description google-pixel">
<h5>Security/Privacy</h5>
<p>Google Pixel devices are the best Android devices
@ -457,7 +462,10 @@
<p>Pixel 8-series is supported for a
<a href="https://support.google.com/nexus/answer/4457705#zippy=%2Cpixel-pro">minimum of 7 years from launch</a>.</p>
</td>
<td headers="hardware-smartphone-source_model google-pixel"></td>
<td headers="hardware-smartphone-source_model google-pixel">
<p>Proprietary</p>
<p>(NONE)</p>
</td>
</tr>
</tbody>
</table>
@ -481,19 +489,22 @@
<th id="software-pc-type">Type</th>
<th id="software-pc">Software</th>
<th id="software-pc-description">Description</th>
<th id="software-pc-source_model">Source model<br/>
(License)</th>
<th id="software-pc-source_model">
<p>Source model</p>
<p>(SPDX License Identifier)</p>
</th>
</tr>
</thead>
<tbody>
<tr>
<th id="software-pc-os">Operating system</th>
<th id="gentoo_linux" headers="software-pc software-pc-os">
<img src="asset/img/logo/gentoo_linux.png" width="100" height="100" alt="Gentoo Linux logo"/><br/>
Gentoo Linux</th>
<img src="asset/img/logo/gentoo_linux.png" width="100" height="100" alt="Gentoo Linux logo"/>
Gentoo Linux
</th>
<td class="desc" headers="software-pc-description gentoo_linux">
<p><a href="https://www.gentoo.org/">Gentoo Linux</a>
is a highly modular, source-based, Linux-based operating system
is a highly-modular, source-based, Linux-based operating system
which allows vast customisation to tailor the operating system
to suit your specific needs. There are many advantages to such
an operating system, with the most notable being the ability to
@ -512,17 +523,42 @@
<a href="https://src.inferencium.net/Inferencium/cfg/">configuration respository</a>.</p>
</td>
<td headers="software-pc-source_model gentoo_linux">
Open-source<br/>
(GPL-2.0-only)</td>
<p>Open-source</p>
<p>(GPL-2.0-only)</p>
</td>
</tr>
<tr>
<th id="software-pc-libc">C Standard Library</th>
<th id="musl" headers="software-pc software-pc-libc">
<img src="asset/img/logo/musl.png" width="90%" height="90%" alt="musl logo"/>
musl
</th>
<td class="desc" headers="software-pc-description musl">
<p><a href="https://musl.libc.org/">musl</a>
is a lightweight C standard library which aims to be correct,
standards-compliant, and safe. Unlike
<a href="https://gnu.org/software/libc">glibc</a>,
it greatly conforms to POSIX standards, deviating very little
by keeping its own non-standard extensions to a minimum, and
takes care to not break such conformity.</p>
<p>Also unlike glibc, due to its lightweight and
standards-compliant design, musl is portable and well-suited for
use in any system, whether desktop, server, or embedded.</p>
</td>
<td headers="software-pc-source_model musl">
<p>Open-source</p>
<p>(MIT)</p>
</td>
</tr>
<tr>
<th id="software-web_browser">Web browser</th>
<th id="chromium" headers="software-pc software-web_browser">
<img src="asset/img/logo/chromium.png" width="100" height="100" alt="Chromium logo"/><br/>
Chromium</th>
<img src="asset/img/logo/chromium.png" width="100" height="100" alt="Chromium logo"/>
Chromium
</th>
<td class="desc" headers="software-pc-description chromium">
<p><a href="https://chromium.org/">Chromium</a>
is a highly secure web browser which is often ahead of other web
is a highly-secure web browser which is often ahead of other web
browsers in security aspects. It has a dedicated security team
and a very impressive
<a href="https://www.chromium.org/Home/chromium-security/brag-sheet/">security brag sheet</a>.
@ -535,14 +571,16 @@
<a href="https://www.chromium.org/developers/testing/control-flow-integrity/">control-flow integrity (CFI)</a>.</p>
</td>
<td headers="software-pc-source_model chromium">
Open-source<br/>
(BSD-3-Clause)</td>
<p>Open-source</p>
<p>(BSD-3-Clause)</p>
</td>
</tr>
<tr>
<th rowspan="2" id="software-vcs">Version Control</th>
<th id="git" headers="software-pc software-vcs">
<img src="asset/img/logo/git.png" width="85%" height="85%" alt="Git logo"/><br/>
Git</th>
<img src="asset/img/logo/git.png" width="85%" height="85%" alt="Git logo"/>
Git
</th>
<td class="desc" headers="software-pc-description git">
<p><a href="https://git-scm.com/">Git</a>
is highly-flexible and feature-rich version control software
@ -552,22 +590,24 @@
client-server model or peer-to-peer.</p>
</td>
<td headers="software-pc-source_model git">
Open-source<br/>
(GPL-2.0-only)</td>
<p>Open-source</p>
<p>(GPL-2.0-only)</p>
</td>
</tr>
<tr>
<th id="gitea" headers="software-pc software-vcs">
<img src="asset/img/logo/gitea.png" width="100" height="100" alt="Gitea logo"/><br/>
Gitea</th>
<img src="asset/img/logo/gitea.png" width="100" height="100" alt="Gitea logo"/>
Gitea
</th>
<td class="desc" headers="software-pc-description software-vcs">
<p><a href="https://gitea.com/">Gitea</a>
is a self-hosted, all-in-one development platform with Git
hosting, code review, team collaboration, package registry and
CI/CD.</p>
is an all-in-one development platform with Git hosting, code
review, team collaboration, package registry and CI/CD.</p>
</td>
<td headers="software-pc-source_model gitea">
Open-source<br/>
(MIT)</td>
<p>Open-source</p>
<p>(MIT)</p>
</td>
</tr>
</tbody>
</table>
@ -588,8 +628,10 @@
<th id="software-smartphone-type">Type</th>
<th id="software-smartphone">Software</th>
<th id="software-smartphone-description">Description</th>
<th id="software-smartphone-source_model">Source model<br/>
(License)</th>
<th id="software-smartphone-source_model">
<p>Source model</p>
<p>(SPDX License Identifier)</p>
</th>
</tr>
</thead>
<tbody>
@ -611,7 +653,12 @@
<a href="https://github.com/GrapheneOS/kernel_gs-gs101/">hardened kernel</a>,
hardened memory allocator
(<a href="https://github.com/GrapheneOS/hardened_malloc/">hardened_malloc</a>)
to protect against common memory corruption vulnerabilities,
to protect against common heap memory corruption vulnerabilities
and reduce the lifetime of data in memory due to
zero-initialising memory on it being freed, Arm's Memory Tagging
Extension to provide protection against heap memory bugs such as
use-after-free and buffer overflow (MTE-supporting devices
only),
<a href="https://github.com/GrapheneOS/platform_bionic/">hardened Bionic standard C library</a>,
<a href="https://github.com/GrapheneOS/platform_system_sepolicy/">stricter SELinux policies</a>,
and local and remote hardware-backed attestation
@ -624,12 +671,12 @@
overall high-security practices.</p>
<p>For an extensive list of features GrapheneOS provides, visit
its
<a href="https://grapheneos.org/features/">official features list</a>
which provides extensive documentation.</p>
<a href="https://grapheneos.org/features/">official features list</a>.</p>
</td>
<td headers="software-smartphone-source_model grapheneos">
Open-source<br/>
(MIT)</td>
<p>Open-source</p>
<p>(MIT)</p>
</td>
</tr>
<tr>
<th id="software-smartphone-web_browser">Web browser</th>
@ -640,7 +687,7 @@
<p>Vanadium is a security-hardened, privacy-hardened,
Chromium-based web browser which utilises GrapheneOS' operating
system hardening to implement stronger defenses to the already
very secure Chromium web browser.</p>
very-secure Chromium web browser.</p>
<p>Its hardening alongside Chromium's base security features
includes
<a href="https://github.com/GrapheneOS/Vanadium/blob/13/patches/0081-Implement-UI-for-JIT-site-settings.patch">disabling JavaScript just-in-time (JIT) compilation by default</a>,
@ -652,8 +699,9 @@
<a href="https://github.com/GrapheneOS/Vanadium/">official repository</a>.</p>
</td>
<td headers="software-smartphone-source_model vanadium">
Open-source<br/>
(GPL-2.0-only)</td>
<p>Open-source</p>
<p>(GPL-2.0-only)</p>
</td>
</tr>
<tr>
<th rowspan="2" id="software-smartphone-messenger">Messenger</th>
@ -675,15 +723,16 @@
<p>Molly is available in
<a href="https://github.com/mollyim/mollyim-android#free-and-open-source">2 flavours</a>:</p>
<ul>
<li>Molly, which includes the same proprietary Google
<li><b>Molly:</b> Includes the same proprietary Google
code as Signal to support more features</li>
<li>Molly-FOSS, which removes the proprietary Google
<li><b>Molly-FOSS:</b> Removes the proprietary Google
code to provide an entirely open-source client</li>
</ul>
</td>
<td headers="software-smartphone-source_model molly">
Open-source<br/>
(GPL-3.0-only)</td>
<p>Open-source</p>
<p>(AGPL-3.0-only)</p>
</td>
</tr>
<tr>
<th id="conversations" headers="software-smartphone software-smartphone-messenger">
@ -695,10 +744,37 @@
<a href="https://xmpp.org/">XMPP</a>
client which serves as the de facto XMPP reference client and
has great usability.</p>
<p>It supports the latest and most important XMPP extensions
(XEPs), including, but not limited to:</p>
<ul>
<li><a href="https://xmpp.org/extensions/xep-0384.html"><b>XEP-0384 (OMEMO Encryption)</b></a><b>:</b>
Provides end-to-end encryption with perfect forward
secrecy</li>
<li><a href="https://xmpp.org/extensions/xep-0065.html"><b>XEP-0065 (SOCKS5 Bytestreams)</b></a><b>:</b>
Allows file transfers behind network address translation
and firewalls</li>
<li><a href="https://xmpp.org/extensions/xep-0198.html"><b>XEP-0198 (Stream Management)</b></a><b>:</b>
Allows XMPP to survive small network outages and changes
of the underlying TCP connection</li>
<li><a href="https://xmpp.org/extensions/xep-0215.html"><b>XEP-0215 (External Service Discovery)</b></a><b>:</b>
Facilitates peer-to-peer audio and video calls via
STUN/TURN</li>
<li><a href="https://xmpp.org/extensions/xep-0280.html"><b>XEP-0280 (Message Carbons)</b></a><b>:</b>
Allows synchronising messages across different XMPP
clients and sessions</li>
<li><a href="https://xmpp.org/extensions/xep-0313.html"><b>XEP-0313 (Message Archive Management)</b></a><b>:</b>
Allows storing messages on, and synchronising messages
with, the server, which is useful for scenarios such as
being offline</li>
<li><a href="https://xmpp.org/extensions/xep-0363.html"><b>XEP-0363 (HTTP File Upload)</b></a><b>:</b>
Allows sharing files in multi-user chats and with
offline contacts</li>
</ul>
</td>
<td headers="software-smartphone-source_model conversations">
Open-source<br/>
(GPL-3.0-only)</td>
<p>Open-source</p>
<p>(GPL-3.0-only)</p>
</td>
</tr>
<tr>
<th id="software-smartphone-viewer">Viewer</th>
@ -714,8 +790,24 @@
individual image and video file view, and folder view.</p>
</td>
<td headers="software-smartphone-source_model gallery">
Open-source<br/>
(Apache-2.0)</td>
<p>Open-source</p>
<p>(Apache-2.0)</p>
</td>
</tr>
<tr>
<th id="software-smartphone-calculator">Calculator</th>
<th id="opencalc" headers="software-smartphone software-smartphone-calculator">
<img src="asset/img/logo/opencalc.png" width="100" height="100" alt="OpenCalc logo"/><br/>
OpenCalc</th>
<td class="desc" headers="software-smartphone-description opencalc">
<p><a href="https://github.com/Darkempire78/OpenCalc">OpenCalc</a>
is a simple, lightweight calculator with optional scientific
features.</p>
</td>
<td headers="software-smartphone-source_model opencalc">
<p>Open-source</p>
<p>(GPL-3.0-only)</p>
</td>
</tr>
</tbody>
</table>