diff --git a/about.xhtml b/about.xhtml index 03e9273..bfb4fc9 100644 --- a/about.xhtml +++ b/about.xhtml @@ -1,7 +1,7 @@ - + @@ -16,25 +16,22 @@

About

-

About Me

+

About Me

I am Jake Winters, also known by my pseudonym "Inference", a security researcher based in United Kingdom.
I am the founder, lead developer, and administrator, of Inferencium.
@@ -92,21 +95,9 @@ webpage.

If you wish to contact me for any reason, you can use my contact methods.

-

Is it GNU/Linux or Just Linux?

-

It's just Linux. GNU is unrelated to Linux, which is a kernel - developed by Linus Torvalds. Linux can be used entirely without GNU - software in userspace, and the kernel can be compiled without the use of - GNU tools. Just because GNU tools were used to initally develop and - compile the kernel, and were initially the only available tools for - userspace, does not make this true today, and it never made GNU a part - of Linux itself at any point of time.

-

Where are all of the other forward-slashes for every other piece of - software on a Linux-based system which makes it just as usable? If a - system is running "GNU/Linux", it should be using more than a single - forward-slash when there is more to the system than only GNU.

-

Date and Time

+

Date and Time

All dates and times across my services are ISO 8601-compliant. The short-form format YYYY-MM-DD is used for dates, and @@ -117,7 +108,7 @@ YYYYMMDDThhmmss-hhmm (with negative offset).

-

Licensing

+

Licensing

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 my @@ -193,8 +184,97 @@ push an ideology by a specific group of people. If software isn't "free", it's not open-source, either.

+
+

Versioning

+
+

What is the Numbering Scheme?

+

All code uses + Semantic Versioning. + The numbering scheme divided into 3 blocks (herein referred to + as Block 0, Block 1, and Block 2, in left-to-right order); the + version blocks are separated by periods. When a version number + block is incremented, all blocks to the right of it are reset to + 0. The legacy versioning scheme was a similar numerical + versioning scheme which lacked standardisation.

+

Block 0 contains the MAJOR version; + this number is incremented whenever an API-incompatible change + is made to the code.

+

Block 1 contains the MINOR version; + this number is incremented whenever an API-compatible, + substantial change is made to the code, such as adding a + feature.

+

Block 2 contains the PATCH version; + this number is incremented whenever an API-compatible, + unsubstantial change is made to the code, such as fixing or + optimising the code.

+

Development and pre-release versions are suffixed with + a hyphen, followed by their phase, a period, then the version of + that phase; for example, -alpha.n for an + alpha version, -beta.n for a beta + version, and -rc.n for a release + candidate version, with n being a + non-negative integer. Stable versions have no suffix.

+
+
+

What Are the Phases?

+

There are 4 phases of development. Each phase typically has + its own branch in each source code repository. The phases are as + follows: +

    +
  1. 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.
    2. +
  2. Beta: 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.
    3. +
  3. 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.
    4. +
  4. 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.
    5. +
+

+

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 for the + lifetime of the code.

+
+
-

Services

+

Services

This list contains the policies and practices of my services.

My policies and practices are heavily security- and privacy-focused, with improvements made on an ongoing basis as new technologies, protocols, and @@ -214,14 +294,14 @@ forward secrecy

  • 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 + 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 IETF RFC8446 section 9.1)
  • All connections are made via high-security key exchange protocols, preferring X25519, with secp256r1 as a fallback - (secp256r1 is mandated for TLS 1.3 by - IETF RFC8446 section 9.1)
    • + (secp256r1 is mandated for TLS 1.3 by IETF RFC8446 section + 9.1)
  • Domain Name System Security Extensions (DNSSEC) enabled to provide a root-of-trust for encryption and authentication for domain and server configuration
    • @@ -246,7 +326,7 @@
    -

    Recommendations

    +

    Recommendations

    Hardware

    Smartphone

    @@ -261,7 +341,7 @@ Smartphone -
    + Front and rear view of a Google Pixel 8 Pro in Obsidian colour
    Google Pixel @@ -340,18 +420,13 @@ by eliminating up to 95% of all security issues caused by memory-unsafety.

    Support
    -

    Pixel 4a (5G), Pixel 5, and Pixel 5a, are - supported for a +

    Pixel 5a is supported for a minimum of 3 years from launch.

    Pixel 6-series, Pixel 7-series, Pixel - Fold, and Pixel Tablet, are supported for a + Fold, and Pixel Tablet are supported for a minimum of 5 years from launch.

    Pixel 8-series is supported for a - minimum of 7 years from launch, - putting it on the same support level as - Apple; Google have even surpassed Apple in - this regard, as Apple does not commit to a - support timeframe for their devices.

    + minimum of 7 years from launch.

    @@ -372,7 +447,7 @@ Operating system -
    + Gentoo Linux logo
    Gentoo Linux @@ -406,7 +481,7 @@ Web browser -
    + Chromium logo
    Chromium @@ -442,7 +517,7 @@ Operating system -
    + GrapheneOS logo
    GrapheneOS @@ -487,7 +562,7 @@ Web browser -
    + Vanadium logo
    Vanadium @@ -512,7 +587,7 @@ Messenger -
    + Molly logo
    Molly @@ -546,7 +621,7 @@ -
    + Conversations logo
    Conversations @@ -565,9 +640,22 @@
    -

    Music

    +

    Music

    For a curated list of music I enjoy, visit my music page.

    +
    +

    Is it GNU/Linux or Just Linux?

    +

    It's just Linux. GNU is unrelated to Linux, which is a kernel developed by + Linus Torvalds. Linux can be used entirely without GNU software in userspace, + and the kernel can be compiled without the use of GNU tools. Just because GNU + tools were used to initally develop and compile the kernel, and were initially + the only available tools for userspace, does not make this true today, and it + never made GNU a part of Linux itself at any point of time.

    +

    Where are all of the other forward-slashes for every other piece of software + on a Linux-based system which makes it just as usable? If a system is running + "GNU/Linux", it should be using more than a single forward-slash when there is + more to the system than only GNU.

    +