diff --git a/faq.html b/faq.html
index 55349ffb1..69655f247 100644
--- a/faq.html
+++ b/faq.html
@@ -458,7 +458,7 @@
 <li><strong>Q 1.9</strong>: <a class="normal" href="#uuid">How can I avoid re-entering my UUID to mkiocccentry?</a></li>
 <li><strong>Q 1.10</strong>: <a class="normal" href="#submission_dir">How can I avoid having to move or delete my submission directory for the same workdir?</a></li>
 </ul>
-<h2 id="ioccc-judging-process">2. <a href="#judging_proceess">IOCCC Judging process</a></h2>
+<h2 id="ioccc-judging-process">2. <a href="#judging_process">IOCCC Judging process</a></h2>
 <ul>
 <li><strong>Q 2.0</strong>: <a class="normal" href="#questions">What is the best way to ask a question about the IOCCC rules, guideline and tools?</a></li>
 <li><strong>Q 2.1</strong>: <a class="normal" href="#feedback">How can I comment or make a suggestion on IOCCC rules, guidelines and tools?</a></li>
@@ -586,6 +586,7 @@
 <div id="enter_questions">
 <h2 id="section-0-entering-the-ioccc-the-bare-minimum-you-need-to-know">Section 0: Entering the IOCCC: the bare minimum you need to know</h2>
 </div>
+<p>Jump to: <a href="#">top</a></p>
 <div id="enter">
 <div id="step_0">
 <div id="step_1">
@@ -955,7 +956,7 @@ and <a href="next/rules.html#rule17">Rule 17</a> itself.</p>
 <p>Do remember that if your submission requires different filenames, then you
 <strong>MUST</strong> make a <strong>COPY</strong> of them in your <code>Makefile</code>. See also <a href="next/rules.html#rule11">Rule
 11</a>.</p>
-Jump to: <a href="#">top</a>
+<p>Jump to: <a href="#">top</a></p>
 <hr style="width:50%;text-align:left;margin-left:0">
 <hr style="width:50%;text-align:left;margin-left:0">
 <div id="submitting_help">
@@ -1896,7 +1897,7 @@ entries that do not win on their web page for everyone to see.</p>
 <div id="mkiocccentry_details">
 <h2 id="section-3-the-mkiocccentry-toolkit-finer-details">Section 3: The mkiocccentry toolkit: finer details</h2>
 </div>
-Jump to: <a href="#">top</a>
+<p>Jump to: <a href="#">top</a></p>
 <div id="mkiocccentry_process">
 <h3 id="q-3.0-what-is-the-mkiocccentry1-process-and-what-sort-of-checks-does-it-perform">Q 3.0: What is the <code>mkiocccentry(1)</code> process and what sort of checks does it perform?</h3>
 </div>
@@ -6503,6 +6504,7 @@ announced in the early years of the IOCCC.</p>
 <h3 id="q-11.6-i-do-not-understand-the-ioccc-can-you-explain-it-to-me">Q 11.6: I do not understand the IOCCC, can you explain it to me?</h3>
 </div>
 <p>Please see the <a href="about.html">About the IOCCC page</a> for more details.</p>
+<p>Jump to: <a href="#">top</a></p>
 <!--
 
     Copyright © 1984-2024 by Landon Curt Noll. All Rights Reserved.
diff --git a/faq.md b/faq.md
index ed867e1bf..51605ba1d 100644
--- a/faq.md
+++ b/faq.md
@@ -33,7 +33,7 @@ This is FAQ version **28.2.16 2025-03-12**.
 - **Q 1.10**: <a class="normal" href="#submission_dir">How can I avoid having to move or delete my submission directory for the same workdir?</a>
 
 
-## 2. [IOCCC Judging process](#judging_proceess)
+## 2. [IOCCC Judging process](#judging_process)
 - **Q 2.0**: <a class="normal" href="#questions">What is the best way to ask a question about the IOCCC rules, guideline and tools?</a>
 - **Q 2.1**: <a class="normal" href="#feedback">How can I comment or make a suggestion on IOCCC rules, guidelines and tools?</a>
 - **Q 2.2**: <a class="normal" href="#warnings">Are there any compiler warnings that I should not worry about in my submissions?</a>
@@ -154,6 +154,7 @@ Jump to: [top](#)
 
 # The IOCCC FAQ
 
+
 <hr style="width:50%;text-align:left;margin-left:0">
 <hr style="width:50%;text-align:left;margin-left:0">
 
@@ -163,6 +164,9 @@ Jump to: [top](#)
 </div>
 
 
+Jump to: [top](#)
+
+
 <div id="enter">
 <div id="step_0">
 <div id="step_1">
@@ -213,6 +217,7 @@ use it to package your submission. Not doing so puts you at a great risk of
 violating the [Rules](next/rules.html) and in particular [Rule
 17](next/rules.html#rule17).
 
+
 Jump to: [top](#)
 
 
@@ -261,6 +266,7 @@ for details on compiling and the
 FAQ on "[using mkiocccentry](#using_mkiocccentry)"
 for more details.
 
+
 Jump to: [top](#)
 
 
@@ -285,6 +291,7 @@ If you already have an mkiocccentry tool directory:
     git rebase
 ```
 
+
 Jump to: [top](#)
 
 
@@ -312,6 +319,7 @@ order you may. If you wish to skip that:
 
 Jump to: [top](#)
 
+
 <div id="install">
 ### Q 0.1.4: How do I install mkiocccentry(1) and related tools?
 </div>
@@ -322,8 +330,6 @@ and compiling the tools (see the
 FAQ on "[compiling mkiocccentry](#compiling_mkiocccentry)"
 above) run as either `sudo(8)` or root `make install`:
 
-
-
 ``` <!---sh-->
     # if you use sudo(8):
     sudo make install
@@ -332,7 +338,6 @@ above) run as either `sudo(8)` or root `make install`:
     make install
 ```
 
-
 If everything goes well you should be able to run `mkiocccentry(1)`,
 `txzchk(1)`, `chkentry(1)` and all the other installed tools from any directory,
 and the tools that rely on other tools will be able to find those required tools
@@ -341,8 +346,10 @@ from any directory too.
 Some tools like `bug_report.sh` and `hostchk.sh` are not meant to be installed
 and will not work from any directory, however.
 
+
 Jump to: [top](#)
 
+
 <div id="using_mkiocccentry">
 #### Q 0.1.5: How do I use mkiocccentry?
 </div>
@@ -409,6 +416,7 @@ contest.
 
 Jump to: [top](#)
 
+
 <div id="minimum_versions">
 #### Q 0.1.6: What are the minimum versions required for this contest?
 </div>
@@ -424,8 +432,8 @@ At minimum, the tools **MUST** be version:
 See also the
 FAQ on "[obtaining the latest release of the toolkit](#obtaining_mkiocccentry)".
 
-Jump to: [top](#)
 
+Jump to: [top](#)
 
 
 <div id="SUS">
@@ -441,6 +449,7 @@ system that conforms to the [SUS](https://en.wikipedia.org/wiki/Single_UNIX_Spec
 otherwise known as the [The Single UNIX Specification Version 4](https://unix.org/version4/)
 or [later SUS](https://unix.org/online.html).
 
+
 Jump to: [top](#)
 
 
@@ -482,6 +491,7 @@ compatible with this; see the
 FAQ on "[Makefile compatibility](#gmake)"
 for more details and help.
 
+
 #### Expected `make` rules:
 
 The following rules should exist in your Makefile:
@@ -512,8 +522,10 @@ date
 does have other rules like `everything` and `alt`, and we encourage you to use
 the one linked to above.
 
+
 Jump to: [top](#)
 
+
 <div id="remarks_md">
 <div id="remarks">
 <div id="readme">
@@ -575,6 +587,7 @@ rounds; we look at the author name only if an entry wins. See the
 use `mkiocccentry(1)`, as it requires it to not be of size 0, though if you only
 include whitespace you would still be violating [Rule 17](next/rules.html#rule17)).
 
+
 Jump to: [top](#)
 
 
@@ -613,7 +626,6 @@ FAQ on "[submission Makefiles](#makefile)".
 Jump to: [top](#)
 
 
-
 <div id="file_perms">
 ### Q 0.6: What permissions may my files be and what if I need different permissions?
 </div>
@@ -638,8 +650,9 @@ Do remember that if your submission requires different filenames, then you
 11](next/rules.html#rule11).
 
 
-
 Jump to: [top](#)
+
+
 <hr style="width:50%;text-align:left;margin-left:0">
 <hr style="width:50%;text-align:left;margin-left:0">
 
@@ -648,8 +661,8 @@ Jump to: [top](#)
 ## Section 1: Entering the IOCCC: more help and details
 </div>
 
-Jump to: [top](#)
 
+Jump to: [top](#)
 
 
 <div id="answers_file">
@@ -676,6 +689,7 @@ To make use of the answers file, use the `-i answers` option like:
     mkiocccentry -i answers.txt ...
 ```
 
+
 Jump to: [top](#)
 
 
@@ -732,6 +746,7 @@ For example:
     # Makefile continues below ...
 ```
 
+
 Jump to: [top](#)
 
 
@@ -756,6 +771,7 @@ as it lists things you **should NOT use** in markdown files and things you
 See the [markdown syntax](https://www.markdownguide.org/basic-syntax) guide.
 See also [CommonMark Spec](https://spec.commonmark.org/current/).
 
+
 Jump to: [top](#)
 
 
@@ -774,6 +790,7 @@ FAQ on "[reporting bugs and other issues in the mkiocccentry repo](https://githu
 in the [mkiocccentry repo](https://github.com/ioccc-src/mkiocccentry)
 for more thorough details on bug reporting.
 
+
 Jump to: [top](#)
 
 
@@ -795,6 +812,7 @@ FAQ on "[Rule 17](#rule17)",
 the [guidelines](next/guidelines.html) and [Rule 17](next/rules.html#rule17)
 itself.
 
+
 <div id="mkiocccentry_test">
 #### Q 1.5: How can I check if my submission passes tests without having to answer questions?
 </div>
@@ -884,8 +902,8 @@ You can do this by creating the tarball like:
     tar --format=v7 -cJf foo.txz directory
 ```
 
-Jump to: [top](#)
 
+Jump to: [top](#)
 
 
 <div id="ai">
@@ -904,6 +922,7 @@ ultimate author of the code you submit.
 If you do use such tools, **PLEASE mention** in your `remarks.md` which tools
 you used as well as how you used them to help write your submission.
 
+
 Jump to: [top](#)
 
 
@@ -911,6 +930,7 @@ Jump to: [top](#)
 ### Q 1.8: What are details behind Rule 17?
 </div>
 
+
 ### TL;DR Rule 17 - Use `mkiocccentry(1)`
 
 <p class="leftbar">
@@ -947,6 +967,7 @@ FAQ on "[what extra files are and how to include additional files](#extra-files)
 should you need to include more files than this maximum.
 </p>
 
+
 Jump to: [top](#)
 
 
@@ -1026,7 +1047,6 @@ about the submission itself. It also **MUST** be valid according to **BOTH**
 `jparse(3)` **AND** `chkentry(1)`.
 </p>
 
-
 <p class="leftbar">
 For the complete `mkiocccentry(1)` process, see the
 FAQ on the "[mkiocccentry process](#mkiocccentry_process)".
@@ -1081,7 +1101,6 @@ FAQs on "[obtaining, compiling, installing and using the mkiocccentry toolkit](#
 for more details.
 </p>
 
-
 <p class="leftbar">
 You are **HIGHLY ENCOURAGED** to use the `mkiocccentry(1)` tool to form your
 submission's xz compressed tarball. See the [guidelines on
@@ -1184,6 +1203,7 @@ These checks **MUST PASS**. If they do not you stand a significant chance of
 having your submission rejected for violating [Rule 17](next/rules.html#rule17)!
 </p>
 
+
 <div id="max-files">
 #### Maximum number of files per submission
 </div>
@@ -1328,12 +1348,13 @@ if your UUID was `test` (for test mode) you could do:
     mkiocccentry -U test workdir topdir
 ```
 
-
 See also the
 FAQ on "[the answers file](#answers_file)".
 
+
 Jump to: [top](#)
 
+
 <div id="submission_dir">
 ### Q 1.10: How can I avoid having to move or delete my submission directory for the same workdir?
 </div>
@@ -1352,8 +1373,10 @@ first so you do not have to do so.
 If for some reason your `rm` command cannot be found or does not exist you can
 specify the path by the `-r rm` option.
 
+
 Jump to: [top](#)
 
+
 <hr style="width:50%;text-align:left;margin-left:0">
 <hr style="width:50%;text-align:left;margin-left:0">
 
@@ -1362,6 +1385,7 @@ Jump to: [top](#)
 ## Section 2: IOCCC Judging process
 </div>
 
+
 Jump to: [top](#)
 
 
@@ -1422,6 +1446,7 @@ others are wondering about as well!
 See also the
 FAQ on "[rules, guidelines, tools feedback](#feedback)".
 
+
 Jump to: [top](#)
 
 
@@ -1450,6 +1475,7 @@ have to say, consider adding comments to that particular discussion.
 Otherwise consider opening a [new mkiocccentry
 discussion](https://github.com/ioccc-src/mkiocccentry/discussions/new/choose).
 
+
 Jump to: [top](#)
 
 
@@ -1479,6 +1505,7 @@ US** the OS, OS version, compiler and compiler version.
 For more details on why we use `-Weverything` in Clang see the FAQ on
 "[-Weverything](#weverything)".
 
+
 Jump to: [top](#)
 
 
@@ -1611,6 +1638,7 @@ FAQ on "[remarks.md](#remarks_md)",
 submitted theme** and **how compares with previous IOCCC winners**
 of the same theme.
 
+
 Jump to: [top](#)
 
 
@@ -1633,6 +1661,7 @@ In some cases the entry may have abused rule 2 and declared an
 "abuse of the rules" (although now blatant abuse of the rules to
 get around rule 2 size limits is discouraged).
 
+
 Jump to: [top](#)
 
 
@@ -1644,6 +1673,7 @@ Jump to: [top](#)
 
 By tradition, we do not say.
 
+
 Jump to: [top](#)
 
 
@@ -1667,6 +1697,7 @@ SUS-conforming. See the
 FAQ on "[SUS](#SUS)"
 for more information.
 
+
 Jump to: [top](#)
 
 
@@ -1686,6 +1717,7 @@ also report when we enter what we believe is the final judging round, so you may
 guess that we have at least 3 rounds.  :-)  The actual number of rounds is
 certainly more than 3.
 
+
 Jump to: [top](#)
 
 
@@ -1730,7 +1762,6 @@ Starting from 1988, the entry we liked the most in that year is called
 - [2018/mills](2018/mills/index.html)
 - [2020/carlini](2020/carlini/index.html)
 
-
 In 1993, 1994 and 1995 the judges were unable to select a clear overall
 winning entry. So to give a nod to the entry that had the highest approval ranking
 from the judges, they used the following awards:
@@ -1742,6 +1773,7 @@ from the judges, they used the following awards:
 These could be considered the '`best entry`' for those years with 1 or
 more other entries that came in close behind.
 
+
 Jump to: [top](#)
 
 
@@ -1775,6 +1807,7 @@ winning entries page](years.html). This is done by updating this repo.
 
 * Update the [IOCCC news](news.html) page, also by updating this repo.
 
+
 Jump to: [top](#)
 
 
@@ -1788,8 +1821,10 @@ Because the publication on the IOCCC site **_IS_** the award!
 Anyone is free to put their IOCCC hopefuls, lookalikes and/or
 entries that do not win on their web page for everyone to see.
 
+
 Jump to: [top](#)
 
+
 <hr style="width:50%;text-align:left;margin-left:0">
 <hr style="width:50%;text-align:left;margin-left:0">
 
@@ -1800,6 +1835,8 @@ Jump to: [top](#)
 
 
 Jump to: [top](#)
+
+
 <div id="mkiocccentry_process">
 ### Q 3.0: What is the `mkiocccentry(1)` process and what sort of checks does it perform?
 </div>
@@ -2018,7 +2055,6 @@ Some of the other checks that are made:
 - If the `Makefile` does not have a `clobber` rule.
 - If the `Makefile` does not have a `try` rule.
 
-
 Conditions that one **MUST** correct, and which `mkiocccentry(1)` will prompt until
 they are correct, are:
 
@@ -2093,6 +2129,7 @@ Finally, if you wish to not have to enter the same answers just to update a
 submission, see the
 FAQ on the "[answers file feature](#answers_file)".
 
+
 Jump to: [top](#)
 
 
@@ -2133,6 +2170,7 @@ of this document to discuss the many tests that `txzchk(1)` runs; if you must
 know we refer you to the [source
 code](https://github.com/ioccc-src/mkiocccentry/blob/master/txzchk.c).
 
+
 Jump to: [top](#)
 
 
@@ -2162,6 +2200,7 @@ See also the
 FAQ on "[validating your submission tarball](#txzchk)"
 for more information.
 
+
 Jump to: [top](#)
 
 
@@ -2205,7 +2244,6 @@ As an example, if your submission directory is
 `00000000-0000-4000-0000-000000000000-3/` then you should run the following
 command:
 
-
 ``` <!---sh-->
     chkentry 00000000-0000-4000-0000-000000000000-3
 ```
@@ -2228,6 +2266,7 @@ and the
 FAQ on "[.info.json](#info_json)"
 as well as [Rule 17](next/rules.html#rule17) for more information.
 
+
 Jump to: [top](#)
 
 
@@ -2504,6 +2543,7 @@ things too).
 If you wish to **verify** that your `.auth.json` file is valid **JSON** then see the
 FAQ on "[validating JSON documents](#validating_json)".
 
+
 Jump to: [top](#)
 
 
@@ -2933,6 +2973,7 @@ because `chkentry` would not validate the `.info.json` file.
 If you wish to **verify** that your `.info.json` file is valid **JSON** then see the
 FAQ on "[validating JSON documents](#validating_json)".
 
+
 Jump to: [top](#)
 
 
@@ -3002,6 +3043,7 @@ Anonymous `author_handle`'s match this regexp:
     Anonymous_[0-9][0-9][0-9][0-9][.0-9]*$
 ```
 
+
 Jump to: [top](#)
 
 
@@ -3476,6 +3518,8 @@ For example:
 
 
 ##### winning_entry_set
+
+
 ##### entry_id
 
 ``` <!---json-->
@@ -3558,6 +3602,7 @@ FAQ on "[fixing author information](#fix_author)"
 for information about how to update
 and/or correct IOCCC author information.
 
+
 Jump to: [top](#)
 
 
@@ -3603,6 +3648,7 @@ See
 FAQ on "[Author, Entry, Submission](#terms)"
 for more information on terms such as _author_, _entry_, and _submission_.
 
+
 Jump to: [top](#)
 
 
@@ -3621,6 +3667,7 @@ of 2020 is found under the directory
 
 The `entry_id` for that winning entry is `2020_ferguson2`.
 
+
 Jump to: [top](#)
 
 
@@ -3765,6 +3812,7 @@ As of _Fri 26 Jul 2024 17:29:15 UTC_, it contains:
 We now will walk through the above JSON document looking at all the JSON
 members:
 
+
 ##### `no_comment`
 
 ``` <!--- json-->
@@ -3778,6 +3826,7 @@ be present in all IOCCC related JSON files.
 There **MUST** be one and only one `no_comment` _JSON member_ and the _JSON value_ **MUST**
 be the exact _JSON string_ as shown above.
 
+
 ##### `entry_JSON_format_version`
 
 ``` <!---json-->
@@ -3796,6 +3845,7 @@ of the these files is modified: and then only those who maintain the
 [official IOCCC website](https://www.ioccc.org) would be the one to do this
 in conjunction with changes to [bin directory tools](bin/index.html).
 
+
 ##### `award`
 
 ``` <!---json-->
@@ -3805,6 +3855,7 @@ in conjunction with changes to [bin directory tools](bin/index.html).
 This JSON string is the award title of the entry which the [Judges](judges.html)
 decide/decided when it becomes/became a winning entry.
 
+
 ##### `year`
 
 ``` <!---json-->
@@ -3813,6 +3864,7 @@ decide/decided when it becomes/became a winning entry.
 
 This JSON number is the year the contest ran, ended or was announced in.
 
+
 ##### `dir`
 
 ``` <!---json-->
@@ -3824,6 +3876,7 @@ in this case [1984](1984/index.html). With the above member, `year`, and this
 one, one can determine the directory of the entry, here being
 [1984/laman](1984/laman/index.html).
 
+
 ##### `entry_id`
 
 ``` <!---json-->
@@ -3902,6 +3955,7 @@ a change of `author_handle` _JSON value_ would also require the
 The full name of an author may use non-ASCII characters so long as the
 full name is properly encoded as a _JSON string_.
 
+
 ##### `manifest`
 
 Finally there is the manifest JSON **array** that lists the files of the winning
@@ -3927,7 +3981,6 @@ A shortened manifest for our example entry is:
     ]
 ```
 
-
 Now we will describe each field of each file in the manifest:
 
 - `file_path` (string)
@@ -4119,7 +4172,6 @@ will depend on the year).
     `entry_text` is always `"this web page"` and its `file_path` is **ALWAYS**
     `"index.html"`.
 
-
 If the entry has an alternate source code file, often it will be in the form of
 `"winner.alt.c"` or `"prog.alt.c"`; this is also what the `file_path` will be.
 The `entry_text` will typically (not always but almost always) be `"alternate
@@ -4131,8 +4183,8 @@ source code (if there is an alternate version). Some, however, have another file
 name. The `entry_text` for the `try` scripts will be `script to try entry` or
 something along those lines.
 
-Jump to: [top](#)
 
+Jump to: [top](#)
 
 
 <div id="validating_json">
@@ -4164,7 +4216,6 @@ repo](https://github.com/ioccc-src/mkiocccentry):
 
 The syntax of `jparse(1)` is very simple:
 
-
 ``` <!--sh-->
     jparse foo.json
 ```
@@ -4188,6 +4239,7 @@ install via the `mkiocccentry` repo because it has the dependencies built in,
 and because the `mkiocccentry` copy is that which is used by the current IOCCC,
 as the two can be different at times.
 
+
 Jump to: [top](#)
 
 
@@ -4199,6 +4251,7 @@ Jump to: [top](#)
 ## Section 4: Compiling IOCCC entries
 </div>
 
+
 Jump to: [top](#)
 
 
@@ -4264,6 +4317,7 @@ compilers might do different things, have different defects or other issues.
 Note that the `Makefile`s check the `CC` variable by substrings so that if you
 were to do something like `make CC=gcc=mp-12` it would register as `gcc`.
 
+
 Jump to: [top](#)
 
 
@@ -4303,8 +4357,10 @@ it like:
 
 though of course for both you may specify a rule or rules to run.
 
+
 Jump to: [top](#)
 
+
 <hr style="width:50%;text-align:left;margin-left:0">
 <hr style="width:50%;text-align:left;margin-left:0">
 
@@ -4313,6 +4369,7 @@ Jump to: [top](#)
 ## Section 5: Dependencies for some IOCCC entries
 </div>
 
+
 Jump to: [top](#)
 
 
@@ -4359,7 +4416,6 @@ According to this [Linux for Devices tutorial on
 XOrg](https://www.linuxfordevices.com/tutorials/linux/install-xorg-on-linux) as
 of 2023 Mar 25 (quote verbatim):
 
-
 > Recently, RHEL developers categorized Xorg [Xorg was put in the ‘deprecated’
 software](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/9/html/9.0_release_notes/deprecated_functionality),
 as its development has mostly halted. Subsequent updates will completely replace
@@ -4375,7 +4431,6 @@ See the [Wayland](https://wayland.freedesktop.org) website for more details.
 **Wayland**.  Some IOCCC entries that use X11 might be OK while other IOCCC
 entries that use X11 in an unusual way might fail under **Wayland**.
 
-
 See the [Wayland FAQ](https://wayland.freedesktop.org/faq.html) for more
 information.
 
@@ -4533,6 +4588,7 @@ See the
 FAQ on "[X.org deprecated](#Xorg_deprecated)"
 for more information.
 
+
 Jump to: [top](#)
 
 
@@ -4658,6 +4714,7 @@ See the
 FAQ on "[GitHub pull request](#pull_request)"
 for more information about pull requests.
 
+
 Jump to: [top](#)
 
 
@@ -4725,6 +4782,7 @@ for downloading, installing and using ncurses.
 
 We recommend trying a method suitable for your environment first, if possible.
 
+
 Jump to: [top](#)
 
 
@@ -4741,6 +4799,7 @@ install depends on your OS. See below.
 After it is installed, you should be able to compile and use the program as
 described in the index.html file.
 
+
 #### Red Hat based Linux
 
 As root or via sudo:
@@ -4749,10 +4808,12 @@ As root or via sudo:
     dnf install -y sox sox-devel
 ```
 
+
 #### macOS
 
 For macOS there are two well known options.
 
+
 ##### macOS via Homebrew
 
 If you have not already done so, install [Homebrew](https://brew.sh).
@@ -4819,6 +4880,7 @@ Then as root or via `sudo(1)` enter:
 That will install it to `/usr/local/bin`. Now you should be able to use the
 entry in question.
 
+
 Jump to: [top](#)
 
 
@@ -4899,6 +4961,7 @@ for downloading, installing and using netpbm.
 
 We recommend trying a method suitable for your environment first, if possible.
 
+
 Jump to: [top](#)
 
 
@@ -4978,6 +5041,7 @@ for downloading, installing and using libjpeg-turbo.
 
 We recommend trying a method suitable for your environment first, if possible.
 
+
 Jump to: [top](#)
 
 
@@ -5057,6 +5121,7 @@ for downloading, installing and using ImageMagick.
 
 We recommend trying a method suitable for your environment first, if possible.
 
+
 Jump to: [top](#)
 
 
@@ -5145,8 +5210,8 @@ for downloading, installing and using OpenGL.
 
 We recommend trying a method suitable for your environment first, if possible.
 
-Jump to: [top](#)
 
+Jump to: [top](#)
 
 
 <div id="zlib">
@@ -5213,6 +5278,7 @@ for downloading, installing and using zlib.
 
 We recommend trying a method suitable for your environment first, if possible.
 
+
 Jump to: [top](#)
 
 
@@ -5223,6 +5289,7 @@ Jump to: [top](#)
 Please see the [official Ruby installation
 guide](https://www.ruby-lang.org/en/documentation/installation/).
 
+
 Jump to: [top](#)
 
 
@@ -5253,8 +5320,10 @@ Once this is done, try as root or via `sudo`:
     gem install rake
 ```
 
+
 Jump to: [top](#)
 
+
 <hr style="width:50%;text-align:left;margin-left:0">
 <hr style="width:50%;text-align:left;margin-left:0">
 
@@ -5263,6 +5332,7 @@ Jump to: [top](#)
 ## Section 6: Problems compiling IOCCC entries
 </div>
 
+
 Jump to: [top](#)
 
 
@@ -5323,6 +5393,7 @@ See the
 FAQ on "[original source code](#original_source_code)"
 for more information.
 
+
 Jump to: [top](#)
 
 
@@ -5345,6 +5416,7 @@ Please see the
 FAQ on "[fixing an entry](#fix_an_entry)"
 for details.
 
+
 Jump to: [top](#)
 
 
@@ -5406,8 +5478,10 @@ a defect of `clang` that required numerous entries to be fixed for clang is that
 requires that `main()`'s arguments to be of a specific type. However some
 versions of `clang` are more strict in the number of args allowed.
 
+
 Jump to: [top](#)
 
+
 <hr style="width:50%;text-align:left;margin-left:0">
 <hr style="width:50%;text-align:left;margin-left:0">
 
@@ -5416,6 +5490,7 @@ Jump to: [top](#)
 ## Section 7: Running IOCCC entries
 </div>
 
+
 Jump to: [top](#)
 
 
@@ -5441,6 +5516,7 @@ and there are some other benefits as well which you would miss if you did not
 use them. Nevertheless, if you prefer to do it manually, whether to help you
 process or appreciate the entry more, then please do so.
 
+
 Jump to: [top](#)
 
 
@@ -5460,6 +5536,7 @@ usually away with `stty echo`. Sometimes you can also get away with `stty sane`.
 clearing of the screen, however, that solves the problem, so `clear` will not
 help.
 
+
 Jump to: [top](#)
 
 
@@ -5506,8 +5583,10 @@ Please see the
 FAQ on "[fixing an entry](#fix_an_entry)"
 for how to submit a fix to an IOCCC entry.
 
+
 Jump to: [top](#)
 
+
 <div id="64bit">
 <div id="64-bit">
 <div id="32bit">
@@ -5547,8 +5626,10 @@ for details.  See also the
 FAQ on "[GitHub pull request](#pull_request)"
 for more information about pull requests.
 
+
 Jump to: [top](#)
 
+
 <div id="eof">
 <div id="intr">
 <div id="interrupt">
@@ -5586,8 +5667,10 @@ to find what the `intr` is set to:
 reason it's not you might have to do something else including just piping it to
 just `grep intr` or whatever.
 
+
 Jump to: [top](#)
 
+
 <div id="entry_downloads">
 <div id="download">
 ### Q 7.4: How do I download individual winning entries or all winning entries of a given year?
@@ -5703,8 +5786,8 @@ browser to `1984/index.html`, scroll down to `Winning Entries of 1984 - The 1st
 IOCCC` and click on the link `1984/mullender` which will take you to the
 `index.html` file. Of course the caveats listed above still will apply.
 
-Jump to: [top](#)
 
+Jump to: [top](#)
 
 
 <hr style="width:50%;text-align:left;margin-left:0">
@@ -5715,6 +5798,7 @@ Jump to: [top](#)
 ## Section 8: Changes made to IOCCC entries
 </div>
 
+
 Jump to: [top](#)
 
 
@@ -5763,7 +5847,6 @@ The following `make` rules exist to make a difference:
     - This rule will show the diff of the entry to the original code (that is
     `entry.c` to `entry.orig.c`).
 
-
 For instance one of Landon's all time favourite entries is
 [1984/mullender](1984/mullender/index.html) so the file names would be:
 `mullender.orig.c`, `mullender.alt.c` and `mullender.c`. For later years, it
@@ -5851,6 +5934,7 @@ See the
 FAQ on "[original source code files](#original_source_code)"
 for more information.
 
+
 Jump to: [top](#)
 
 
@@ -5875,7 +5959,6 @@ warning in such a way that caused confusing output for the entry, looking like:
     # nothing here, what to do?
 ```
 
-
 In some cases it is not possible to fix or at least it is highly unlikely and so
 those have mainly not been touched except one that has had the buffer size
 increased (which could be done for others that are not possible to change to
@@ -5903,6 +5986,7 @@ We're not sure how this is compatibility but either way it can cause a
 problem and it is this that has complicated most of the fixes though again some
 can look almost identical.
 
+
 Jump to: [top](#)
 
 
@@ -5932,6 +6016,7 @@ and the
 FAQ on "[entry source code changes](#what_changed)"
 for more information.
 
+
 Jump to: [top](#)
 
 
@@ -5944,6 +6029,7 @@ are the original winning entry or as close to as possible to the original that
 we can find (in some cases a change was made by the Judges, for example, or an
 author might have made a modification without saving the original).
 
+
 Jump to: [top](#)
 
 
@@ -5982,6 +6068,7 @@ See also the
 FAQ on "[original source code](#original_source_code)"
 for more information.
 
+
 Jump to: [top](#)
 
 
@@ -6006,6 +6093,7 @@ could no longer be so: `main()` instead had to call another function that has
 the body of the old `main()` and that function would call itself again. In some
 cases, however, this had to be done even without `clang` objections.
 
+
 Jump to: [top](#)
 
 
@@ -6043,6 +6131,7 @@ In a few cases files were removed and there are multiple reasons for this too.
 The end result is to help improve the presentation of the entries in some way or
 ways.
 
+
 Jump to: [top](#)
 
 
@@ -6096,6 +6185,7 @@ for more information on changes. If you want to see more details, including how
 to see the actual differences, see the
 FAQ on "[what changed in more detail](#detailed-diff)".
 
+
 Jump to: [top](#)
 
 
@@ -6125,8 +6215,10 @@ other times something else.
 
 There were certainly other reasons as well.
 
+
 Jump to: [top](#)
 
+
 <hr style="width:50%;text-align:left;margin-left:0">
 <hr style="width:50%;text-align:left;margin-left:0">
 
@@ -6135,6 +6227,7 @@ Jump to: [top](#)
 ## Section 9: Helping the IOCCC
 </div>
 
+
 Jump to: [top](#)
 
 
@@ -6144,6 +6237,7 @@ Jump to: [top](#)
 </div>
 </div>
 
+
 #### We welcome your help in fixing IOCCC entries
 
 The [known bugs](bugs.html) file, order by IOCCC years, contains a
@@ -6160,6 +6254,7 @@ while a (mis)feature is not considered a bug and should **not be fixed**.
 In cases where the bug is known, the entry's [known bugs](bugs.html) file
 section may offer you important fixing clues.
 
+
 #### We welcome your help on fixing the IOCCC website
 
 This includes typos, dead/invalid links and many other things. Please see the
@@ -6185,6 +6280,7 @@ Note that just because an entry is not in the bugs file does not mean there is
 not an issue and note that some issues are simply missing files, dead URL(s) or
 something like that.
 
+
 Jump to: [top](#)
 
 
@@ -6238,6 +6334,7 @@ for more information about pull requests.
 Note that we're much more inclined to accept an author's fixes but the judges
 have the final say in the matter.
 
+
 Jump to: [top](#)
 
 
@@ -6269,6 +6366,7 @@ To help you out here is a navigation menu in this FAQ entry:
 Go to [GitHub](https://github.com/) and click on 'Sign up'. Follow the
 instructions. Once you've completed this task make sure you log in to GitHub.
 
+
 #### Installing an ssh key to GitHub
 
 Assuming you do not have an ssh key you should go to the command prompt and
@@ -6300,6 +6398,7 @@ it might be `~/.ssh/github.pub`.
 Whatever the key file is, copy the contents and paste it into the GitHub field
 labelled _Key_. Once you have done so click on _Add SSH key_.
 
+
 #### Forking the IOCCC winner repo
 
 Open in your browser the link:
@@ -6355,6 +6454,7 @@ where _foo_ is the file to add.
 When he's ready to make a commit he would need to create a new branch for the
 pull request.
 
+
 #### Committing your changes
 
 First, as an aside, if this is your first pull request (which we assume is if you're
@@ -6372,7 +6472,6 @@ Cody would see:
 Now, assuming that the forked repo is
 <https://github.com/xexyl/winner>, you'd type:
 
-
 ``` <!---sh-->
     git remote set-url origin git@github.com:xexyl/winner.git
 ```
@@ -6383,7 +6482,6 @@ Before doing anything else, however, a new branch needs to be created.
 Continuing the example above for
 [2020/ferguson1/play.sh](%%REPO_URL%%/2020/ferguson1/play.sh), it might be that:
 
-
 ``` <!---sh-->
     git checkout -B human-snakes
 ```
@@ -6492,6 +6590,7 @@ example, you would type:
 
 This will merge your pull request to your fork.
 
+
 Jump to: [top](#)
 
 
@@ -6523,6 +6622,7 @@ already been reported.  If it has been reported, feel free to add a comment to
 the issue. Otherwise, if you do not see the same issue reported, then feel free
 to [open a new IOCCC website issue](https://github.com/ioccc-src/winner/issues/new?assignees=&labels=website&projects=&template=website_issue.yml&title=%5BWebsite%5D+%3Ctitle%3E).
 
+
 Jump to: [top](#)
 
 
@@ -6737,6 +6837,7 @@ See the
 FAQ on "[fixing author information](#fix_author)"
 for information about how to change author location codes.
 
+
 Jump to: [top](#)
 
 
@@ -6792,6 +6893,7 @@ replace that text with:
 If you just wish to report the bad link issue, see
 FAQ on "[report website problem](#report_web_problem)".
 
+
 Jump to: [top](#)
 
 
@@ -6816,6 +6918,7 @@ If you wish to express your support and/or appreciation for our
 efforts, we suggest making an **Anonymous** gift via the
 [IOCCC Amazon wishlist](https://www.amazon.com/hz/wishlist/ls/3HSNTEL8RQ1M0?ref_=wl_share).
 
+
 Jump to: [top](#)
 
 
@@ -6913,6 +7016,7 @@ that be prove helpful.
 
 **THANK YOU** in advance for your willingness to assist!
 
+
 Jump to: [top](#)
 
 
@@ -6943,8 +7047,10 @@ IOCCC entry.  See also the
 FAQ on "[GitHub pull request](#pull_request)"
 for more information about pull requests.
 
+
 Jump to: [top](#)
 
+
 <hr style="width:50%;text-align:left;margin-left:0">
 <hr style="width:50%;text-align:left;margin-left:0">
 
@@ -6953,6 +7059,7 @@ Jump to: [top](#)
 ## Section 10: Miscellaneous IOCCC
 </div>
 
+
 Jump to: [top](#)
 
 
@@ -6989,6 +7096,7 @@ and certainly **OUT OF DATE**.
 If you do make a new fork of **THIS** repo, we do ask that your fork keep up to
 date with the latest changes when possible. Thank you.
 
+
 Jump to: [top](#)
 
 
@@ -7014,6 +7122,7 @@ See
 FAQ on "[using IOCCC content](#license)".
 For additional information on the [Copyright and CC BY-SA 4.0 License](license.html).
 
+
 Jump to: [top](#)
 
 
@@ -7061,6 +7170,7 @@ p.s. Here is an image of F. D. C. Willard:
  alt="image of F.D.C.Willard.png"
  width=600 height=401>
 
+
 Jump to: [top](#)
 
 
@@ -7094,6 +7204,7 @@ The .top, .allyear, .year and .path files are generated from the top level Makef
     make genpath
 ```
 
+
 Jump to: [top](#)
 
 
@@ -7157,6 +7268,7 @@ such as old rules and old guidelines, terms such as _entry_ may still be
 found.  Moreover, out of habit, the IOCCC judges sometimes use old
 names such as _entry_ when they should use _submission_.  Sorry (tm Canada)! 🇨🇦:-)
 
+
 Jump to: [top](#)
 
 
@@ -7194,6 +7306,7 @@ enjoy that those working on the IOCCC have proper Attribution
 including, of course, the IOCCC winners themselves!  It is designed
 to help ensure that everyone may enjoy the IOCCC.
 
+
 Jump to: [top](#)
 
 
@@ -7233,6 +7346,7 @@ follow posts something so you will have to check the IOCCC feed manually.
 mastodon feed](https://fosstodon.org/@ioccc) page and/or mastodon
 app from time to time to view IOCCC mastodon updates.
 
+
 Jump to: [top](#)
 
 
@@ -7252,6 +7366,7 @@ can hit ESC to do this) and then type the command:
 
 where `4` is the value you wish to set the tabstop to.
 
+
 Jump to: [top](#)
 
 
@@ -7259,6 +7374,7 @@ Jump to: [top](#)
 ### Q 10.8: How do the menus on the website work and what can I do if they don't work?
 </div>
 
+
 <div id="desktop_menu">
 #### Menu on desktops or laptop computers
 </div>
@@ -7294,7 +7410,6 @@ For instance, on an iPhone 14
 Pro Max or similar device (in dimensions), you should see at the top right of
 every page, something that looks like:
 
-
 <img src="png/ioccc-menu-mobile-phone.png"
  alt="screenshot of IOCCC menu on iPhone 14 Pro Max"
  width=1290 height=527>
@@ -7307,6 +7422,7 @@ In this case click on the icon at the top right corner that looks like:
 
 to activate the menu.
 
+
 <div id="no_javascript_menu">
 ##### Menu on mobile devices if JavaScript is disabled
 </div>
@@ -7323,6 +7439,7 @@ menu](nojs-menu.html) which is a plaintext menu. You of course can use this if
 you like, even if you do not have JavaScript enabled, by pointing your browser
 to <https://www.ioccc.org/nojs-menu.html>.
 
+
 <div id="tablet_menu">
 ##### Menus on tablet devices (e.g. iPads)
 </div>
@@ -7373,6 +7490,7 @@ least [report it as an
 issue](https://github.com/ioccc-src/winner/issues/new/choose) (choose
 the category _Website issue_).
 
+
 Jump to: [top](#)
 
 
@@ -7398,6 +7516,7 @@ Of course if you know the author's name you can go directly to
 [authors.html](authors.html) and click on their surname's/last name's/second
 name's initial and then scroll down (if necessary) to the author in question.
 
+
 Jump to: [top](#)
 
 
@@ -7410,6 +7529,7 @@ longer be available, code wise, except for Plan 9, but Plan 9 was never used for
 judging the IOCCC. A Unix man page for `cb`
 [still exists](https://www.ibm.com/docs/en/aix/7.3?topic=c-cb-command).
 
+
 Jump to: [top](#)
 
 
@@ -7626,6 +7746,7 @@ Jump to: [top](#)
 </div>
 </div>
 
+
 Jump to: [top](#)
 
 
@@ -7722,6 +7843,7 @@ P.S. Part of the inspiration for making the IOCCC a contest goes to the
 reference to that (in)famous dark and stormy night all the way back in 1830 when
 Landon was just a wee lad).
 
+
 Jump to: [top](#)
 
 
@@ -7741,6 +7863,7 @@ and the website generation) and the JSON parser (for the tools, the contest and
 the website) to make it easier and much more likely for the IOCCC to be held on
 a yearly basis.
 
+
 Jump to: [top](#)
 
 
@@ -7750,6 +7873,7 @@ Jump to: [top](#)
 </div>
 </div>
 
+
 #### In the beginning of www.ioccc.org
 
 The long history of the [official IOCCC website](https://www.ioccc.org) can be
@@ -7766,6 +7890,7 @@ repo](https://web.archive.org/web/20210101211346/https://www.ioccc.org/) on
 site](https://www.ioccc.org) became a [GitHub Pages](https://pages.github.com)
 website.
 
+
 #### 2020 Dec 28 bzip2 compressed tarball archive
 
 Furthermore, a bzip2 compressed tarball containing the released
@@ -7948,6 +8073,7 @@ and the [Pull Request 24 in the winner repo](https://github.com/ioccc-src/winner
 The **Great Fork Merge** _changed 5,157 files_ with _843,045 additions_ and _137,758
 deletions_, in _6,169 commits_ ‼️
 
+
 Jump to: [top](#)
 
 
@@ -7964,6 +8090,7 @@ In later years, Rule 2 was split into two parts.  These two parts of Rule 2 are:
 * Rule 2a: Overall size limit of "prog.c"
 * Rule 2b: Size of "prog.c", w/o counting certain types of characters
 
+
 <div id="size_rule1984-1985">
 #### IOCCC 1984-1985
 </div>
@@ -7973,6 +8100,7 @@ In later years, Rule 2 was split into two parts.  These two parts of Rule 2 are:
 * Rule 2a: 512
 * Rule 2b: n/a
 
+
 <div id="size_rule1986-1987">
 #### IOCCC 1986-1987
 </div>
@@ -7982,6 +8110,7 @@ In later years, Rule 2 was split into two parts.  These two parts of Rule 2 are:
 * Rule 2a: 1024
 * Rule 2b: n/a
 
+
 <div id="size_rule1988-1991">
 #### IOCCC 1988-1991
 </div>
@@ -7991,6 +8120,7 @@ In later years, Rule 2 was split into two parts.  These two parts of Rule 2 are:
 * Rule 2a: 1536
 * Rule 2b: n/a
 
+
 <div id="size_rule1992-2000">
 #### IOCCC 1992-2000
 </div>
@@ -7998,6 +8128,7 @@ In later years, Rule 2 was split into two parts.  These two parts of Rule 2 are:
 * Rule 2a: 3217
 * Rule 2b: 1536
 
+
 <div id="size_rule2001-2012">
 #### IOCCC: 2001-2012
 </div>
@@ -8005,6 +8136,7 @@ In later years, Rule 2 was split into two parts.  These two parts of Rule 2 are:
 * Rule 2a: 4096
 * Rule 2b: 2048
 
+
 <div id="size_rule2013-2020">
 #### IOCCC 2013-2020
 </div>
@@ -8012,6 +8144,7 @@ In later years, Rule 2 was split into two parts.  These two parts of Rule 2 are:
 * Rule 2a: 4096
 * Rule 2b: 2053
 
+
 <div id="size_rule2024-xxxx">
 #### IOCCC 2024-date
 </div>
@@ -8019,6 +8152,7 @@ In later years, Rule 2 was split into two parts.  These two parts of Rule 2 are:
 * Rule 2a: 4993
 * Rule 2b: 2503
 
+
 Jump to: [top](#)
 
 
@@ -8035,6 +8169,7 @@ See the
 FAQ on "[Great Fork Merge Date](#great_fork_merge_date)"
 for more information and stats.
 
+
 Jump to: [top](#)
 
 
@@ -8050,6 +8185,7 @@ general [USENIX conference](https://www.usenix.org/conferences), usually
 immediately after the BSD BOF, where the winners of a new IOCCC were
 announced in the early years of the IOCCC.
 
+
 Jump to: [top](#)
 
 
@@ -8060,6 +8196,9 @@ Jump to: [top](#)
 Please see the [About the IOCCC page](about.html) for more details.
 
 
+Jump to: [top](#)
+
+
 <!--
 
     Copyright © 1984-2024 by Landon Curt Noll. All Rights Reserved.
diff --git a/news.html b/news.html
index 0cfe22e9b..86b5524ab 100644
--- a/news.html
+++ b/news.html
@@ -434,7 +434,21 @@ for more information on Mastodon.</p>
 <h3 id="ioccc-discord-community">IOCCC Discord Community</h3>
 <p>We invite you to join the <strong>IOCCC Discord Community</strong> via this link: <a href="https://discord.gg/Wa42Qujwnw">https://discord.gg/Wa42Qujwnw</a></p>
 <h1 id="news">News</h1>
-<h2 id="section">2025-03-05</h2>
+<h2 id="section">2025-03-12</h2>
+<p>We released <a href="https://github.com/ioccc-src/mkiocccentry">mkiocccentry toolkit</a> <strong>version 2.4.3 2025-03-11</strong>.</p>
+<p>While you are <strong>NOT</strong> required to use this release in order to submit to <strong>IOCCC28</strong>,
+we do <strong>RECOMMEND</strong> that you <strong>install and use</strong> it, because among other things, it provides:</p>
+<ul>
+<li><code>mkiocccentry(1)</code> and <code>txzchk(1)</code> now search for other toolkit tools using <code>$PATH</code></li>
+<li><code>mkiocccentry(1)</code> and <code>chkentry(1)</code> are now less strict with most <code>iocccsize(1)</code> warnings</li>
+<li><code>mkiocccentry -x</code> will force the overwriting of the submission directory it forms under <code>workdir</code></li>
+<li><code>mkiocccentry -U uuid</code> and <code>mkiocccentry -u uuid_file</code> let you set your username</li>
+</ul>
+<p>See the <a href="https://github.com/ioccc-src/mkiocccentry/releases/tag/2.4.3">version 2.4.3 release notes</a>
+for more details.</p>
+<p><strong>Clarification</strong>: <strong>NUL bytes</strong> are <strong>ALLOWED</strong> in your submission <code>prog.c</code> and related C code.</p>
+<p>Please mention in your <code>remarks.md</code> file if your C source contains <strong>NUL bytes</strong>.</p>
+<h2 id="section-1">2025-03-05</h2>
 <p>The <a href="faq.html#ioccc_start">40th anniversary of the IOCCC</a>, <strong>IOCCC28</strong>, will be <strong>open</strong> for
 submissions from <strong>2025-03-05 23:19:17.131107 UTC</strong> to <strong>2025-06-05 04:03:02.010099 UTC</strong>.</p>
 <p>Version <strong>28.30 2025-03-03</strong> of the <a href="next/rules.html">IOCCC28 rules</a>,
@@ -454,13 +468,13 @@ and initial password by email. If you cannot find that email, contact the
 <a href="contact.html#if-you-really-need-to-send-email-the-ioccc-judges">IOCCC Judges by email</a>
 for help. We have given early registrants extra time (until <strong>2025 Mar 12 UTC</strong>), to login
 and change their initial password.</p>
-<h2 id="section-1">2025-02-28</h2>
+<h2 id="section-2">2025-02-28</h2>
 <p>We have reached our <strong>code freeze</strong> milestone for the <a href="https://github.com/ioccc-src/mkiocccentry">mkiocccentry repo</a> and released a new version of the <a href="faq.html#mkiocccentry">mkiocccentry toolkit</a>!</p>
 <p>Final testing is going well. We remain on track to open the <strong>IOCCC28</strong> on <strong>2025-03-05 23:19:17.131107 UTC</strong>.</p>
 <p>In a few days, those <a href="https://www.ioccc.org/next/register.html">registered for IOCCC28</a> will receive email with their username and initial password to <a href="https://submit.ioccc.org">submit their code</a>.</p>
 <p>We encourage those who wish to enter the <strong>IOCCC28</strong> to <a href="https://www.ioccc.org/next/register.html">registered for IOCCC28</a> today.</p>
 <p>Consider joining the IOCCC discord community via this link: <a href="https://discord.gg/Wa42Qujwnw">https://discord.gg/Wa42Qujwnw</a></p>
-<h2 id="section-2">2025-02-12</h2>
+<h2 id="section-3">2025-02-12</h2>
 <p>We have discovered an issue that needs to be resolved, followed by more testing
 after the code freeze. We also want to improve the <a href="next/guidelines.html">IOCCC28 guidelines</a>,
 and to simplify the write-up of the <a href="next/rules.html">IOCCC28 rules</a>.</p>
@@ -468,7 +482,7 @@ and to simplify the write-up of the <a href="next/rules.html">IOCCC28 rules</a>.
 on <strong>2024-12-29 23:58:13.213455 UTC</strong>, is now scheduled to be <strong>open</strong>
 from <strong>2025-03-05 23:19:17.131107 UTC</strong> to <strong>2025-06-05 04:03:02.010099 UTC</strong>.
 We apologize for this delay.</p>
-<h2 id="section-3">2025-01-28</h2>
+<h2 id="section-4">2025-01-28</h2>
 <p><strong>IMPORTANT DISCORD UPDATE</strong>: Due to a Discord bug/mis-feature, those
 who joined the <a href="https://discord.gg/Wa42Qujwnw">IOCCC Discord server</a>
 recently lost their access soon afterwards and have to re-join.
@@ -478,7 +492,7 @@ Fans of the IOCCC, hopeful <strong>IOCCC28</strong> contestants, and past winner
 are all encouraged to stop by and say hello.</p>
 <p>To join, click this link:
 <a href="https://discord.gg/Wa42Qujwnw">https://discord.gg/Wa42Qujwnw</a>.</p>
-<h2 id="section-4">2025-01-25</h2>
+<h2 id="section-5">2025-01-25</h2>
 <p>The IOCCC now has a <a href="https://discord.gg/Wa42Qujwnw">Discord server</a>!
 Click the link to join the <a href="https://discord.gg/Wa42Qujwnw">IOCCC Discord server</a>.
 Fans of the IOCCC, hopeful <strong>IOCCC28</strong> contestants, and past winners of the IOCCC
@@ -494,14 +508,14 @@ on <strong>2024-12-29 23:58:13.213455 UTC</strong>, is now scheduled to be <stro
 from <strong>2025-02-19 23:19:17.130705 UTC</strong> to <strong>2025-05-19 23:29:31.374143
 UTC</strong>. We will update the <a href="next/rules.html">IOCCC rules</a> and
 <a href="next/guidelines.html">IOCCC guidelines</a> accordingly, before the contest opens.</p>
-<h2 id="section-5">2024-12-31</h2>
+<h2 id="section-6">2024-12-31</h2>
 <p>We have just released <a href="https://github.com/ioccc-src/mkiocccentry/releases/tag/v2.3">version 2.3 of the mkiocccentry repo</a>.
 This repo 2.3 release includes important improvements (over repo release 2.1) to the <code>mkiocccentry(1)</code> tool
 as well as a critical fix for installing on BSD based systems.</p>
 <p>Please download <a href="https://github.com/ioccc-src/mkiocccentry/releases/tag/v2.3">version 2.3 of the mkiocccentry repo</a>,
 and compile the <a href="faq.html#mkiocccentry">mkiocccentry tool set</a>. You may also wish to install this code.
 See also the <a href="https://github.com/ioccc-src/mkiocccentry/blob/master/FAQ.md">mkiocccentry FAQ</a> for more information.</p>
-<h2 id="section-6">2024-12-30</h2>
+<h2 id="section-7">2024-12-30</h2>
 <p>The IOCCC <a href="next/rules.html#rule13">Rule 13</a> no longer discourages the
 use of UTF-8 in C source. Since the days of <code>-std=gnu17</code> compilers,
 UTF-8 characters do not impose a compiler problem. The related guideline
@@ -512,7 +526,7 @@ modifications as means to tell the submitter that their submission was received.
 <p>All of the import IOCCC dates within the <a href="next/rules.html">IOCCC rules</a>
 have been moved into the “<a href="next/rules.html#dates">Important IOCCC dates</a>”
 section.</p>
-<h2 id="section-7">2024-12-28</h2>
+<h2 id="section-8">2024-12-28</h2>
 <h3 id="good-news-everyone--">Good News Everyone! :-)</h3>
 <p>After a 4 year effort by a <a href="thanks-for-help.html">number of people</a>,
 with over 6168+ commits, the <strong>Great Fork Merge</strong> has been completed
@@ -540,7 +554,7 @@ and <a href="status.json">status.json</a> has been updated to reflect this new s
 <p>Proposed and tentative <a href="next/rules.html">IOCCC rules</a> and <a href="next/guidelines.html">IOCCC guidelines</a>
 have been released.</p>
 <p>See <a href="quick-start.html#enter_questions">FAQ Section 0</a> for more information on how to enter.</p>
-<h2 id="section-8">2024-06-08</h2>
+<h2 id="section-9">2024-06-08</h2>
 <p>We continue to make good progress on the
 <a href="https://ioccc-src.github.io/temp-test-ioccc/">temp-test-ioccc website</a>
 via the <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc</a> repo.</p>
@@ -570,7 +584,7 @@ not having to look at them more than once on a whole, other than possible
 entries that have to be added at the end, like the example below.</p>
 <p>Once the <em>submit server</em> server is ready another FAQ will be added and that
 entry can be looked at alone.</p>
-<h2 id="section-9">2024-05-30</h2>
+<h2 id="section-10">2024-05-30</h2>
 <p>A number of issues from minor fixes have been applied to the
 <a href="https://ioccc-src.github.io/temp-test-ioccc/">temp-test-ioccc website</a>
 via the <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc</a> repo.</p>
@@ -605,7 +619,7 @@ ask for beta testing of the new <strong>IOCCC registration process</strong> and
 This will speed up the start date of IOCCC28.</p>
 <p>It is our plan that IOCCC28 will occur in 2024, the 40th anniversary of the
 IOCCC.</p>
-<h2 id="section-10">2024-04-30</h2>
+<h2 id="section-11">2024-04-30</h2>
 <p>The website now is viewing by mobile devices such as cell phones
 and tablets. Devices with a screen resolution 1024 pixels and
 narrower are given a <em>hamburger-style</em> menu icon in place of
@@ -627,7 +641,7 @@ files that are static (not generated <code>bin</code> tools) report </strong>no
 warnings, nor info** messages, changes involving fixing invalid
 links to local files have been corrected, and changes involving the
 <em>topbar</em> are now HTML 5 conforming.</p>
-<h2 id="section-11">2024-04-20</h2>
+<h2 id="section-12">2024-04-20</h2>
 <p>Nearly all of the <a href="https://ioccc-src.github.io/temp-test-ioccc/">temp-test-ioccc website</a>
 website has undergone editorial review. Nearly all <a href="years.html">IOCCC winning entries</a>
 compile on modern systems and many have <code>try.sh</code> scripts to help you run them.
@@ -645,10 +659,10 @@ glaring “<em>dancing bears</em>” and other frivolous web features.</p>
 where the contents of the <a href="https://ioccc-src.github.io/temp-test-ioccc/">temp-test-ioccc website</a>
 will be merged into the <a href="https://www.ioccc.org/index.html">Official IOCCC website</a>.</p>
 <p>Stay tuned!</p>
-<h2 id="section-12">2024-02-29</h2>
+<h2 id="section-13">2024-02-29</h2>
 <p>We continue to make good progress on website. In the <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc GitHub repo</a> we have made nearly 4600 changes to date!</p>
 <p>All web pages, including this one, are now constructed from markdown files and/or JSON data files using tools found in the <a href="bin/index.html">bin</a> directory.</p>
-<h2 id="section-13">2023-05-22</h2>
+<h2 id="section-14">2023-05-22</h2>
 <p>We have been busy preparing for an important / significant update to this website. In the <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc GitHub repo</a> we have made nearly 2645 changes to date.</p>
 <p>While you are free to look at the <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc GitHub repo</a>,
 please <strong>do not link to it</strong> as this repo and related website will disappear once the main
@@ -704,7 +718,7 @@ that needs urgent fixing.
 The <strong>IOCCCMOCK</strong> will us to beta-test the new IOCCC process without putting the hard work of those
 who submit real IOCCC entries at risk.</p>
 <p>Stay tuned!</p>
-<h2 id="section-14">2023-01-30</h2>
+<h2 id="section-15">2023-01-30</h2>
 <p>We added to the
 <a href="status.json">status.json</a> page,
 a <em>“status_date”</em> JSON member whose value is the date
@@ -716,7 +730,7 @@ a <em>“latest_news”</em> JSON member whose value is the date
 of the most recent news item.</p>
 <pre><code>    &quot;status_date&quot; : &quot;Mon Jan 30 02:28:44 PST 2023&quot;,
     &quot;latest_news&quot; : &quot;Mon Jan 30 02:28:44 PST 2023&quot;</code></pre>
-<h2 id="section-15">2022-12-18</h2>
+<h2 id="section-16">2022-12-18</h2>
 <p>As per the suggestion of <a href="https://fosstodon.org/@Virtaava@home.social">Toni Mikkola
 (<span class="citation" data-cites="Virtaava">@Virtaava</span><span class="citation" data-cites="home.social&amp;rpar">@home.social&amp;rpar</span>;</a>
 we now maintain a <a href="status.json">status.json</a> page on this website.</p>
@@ -734,7 +748,7 @@ The details of such additional JSON members are <em>TBD</em>.</p>
 Instead you will have to rely on the additional JSON information
 and/or read the <a href="#news">IOCCC news</a>,
 and/or follow us on Mastodon via <strong><span class="citation" data-cites="ioccc">@ioccc</span><span class="citation" data-cites="fosstodon.org">@fosstodon.org</span></strong>.</p>
-<h2 id="section-16">2022-11-29</h2>
+<h2 id="section-17">2022-11-29</h2>
 <p>We are planning to abandon our
 <a href="https://twitter.com/ioccc">IOCCC Twitter feed</a>
 in favor of our new <a href="https://fosstodon.org/@ioccc">IOCCC Mastodon</a> feed.</p>
@@ -769,7 +783,7 @@ is made possible by volunteers,
 and those who voluntarily
 <a href="https://hub.fosstodon.org/support/">support</a> the cost of their server.</p>
 <p>Stay tuned in Mastodon as we update you on our progress towards the next IOCCC!</p>
-<h2 id="section-17">2022-11-19</h2>
+<h2 id="section-18">2022-11-19</h2>
 <p>Source code has been released for version <strong>0.8.1 2022-11-19</strong> of the
 <a href="https://github.com/ioccc-src/mkiocccentry">mkiocccentry repo</a>,
 a GitHub repo that includes the official iocccsize tool,
@@ -781,13 +795,13 @@ to upload the above mentioned compressed tarball: when the contest is open of co
 judges will go through the motions (without judging the content) of an IOCCC:
 testing the above mentioned tools and testing the submit server.</p>
 <p>We are working on complete rebuild of this website as well.</p>
-<h2 id="section-18">2022-01-15</h2>
+<h2 id="section-19">2022-01-15</h2>
 <p>Source code has been released for version <strong>0.24 2022-01-15</strong> of the
 <a href="https://github.com/ioccc-src/mkiocccentry">mkiocccentry tool</a>,
 a tool that is based on, and is containing, the official iocccsize tool,
 will form a compressed tarball that a registered IOCCC contestant
 will upload to the submit server (when the contest is open of course).</p>
-<h2 id="section-19">2021-12-27</h2>
+<h2 id="section-20">2021-12-27</h2>
 <p><a href="judges.html">The Judges</a>
 are continuing to work on re-tooling how we run the IOCCC.
 We are writing tools under various repositories our
@@ -796,7 +810,7 @@ We are writing tools under various repositories our
 Sorry for the delay, but we think you will appreciate the re-tooling
 when it is completed.
 Stay tuned!</p>
-<h2 id="section-20">2021-10-21</h2>
+<h2 id="section-21">2021-10-21</h2>
 <p><a href="judges.html">The Judges</a>
 are re-tooling how we run the IOCCC.
 Our goal is to build a smoother, more rapid process centered around
diff --git a/news.md b/news.md
index 565e95e98..5df2587bd 100644
--- a/news.md
+++ b/news.md
@@ -20,6 +20,26 @@ We invite you to join the **IOCCC Discord Community** via this link: [https://di
 </div>
 
 
+## 2025-03-12
+
+We released [mkiocccentry toolkit](https://github.com/ioccc-src/mkiocccentry) **version 2.4.3 2025-03-11**.
+
+While you are **NOT** required to use this release in order to submit to **IOCCC28**,
+we do **RECOMMEND** that you **install and use** it, because among other things, it provides:
+
+* `mkiocccentry(1)` and `txzchk(1)` now search for other toolkit tools using `$PATH`
+* `mkiocccentry(1)` and `chkentry(1)` are now less strict with most `iocccsize(1)` warnings
+* `mkiocccentry -x` will force the overwriting of the submission directory it forms under `workdir`
+* `mkiocccentry -U uuid` and `mkiocccentry -u uuid_file` let you set your username
+
+See the [version 2.4.3 release notes](https://github.com/ioccc-src/mkiocccentry/releases/tag/2.4.3)
+for more details.
+
+**Clarification**: **NUL bytes** are **ALLOWED** in your submission `prog.c` and related C code.
+
+Please mention in your `remarks.md` file if your C source contains **NUL bytes**.
+
+
 ## 2025-03-05
 
 The [40th anniversary of the IOCCC](faq.html#ioccc_start), **IOCCC28**, will be **open** for
diff --git a/sitemap.xml b/sitemap.xml
index f515d5dc3..4374d27bb 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -15414,11 +15414,11 @@
 </url>
 <url>
     <loc>https://www.ioccc.org/faq.html</loc>
-    <lastmod>2025-03-05T17:49:07+00:00</lastmod>
+    <lastmod>2025-03-13T03:37:32+00:00</lastmod>
 </url>
 <url>
     <loc>https://www.ioccc.org/faq.md</loc>
-    <lastmod>2025-03-05T17:49:07+00:00</lastmod>
+    <lastmod>2025-03-13T03:37:26+00:00</lastmod>
 </url>
 <url>
     <loc>https://www.ioccc.org/inc/index.html</loc>
@@ -15458,11 +15458,11 @@
 </url>
 <url>
     <loc>https://www.ioccc.org/news.html</loc>
-    <lastmod>2025-03-08T05:38:40+00:00</lastmod>
+    <lastmod>2025-03-13T03:00:48+00:00</lastmod>
 </url>
 <url>
     <loc>https://www.ioccc.org/news.md</loc>
-    <lastmod>2025-03-08T05:38:40+00:00</lastmod>
+    <lastmod>2025-03-13T03:00:38+00:00</lastmod>
 </url>
 <url>
     <loc>https://www.ioccc.org/README.html</loc>
@@ -15478,7 +15478,7 @@
 </url>
 <url>
     <loc>https://www.ioccc.org/status.json</loc>
-    <lastmod>2025-03-08T05:41:00+00:00</lastmod>
+    <lastmod>2025-03-13T03:00:54+00:00</lastmod>
 </url>
 <url>
     <loc>https://www.ioccc.org/thanks-for-help.html</loc>
diff --git a/status.html b/status.html
index c3b68870b..78f6089b8 100644
--- a/status.html
+++ b/status.html
@@ -434,7 +434,7 @@
         &quot;no_comment&quot; : &quot;mandatory comment: because comments were removed from the original JSON spec&quot;,
         &quot;IOCCC_status_version&quot; : &quot;1.0 2024-03-09&quot;,
         &quot;contest_status&quot; : &quot;open&quot;,
-        &quot;news_update&quot; : &quot;2025-03-08T05:38:40+00:00&quot;,
+        &quot;news_update&quot; : &quot;2025-03-13T03:00:38+00:00&quot;,
         &quot;status_update&quot; : &quot;2025-03-05T18:15:23+00:00&quot;
     }</code></pre>
 
diff --git a/status.json b/status.json
index 849eb3115..93fe0f833 100644
--- a/status.json
+++ b/status.json
@@ -2,6 +2,6 @@
     "no_comment" : "mandatory comment: because comments were removed from the original JSON spec",
     "IOCCC_status_version" : "1.0 2024-03-09",
     "contest_status" : "open",
-    "news_update" : "2025-03-08T05:38:40+00:00",
+    "news_update" : "2025-03-13T03:00:38+00:00",
     "status_update" : "2025-03-05T18:15:23+00:00"
 }