Kevin Day [Sat, 10 Aug 2024 21:10:20 +0000 (16:10 -0500)]
Update: Documentation and specifications.
Update the raw documentation and specifications with a recent copy.
This updates some pages, such as adding the "stage" to the fakefile and settings file.
Kevin Day [Sat, 10 Aug 2024 20:08:57 +0000 (15:08 -0500)]
Cleanup: Remove 'file:""' from file paths.
There should be some HTML markup, such as `<code></code>` wrapping these instead of using a literal `file:""` IKI syntax.
I clearly forgot to convert the IKI syntax for `file`.
I do not remember or I have not yet decided what the `file:""` should be mapped to in HTML.
Just get rid of the IKI syntax.
I will make further updates once I figure out how I want a file text to be presented.
Kevin Day [Sat, 10 Aug 2024 19:32:24 +0000 (14:32 -0500)]
Cleanup: Add specification date to the Controller specifications.
I only did a quick glance through the specifications and they look the same as the pages.
The only change is copying the version date from the specifications file onto the web page.
Kevin Day [Wed, 12 Jun 2024 00:37:37 +0000 (19:37 -0500)]
Update: Specifications pages.
I did a quick review of the updates but I may very easily have missed something.
I attempt to run the following commands to generate this:
# fss_basic_list_read specifications/iki.txt +Q -cn "IKI Specifications" | iki_read +Q -w -WWW character '<code class="code">' "</code>" code '<code class="code">' '</code>' italic '<em class="em">' '</em>'
and this:
# fss_basic_list_read specifications/fss.txt +Q -cn "Featureless Settings Specifications" | iki_read +Q -w -rrrrrrrr anti-KISS 'anti-<abbr title="Keep It Simple Stupid">KISS</abbr>' ASCII '<abbr title="American Standard Code for Information Interchange">ASCII</abbr>' BOM '<abbr title="Byte Order Mark">BOM</abbr>' FSS '<abbr title="Featureless Settings Specifications">FSS</abbr>' KISS '<abbr title="Keep It Simple Stupid">KISS</abbr>' UTF-8 '<abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr>' URL '<abbr title="Byte Order Mark">URL</abbr>' XML '<abbr title="Extensible Markup Language">XML</abbr>' -WWW character '<code class="code">' "</code>" code '<code class="code">' '</code>' italic '<em class="em">' '</em>'
This exposed a bug somewhere where "-rrrrrrrr" is too large.
I had to break it up like this:
# fss_basic_list_read specifications/fss.txt +Q -cn "Featureless Settings Specifications" | iki_read +Q -w -rrrr anti-KISS 'anti-<abbr title="Keep It Simple Stupid">KISS</abbr>' ASCII '<abbr title="American Standard Code for Information Interchange">ASCII</abbr>' BOM '<abbr title="Byte Order Mark">BOM</abbr>' FSS '<abbr title="Featureless Settings Specifications">FSS</abbr>' -r KISS '<abbr title="Keep It Simple Stupid">KISS</abbr>' -r UTF-8 '<abbr title="Unicode Transformation Format 8-bit">UTF-8</abbr>' -r URL '<abbr title="Byte Order Mark">URL</abbr>' -r XML '<abbr title="Extensible Markup Language">XML</abbr>' -WWW character '<code class="code">' "</code>" code '<code class="code">' '</code>' italic '<em class="em">' '</em>'
This problem will be addressed later.
I also noticed that the specification that I am updating contains less IKI syntax than what is used on the website.
I may have to do additional clean ups to the source specifications.
This is good enough of an update for now but I suspect that I will have updates later on.
Kevin Day [Thu, 6 Jun 2024 01:12:16 +0000 (20:12 -0500)]
Feature: Add "Magic Bit" to the FSS-000F (Simple Packet) format.
Make the FSS-000F (Simple Packet) format more generalized and flexible by allowing other payload formats than only formally supporting FSS-000E (Payload).
This adds a new optional "Magic Block" that is designated via the "Magic Bit", which is the third bit from the left.
This should make it easy to store the Simple Packet as a local file.
This should make it easier for routing to optimize processing of the packet by quickly identifying the packet.
The "Control Block" and the "Size Block" have static sizes and positions, which should make it easy to identify the "Magic Block".
The third bit should be checked and then the "Magic Block" should be checked when trying to quickly identify the packet type via the "Magic Block".
Kevin Day [Fri, 29 Mar 2024 21:46:40 +0000 (16:46 -0500)]
Update: Out of date specification documentation.
Make sure the version dates are present.
Working on this led to the discovery of some bugs in the iki specification that have been fixed in the original source.
Kevin Day [Wed, 13 Mar 2024 02:11:13 +0000 (21:11 -0500)]
Update: FSS-000E specification, adding "salt" and "time" as suggested headers.
I intend to keep the recommended and now suggested headers to a bare minimum.
I have decided that "salt" and "time" should be common enough and important enough to add to this small list.
Kevin Day [Wed, 28 Feb 2024 02:34:40 +0000 (20:34 -0600)]
Cleanup: The OSLv1 license, fixing grammar and clarifying intent.
This does not change the license other than fixing grammar and making the intent more consistent and clear.
This also adds a day to the license data that represents that last time this license has been modified.
The version number is changed only when there is a functional or substantial change to the license.
I have noticed that in some places individuals decide the "includes" is a restrictive word.
It is not, especially given that it is literally an inclusive word.
This changes the wording from "includes" or "including" to something like "including but not limited to" avoid any of that non-sense.
The proper application of the English language would result in the "but not limited to" being redundant and pointless.
This specific language is added just in case somebody does not understand the English language when it comes to the word "including".
Try to be consistent and use "lawful" instead of "legal" (except in cases where both are mentioned).
Generally, referring to "lawful" here also includes "legal".
The "lawful" is chosen to represent actual law rather than the more questionable "legal" terminology.
The wording of "access to use, implement, etc.." can be misinterpreted such that the "access to" is applied to implement (and etc..) such that it becomes "access to implement".
The actual intent and design is not simply around "access to implement".
Instead, it is around "to implement", period.
Clarify this by splitting out "access to use" into "to access", "to use", etc...
The deprecated key is still not quite expired (it expires next month), so use that one to sign this one again.
Future versions will not do this and will very likely be self-signed (there is not much that can be done about that).
Kevin Day [Mon, 1 Jan 2024 16:59:43 +0000 (10:59 -0600)]
Update: Specifications and add FSS-0010 Encrypted Simple Packet specification.
Add "version date" paragraph to each specification to make it clearer when this specification was last updated.
I happened to notice that there is a mistake in the FSS-000E specification.
I fixed this in the proper FLL source code but this is after the formal 0.6.8 release was made, unfortunately.
This documentation will be more up to date that the current release.
Update the FSS-000E and FSS-000F specifications to reflect the changes formally introduced as of the 0.6.8 release on 2023/12/31.
The FSS-0010 Encrypted Simple Packet specification has been present for a while now but I failed to update the website.
This specification is now present.
Kevin Day [Mon, 1 Jan 2024 16:58:05 +0000 (10:58 -0600)]
Update: The code style should flow more naturally.
Browsers are displaying monospace fonts slightly larger than normal fonts.
Change the code font-size to be slightly smaller than the standard to make the flow more natural.
Kevin Day [Tue, 9 May 2023 02:56:06 +0000 (21:56 -0500)]
Update: Website package release for 2023/05/09.
Designate another release point where the website is packaged and released for easy download.
I would note that I am, going forward, trying to use UTC to communicate the date rather than my local time.
This is not yet a habit and will take some time to get consistent.
Kevin Day [Tue, 9 May 2023 02:52:30 +0000 (21:52 -0500)]
Update: Development update of TKIS, tools, and development iso on 2023/05/09.
A collection of the latest state of the Turtle Kevux development.
This is not intended to work per-say but is instead a bookmark of the current progress.
Major work is needed in regards to the kernel, the initrd, and the system init.
There is no GUI work at all (such as Xorg, etc..).
Kevin Day [Wed, 15 Feb 2023 05:44:16 +0000 (23:44 -0600)]
Update: Featureless Make specification regarding multiple single-valued Objects.
This is not referring to Objects with multiple Content.
Instead, this refers to multiple identical Objects where that Object is expected to have only a single assignment.
Kevin Day [Thu, 8 Sep 2022 02:27:58 +0000 (21:27 -0500)]
Update: Improve accessibility in the "Continue reading..." and fix a mistake in a label.
The continue reading must remain as-is for proper use.
The accessibility tools do not understand article and document structure as well as they should.
Provide hints as per Aria and WCAG standards to help with this.
To get this working I've had to add unwanted id attributes, which clobers up the id list.
This makes things a bit less accessible for other uses due to the invalid or non-meaningful id associations added to make the aria-labelledby work.
The labeled by situation is a good reminder that I need to publish an article about my Context Markup Language (CML) so that I can provide a better language.
This situation is just an example of bad design by the accessibility developers and WCAG.
At least this shows progress on their end.
projects / kevux.org-website / log