From b271e8c6d2081d6a4671168fb038c1ea8dcfb42d Mon Sep 17 00:00:00 2001
From: inference
Development branch. All pre-alpha development and alpha testing happens here.
+
Website root directory files pre-alpha development and alpha testing happens in this branch.
+Website asset, including multimedia, files pre-alpha development and alpha testing happens in +this branch.
+Website blog files pre-alpha development and alpha testing happens in this branch.
Website contact
Beta branch. All beta testing happens here.
+Feature-complete beta testing of merged code from development branches happens in this +branch.
Stable branch. Complete and stable versions are stored here.
-
+
Completed and tested versions from beta branch are stored in this branch.
+This branch contains files used in production.
All content is licensed under BSD-3-Clause-Clear license*.
+
All content is licensed under BSD-3-Clause-Clear license*.
*Exceptions:
Website blog files pre-alpha development and alpha testing happens in this branch.
Website contact +
Website contact files pre-alpha development and alpha testing happens in this branch.
+Website license files pre-alpha and alpha testing happens in this branch.
+Feature-complete beta testing of merged code from development branches happens in this branch.
From 2eb9184b4ba2a6c5c35941b091796b181ca68d9f Mon Sep 17 00:00:00 2001 From: inferenceAll content is licensed under All content is licensed under BSD-3-Clause-Clear license*.
*Exceptions:
From d6241f73b4f0a7ed19864539b424c1cf311f332f Mon Sep 17 00:00:00 2001
From: inference
Website root directory files pre-alpha development and alpha testing happens in this branch.
+Website asset, including multimedia, files pre-alpha development and alpha testing happens in this branch.
+Website blog files pre-alpha development and alpha testing happens in this branch.
Website root directory files pre-alpha development and alpha testing happens in this branch.
Website root directory files pre-alpha development and alpha testing happens in this branch.
Website asset, including multimedia, files pre-alpha development and alpha testing happens in this branch.
Website asset, including multimedia, files pre-alpha development and alpha testing happens in this branch.
Website blog files pre-alpha development and alpha testing happens in this branch.
Website blog files pre-alpha development and alpha testing happens in this branch.
Website contact files pre-alpha development and alpha testing happens in this branch.
Website contact files pre-alpha development and alpha testing happens in this branch.
Website license files pre-alpha and alpha testing happens in this branch.
Website license files pre-alpha and alpha testing happens in this branch.
Feature-complete beta testing of merged code from development branches happens in this branch.
Feature-complete beta testing of merged code from development branches happens in this branch.
Completed and tested versions from beta branch are stored in this branch.
This branch contains files used in production.
All content is licensed under All content is licensed under BSD-3-Clause-Clear license*. All content is licensed under All content is licensed under BSD-3-Clause-Clear license*. Feature-complete beta testing of merged code from development branches happens in this
branch. Completed and tested versions from beta branch are stored in this branch. Inferencium cares about upstreaming and sharing code, and strongly prefers licenses which
+ have high license compatibility in order to make sharing code with other projects possible;
+ for this reason, permissive licenses are our preferred choice, while avoiding copyleft
+ licenses and other licenses which place restrictions on how our code may be used. All
+ Inferencium code is and will be permissively licensed unless specific circumstances make it
+ impractical or infeasible to do so. Our goal is to share code which has the least amount of
+ restrictions as possible, to allow wider propagation of our code and allow more
+ use cases and possibilities. Inferencium cares about upstreaming and sharing code, and strongly prefers licenses which
+ Inferencium cares about upstreaming and sharing code, strongly preferring licenses which
have high license compatibility in order to make sharing code with other projects possible;
for this reason, permissive licenses are our preferred choice, while avoiding copyleft
- licenses and other licenses which place restrictions on how our code may be used. All
- Inferencium code is and will be permissively licensed unless specific circumstances make it
- impractical or infeasible to do so. Our goal is to share code which has the least amount of
- restrictions as possible, to allow wider propagation of our code and allow more
- use cases and possibilities.
*Exceptions:
From a0c29555f2fc6ecc28030f075bf09d6017a22b08 Mon Sep 17 00:00:00 2001
From: inference
Licensing
-
*Exceptions:
From 30c8f6f525f51391266e95a9b4350580f8ed984c Mon Sep 17 00:00:00 2001
From: inference
-stable
This branch contains files used in production.
From d0a3c45f1b3d77686bda372682763d06404c1713 Mon Sep 17 00:00:00 2001
From: inference
+ Licensing
+
+
+
Recommendations
From 42e29c9e26f1cfd915c309bbf5c10a864bb91440 Mon Sep 17 00:00:00 2001
From: inference Licensing
-
Inferencium cares about upstreaming and sharing code, strongly preferring licenses which - have high license compatibility in order to make sharing code with other projects possible; - for this reason, permissive licenses are our preferred choice, while avoiding copyleft - licenses and other licenses which place restrictions on how our code may be used, and - prevent us from including important proprietary code, such as firmware, which can patch - security vulnerabilities. All Inferencium code is and will be permissively licensed unless - specific circumstances make it impractical or infeasible to do so. Our goal is to share code - which has the least amount of restrictions as possible, to allow wider propagation of our - code and allow more use cases and possibilities, as well as ensuring proprietary code, - whenever required, is permitted to be included.
+ have high license compatibility in order to permit sharing code with as many other projects + as possible; for this reason, permissive licenses are our preferred choice, while avoiding + copyleft licenses and other licenses which place restrictions on how our code may be used, + and prevent us from including important proprietary code, such as firmware, which can patch + security vulnerabilities and privacy issues. All Inferencium code is and will be + permissively licensed unless specific circumstances make it impractical or infeasible to do + so. Our goal is to share code which has the least amount of restrictions as possible, to + allow wider propagation of our code and allow more use cases and possibilities, as well as + ensuring proprietary code, whenever required, is permitted to be included.SPDX-License-Identifier: BSD-3-Clause-Clear
+Type: Permissive
+BSD 3-Clause Clear 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 the
+ project and/or its contributors may not be used to endorse or promote products derived from
+ the original project.
+ BSD 3-Clause Clear is a derivative of BSD 3-Clause, which adds an explicit statement clarifying that patent rights are not
+ granted by the license alone, and must be granted separately by the copyright and/or patent
+ holder(s). We prefer this license over the standard BSD 3-Clause license due to this
+ explicit statement which removes any possibility of debate and misunderstanding in regards
+ to patents applied to code using a BSD 3-Clause license.
SPDX-License-Identifier: BSD-3-Clause-Clear
+SPDX-License-Identifier: BSD-3-Clause-Clear
Type: Permissive
Date: Thu, 16 Mar 2023 06:58:16 +0000
Subject: [PATCH 024/239] Apply body-link class to body links.
---
about.html | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/about.html b/about.html
index 96844fe..88a631e 100644
--- a/about.html
+++ b/about.html
@@ -5,7 +5,7 @@
-
+
@@ -132,7 +132,7 @@
Type: Permissive BSD 3-Clause Clear 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
@@ -140,7 +140,7 @@
project and/or its contributors may not be used to endorse or promote products derived from
the original project.SPDX-License-Identifier: BSD-3-Clause-Clear
-
BSD 3-Clause Clear is a derivative of BSD 3-Clause, which adds an explicit statement clarifying that patent rights are not
granted by the license alone, and must be granted separately by the copyright and/or patent
holder(s). We prefer this license over the standard BSD 3-Clause license due to this
From 4aea933ad684b493f5db31a5d7a0a4c2753842fc Mon Sep 17 00:00:00 2001
From: inference
SPDX-License-Identifier: BSD-3-Clause-Clear
Type: Permissive
BSD 3-Clause Clear 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 the
- project and/or its contributors may not be used to endorse or promote products derived from
- the original project.
- BSD 3-Clause Clear is a derivative of BSD 3-Clause, which adds an explicit statement clarifying that patent rights are not
- granted by the license alone, and must be granted separately by the copyright and/or patent
- holder(s). We prefer this license over the standard BSD 3-Clause license due to this
- explicit statement which removes any possibility of debate and misunderstanding in regards
- to patents applied to code using a BSD 3-Clause license.
SPDX-License-Identifier: MIT
+ Type: Permissive
+MIT License 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 restriction being the original copyright notice must be kept in order
+ to attribute the original creator of the licensed content.
+ Due to this license allowing the original project's name and/or contributors to be used to
+ endorse or promote products derived from the original project, unless an explicit statement
+ is made alongside this license, increasing complexity and deviating from the standard
+ license text, we prefer BSD 3-Clause Clear License; however, MIT License is a great choice when derivatives
+ using the name of the original project and/or its contributors is a non-issue.
+
SPDX-License-Identifier: MIT
Type: Permissive
MIT License is a highly permissive license which allows content licensed under it to be +
MIT License 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 restriction being the original copyright notice must be kept in order
to attribute the original creator of the licensed content.
Due to this license allowing the original project's name and/or contributors to be used to
endorse or promote products derived from the original project, unless an explicit statement
is made alongside this license, increasing complexity and deviating from the standard
- license text, we prefer BSD 3-Clause Clear License; however, MIT License is a great choice when derivatives
using the name of the original project and/or its contributors is a non-issue.
From 4a994f8936fee02e7c45ea9e750fca1a828140f7 Mon Sep 17 00:00:00 2001
From: inference
SPDX-License-Identifier: GPL-2.0-only
+ Type: Copyleft
+GNU General Public License v2.0 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 binary-only form and inclusion of proprietary code impossible, requiring
+ all derivatives to be licensed under the same license (allowing sublicensing under only
+ newer GPL licenses if GPL-2.0-or-later
is specified in the
+ SPDX-License-Identifier), and requiring the original copyright notice to be kept in order to
+ attribute the original creator of the licensed content.
+ Due to the restrictive and invasive nature of this license, it is avoided unless such
+ restrictions would be beneficial to Inferencium code; whenever this is the case, the GNU
+ General Public License v2.0 will be used, rather than the more restrictive
+ GNU General Public License v3.0", and relicensing derivatives under GNU General Public
+ License v3.0 will be disallowed.
SPDX-License-Identifier: GPL-3.0-only
+ Type: Copyleft
+GNU General Public License v3.0 is a strong copyleft license which restricts usage of
+ content licensed under it by requiring all source code of the content to be publicly
+ available, making binary-only form and inclusion of proprietary code impossible, requiring
+ all derivatives to be licensed under the same license (allowing sublicensing under only
+ newer GPL licenses if GPL-3.0-or-later
is specified in the
+ SPDX-License-Identifier), requiring the content to be made available only on systems which
+ allow modifying the content, such as systems with unlocked/unlockable bootloaders and/or
+ which are unsigned by the OEM, and requiring the original copyright notice to be kept in
+ order to attribute the original creator of the licensed content.
+ Due to the restrictive and invasive nature of this license, and the fact it requires code to
+ be included only on specific systems, further restricting usage of Inferencium code, it is
+ avoided completely.
SPDX-License-Identifier: GPL-3.0-only
From a6a59f602fa8677c29dc5e6861bd34b87bbb8492 Mon Sep 17 00:00:00 2001
From: inference SPDX-License-Identifier: BSD-3-Clause-Clear
Type: Permissive
SPDX-License-Identifier: MIT
Type: Permissive
SPDX-License-Identifier: GPL-2.0-only
Type: Copyleft
SPDX-License-Identifier: GPL-3.0-only
Type: Copyleft
SPDX-License-Identifier: BSD-3-Clause-Clear
Type: Permissive
SPDX-License-Identifier: MIT
Type: Permissive
SPDX-License-Identifier: GPL-2.0-only
Type: Copyleft
SPDX-License-Identifier: GPL-3.0-only
Type: Copyleft
SPDX-License-Identifier: CC-BY-4.0
+ Type: Permissive
+Creative Commons Attribution 4.0 International 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 notice must be kept in order to attribute the + original creator of the licensed content.
SPDX-License-Identifier: CC-BY-NC-4.0
+ Type: Permissive non-commercial
+Creative Commons Attribution Non Commercial 4.0 International is a permissive license + which allows content licensed under it to be used in any way, in any medium, with its + restrictions being commercial usage is prohibited, and the original copyright notice must be + kept in order to attribute the original creator of the licensed content. + Due to the non-commercial restriction of this license preventing Inferencium code from being + used for any purpose, specifically preventing commercial usage we do not want to prevent, it + is avoided completely.
SPDX-License-Identifier: CC-BY-4.0
Type: Permissive
Creative Commons Attribution Non Commercial 4.0 International is a permissive license
- which allows content licensed under it to be used in any way, in any medium, with its
+ which allows content licensed under it to be used in any way, in any medium, with the
restrictions being commercial usage is prohibited, and the original copyright notice must be
kept in order to attribute the original creator of the licensed content.
Due to the non-commercial restriction of this license preventing Inferencium code from being
From b5f5141616b4cb4a0468e4fbd39012ff0fff778a Mon Sep 17 00:00:00 2001
From: inference Type: PermissiveCode
- BSD 3-Clause Clear License
SPDX-License-Identifier: BSD-3-Clause-Clear
SPDX-License-Identifier: MIT
Type: Permissive
@@ -191,7 +191,7 @@ >BSD 3-Clause Clear License; however, MIT License is a great choice when derivatives using the name of the original project and/or its contributors is a non-issue.SPDX-License-Identifier: GPL-2.0-only
Type: Copyleft
@@ -228,7 +228,7 @@ >OtherSPDX-License-Identifier: GPL-3.0-only
Type: Copyleft
From 78bca25d60ba73c38fb1da89816a744e4fbb1445 Mon Sep 17 00:00:00 2001 From: inferenceI write about my research and experience in cybersecurity and also physical security. + I write about my research and experience in cybersecurity and also physical security. Most of my postings are security-related, but I occasionally post about other aspects of my - life.
+ life.I am an open source advocate for the preservation and modifiability of source code. I
+ I am an open source advocate for the preservation and modifiability of source code. I
believe source code should be considered human knowledge as much as past knowledge and
teachings were; it is how modern humanity survives and runs.
Source code being modifiable allows it to be adapted for use by anyone, whether to add
@@ -129,7 +129,7 @@
I am also a modular design advocate for the ability to securely and robustly make changes to
hardware and software without the entire system being affected.
If you want to contact me for any reason, you can use my + If you want to contact me for any reason, you can use my contact methods.
sys-hardening@muc.xmpp.inferencium.net
, and its respective
+ off-topic channel at sys-hardening-ot@muc.xmpp.inferencium.net
.
SPDX-License-Identifier: <license>
; see the
+ SPDX license list for the full list of available licenses under this standard.
Website root directory files pre-alpha development and alpha testing happens in this branch.
+Website root directory files pre-alpha development and alpha testing happens in this branch.
+Feature-complete modifications of this branch are merged to beta branch for beta testing.
Website asset, including multimedia, files pre-alpha development and alpha testing happens in -this branch.
+this branch.Website blog files pre-alpha development and alpha testing happens in this branch.
+Website blog files pre-alpha development and alpha testing happens in this branch.
+Feature-complete modifications of this branch are merged to beta branch for beta testing.
Website contact files pre-alpha development and alpha testing happens in this branch.
+Website contact files pre-alpha development and alpha testing happens in this branch.
+Feature-complete modifications of this branch are merged to beta branch for beta testing.
Website license files pre-alpha and alpha testing happens in this branch.
+Website license files pre-alpha and alpha testing happens in this branch.
+Feature-complete modifications of this branch are merged to beta branch for beta testing.
Feature-complete beta testing of merged code from development branches happens in this -branch.
+branch.Completed and tested versions from beta branch are stored in this branch.
-This branch contains files used in production.
Feature-complete and tested versions from beta branch are stored in this branch.
+Merges from beta branch to this branch are squashed, and the updated versions of the individual
+files are mentioned in the commit messages.
+This branch contains code used in production.
Website root directory files pre-alpha development and alpha testing happens in this branch.
+
Website root directory files pre-alpha development and alpha testing occurs in this branch.
Feature-complete modifications of this branch are merged to beta branch for beta testing.
Website asset, including multimedia, files pre-alpha development and alpha testing happens in
-this branch.
+
Website asset, including multimedia, files pre-alpha development and alpha testing occurs in this
+branch.
Feature-complete modifications of this branch are merged to beta branch for beta testing.
Website blog files pre-alpha development and alpha testing happens in this branch.
+
Website blog files pre-alpha development and alpha testing occurs in this branch.
Feature-complete modifications of this branch are merged to beta branch for beta testing.
Website contact files pre-alpha development and alpha testing happens in this branch.
+
Website contact files pre-alpha development and alpha testing occurs in this branch.
Feature-complete modifications of this branch are merged to beta branch for beta testing.
Website license files pre-alpha and alpha testing happens in this branch.
+
Website license files pre-alpha and alpha testing occurs in this branch.
Feature-complete modifications of this branch are merged to beta branch for beta testing.
Feature-complete beta testing of merged code from development branches happens in this
-branch.
+
Feature-complete beta testing of merged code from development branches occurs in this branch.
Merges from development branches to this branch are squashed, and the updated versions of the
individual files are mentioned in the commit messages.
For a curated list of music I enjoy, visit my + music page.
+This is a curated list of my personally-enjoyed music. The list is alphabetically-sorted A-Z, based
+ on artist name, followed by track name, and is formatted as ARTIST - TRACK
. Each item in
+ the list has its own individual link which will take you to an official source of the item (or the best
+ alternative when an official source is unavailable). It is your responsibility to comply with any local
+ laws when following these links and/or consuming any media found in this list.
This is a curated list of my personally-enjoyed music. The list is alphabetically-sorted A-Z, based
- on artist name, followed by track name, and is formatted as ARTIST - TRACK
. Each item in
- the list has its own individual link which will take you to an official source of the item (or the best
- alternative when an official source is unavailable). It is your responsibility to comply with any local
- laws when following these links and/or consuming any media found in this list.
This is a curated list of my personally-enjoyed music. The list is alphabetically-sorted A-Z, based
+ on artist name, followed by track name, and is formatted as ARTIST - TRACK
. Each item in
+ the list has its own individual link which will take you to an official source of the item (or the best
+ alternative when an official source is unavailable). It is your responsibility to comply with any local
+ laws when following these links and/or consuming any media found in this list.
This is a curated list of my personally-enjoyed music. The list is alphabetically-sorted A-Z, based
- on artist name, followed by track name, and is formatted as ARTIST - TRACK
. Each item in
- the list has its own individual link which will take you to an official source of the item (or the best
- alternative when an official source is unavailable). It is your responsibility to comply with any local
- laws when following these links and/or consuming any media found in this list.
This is a curated list of my personally-enjoyed music. The list is alphabetically-sorted A-Z,
+ based on artist name, followed by track name, and is formatted as ARTIST - TRACK
.
+ Each item in the list has its own individual link which will take you to an official source of
+ the item (or the best alternative when an official source is unavailable). It is your
+ responsibility to comply with any local laws when following these links and/or consuming any
+ media found in this list.
- I have phased out usage of obsolete, insecure PGP for all contact methods.
-- I have phased out usage of email, including TLS-encrypted email.
-Whenever possible, use the following contact methods; they allow verification to mitigate man-in-the-middle
- attacks, have high security, and reasonable privacy.
-
-
Use the
- keys for each contact method to verify my devices.
- Note: Verification does not verify a person, only their devices, and can be defeated via coercion or other
- force.
Signal
-
- +447549902964
-
XMPP
-
- inference@inferencium.net
- (Key)
-
-
-
-
-
If metadata leakage is an issue for you, you can use the following contact methods.
-
- Note: These services do not have verification functionality and will be treated as less secure; unless
- you really need to use these services, use a preferred method instead.
Briar
-
- Unavailable
Session
-
- Unavailable
- I have phased out usage of obsolete, insecure PGP for all contact methods.
+- I have phased out usage of email, including TLS-encrypted email.
+Whenever possible, use the following contact methods; they allow verification
+ to mitigate man-in-the-middle attacks, have high security, and reasonable
+ privacy.
+
+
Use the
+ keys for each contact method to verify my devices.
+ Note: Verification does not verify a person, only their devices, and can be
+ defeated via coercion or other force.
Signal
+
+ +447549902964
+
XMPP
+
+ inference@inferencium.net
+ (Key)
+
+
+
+
+
If metadata leakage is an issue for you, you can use the following contact methods.
+
+ Note: These services do not have verification functionality and will be treated as less secure; unless
+ you really need to use these services, use a preferred method instead.
Briar
+
+ Unavailable
Session
+
+ Unavailable
If metadata leakage is an issue for you, you can use the following contact methods.
Note: These services do not have verification functionality and will be treated as less secure; unless
From f9a202ce25c7061ecffbfa044c4bd84040854abb Mon Sep 17 00:00:00 2001
From: inference