In some cases the author may wish to record a special URL for their IOCCC entry, or a 2nd URL such as a work or school or personal home page. For example, -Cody as of Thu Nov 30 23:51:12 UTC 2023 used:
+Cody Boone Ferguson as of Thu Nov 30 23:51:12 UTC 2023 used: "alt_url" : "https://ioccc.xexyl.net"If the author wishes to not specify an alternate URL, or if the alternate URL is
unknown, it should be the JSON null as the JSON value of this JSON
@@ -2537,7 +2537,7 @@ will always be null anyway.
"mastodon" : "@mame@ruby.social"This JSON member holds the -Mastodon social network +Mastodon instance handle of the author.
There MUST be one and only one mastodon JSON member and the JSON value MUST
be a JSON string or it MUST be a JSON null. The JSON string just be a valid
@@ -2548,11 +2548,11 @@ used by the author.
The IOCCC Mastodon handle is:
@ioccc@fosstodon.orgThe IOCCC uses the Mastodon social network for announcements such +
The IOCCC uses Mastodon for announcements such as the opening and closing of a new IOCCC, changes to the IOCCC web site, updates during the judging process, and when new IOCCC entries are selected. We recommend you follow us on Mastodon.
-If the author wishes to not specify an Mastodon handle, or if the Mastodon handle is +
If the author wishes to not specify a Mastodon handle, or if the Mastodon handle is unknown, it should be the JSON null as the JSON value of this JSON member. For example:
"mastodon" : nullmastodon handle is a JSON string, then the ma
The mastodon_url is just a translation of the above mentioned Mastodon handle.
For example, if the Mastodon handle is @user@server.domain, then the
mastodon_url would be https://server.domain/@user.
-If the author wishes to not specify an Mastodon URL, or if the Mastodon URL is
+
If the author wishes to not specify a Mastodon URL, or if the Mastodon URL is
unknown, it should be the JSON null as the JSON value of this JSON member.
For example:
"mastodon_url" : null
@@ -3284,9 +3284,9 @@ further down for different instructions. Otherwise: in particular you must:
deprecated.
According to this Linux for Devices tutorial on
XOrg as
-of 2023 Mar 25:
+of 2023 Mar 25 (quote verbatim):
-Recently, RHEL developers categorized Xorg was put in the ‘deprecated’
+Recently, RHEL developers categorized Xorg Xorg was put in the ‘deprecated’
software,
as its development has mostly halted. Subsequent updates will completely replace
it with Wayland, a more modern windowing system.. Although Wayland is not fully
@@ -3918,9 +3918,10 @@ or no longer work on modern computers or modern operating systems, though again
a great deal of these were fixed for modern systems.
There are some cases where certain compilers or even certain versions are
necessary for the program to function in part or even completely.
-Some IOCCC entries might operating system services that may not be present on
+
Some IOCCC entries might need operating system services that might not be present on
your system, as well.
-In some cases the IOCCC entry simply has bugs or (Mis)features.
+In some cases the IOCCC entry simply has bugs or
+(Mis)features.
If you are having problems compiling or running an IOCCC entry,
we recommend that you look in bugs.html to see if
there is a known bugs or (Mis)feature. In some cases what you
@@ -4460,7 +4461,7 @@ against fixing it, then please consider opening a branch of the ioccc-src/winner
repo.
-BTW: A problem is not limited to the code itself. Fixing typos in files
+
BTW: A problem is not limited to the code itself. Fixing typos in files
such as “index.html” files (via its respective README.md file), fixing
issues in a “Makefile”, or otherwise correcting an IOCCC entry is VERY MUCH
WELCOME! Please use the same GitHub pull
@@ -4498,10 +4499,10 @@ have to be logged into your account.
To help you out here is a navigation menu in this FAQ entry:
- Creating a GitHub account
-- Installing an ssh key to GitHub
+- Installing an ssh key to GitHub
- Forking the IOCCC winner repo
- Cloning the IOCCC winner repo
-- Making changes, fixes etc.
+- Making changes, fixes etc.
- Committing your changes
- Opening a pull request
- What to do after a merge
@@ -4638,7 +4639,7 @@ title could have:
script that discusses this and gives supposed examples.
Once you’ve done this you should click on Create pull request.
-IMPORTANT NOTE: although the Judges will
+
IMPORTANT NOTE: although the Judges will
give more deference to the authors of edited entries the
Judges also retain the final editorial say
in the matter.
@@ -4763,7 +4764,9 @@ of the ioccc-src/winner repo.<
FAQ on “GitHub pull request”
for more information.
IMPORTANT NOTE: As these files are JSON you should verify that
-they are validly formed (e.g., you didn’t make a typo).
+they are validly formed (e.g., you didn’t make a typo). See the
+FAQ on “how to validate JSON files”
+for more help.
Before you form your GitHub pull request that modifies a
author_handle.json file, please run the make www command. This
unfortunately takes quite a while but it is the safest way to do
@@ -5100,7 +5103,7 @@ entries that have won the IOCCC, sometimes in the same IOCCC contest year.
refer to what is now an author. In a number of historical cases,
such as old rules and old guidelines, terms such as winner may still be
found. Moreover, out of habit, the IOCCC judges sometimes use old
-names such as winner when they should use author. Sorry (tm Canada)! :-)
+names such as winner when they should use author. Sorry (tm Canada :-) )!
- Entry
@@ -5116,7 +5119,7 @@ directory YYYY/entry.
refer to what is now an entry. In a number of historical cases,
such as old rules and old guidelines, terms such as winner may still be
found. Moreover, out of habit, the IOCCC judges sometimes use old
-names such as winner when they should use entry. Sorry (tm Canada)! :-)
+names such as winner when they should use entry. Sorry (tm Canada :-) )!
- Submission
@@ -5345,13 +5348,13 @@ this bad!
flame to
net.lang.c
inviting people to try and out obfuscate the UN*X source code we had just been working on.
-BTW: I (Landon Curt Noll) had to post this typo
+BTW: I (Landon Curt Noll) had to post this typo
correction.
Thus began the tradition of putting typos in the contest rules and guidelines
… to make them more obfuscated of course! :-)
-BTW: This posting was made back in the days when AT&T was the evil giant.
+
BTW: This posting was made back in the days when AT&T was the evil giant.
Now, Microsoft makes AT&T look mild and kind in comparison. :-( (IMHO) ).
-BTW: See the story about the ‘Bill Gates’ award. :-)
+BTW: See the story about the ‘Bill Gates’ award. :-)
OK, back to the story.
We (Larry and I) received a number of entries by email.
When we began to receive messages from outside of the US, Larry and I
@@ -5366,14 +5369,14 @@ were posted on 17 April 1984.
2nd place
1st place
-BTW: The (dis)honorable mention wished to remain anonymous.
+
BTW: The (dis)honorable mention wished to remain anonymous.
While many have asked who it was, we have continued to follow the
author’s wish to remain anonymous.
A few years ago, we asked the author if they still wanted to remain anonymous.
They said: ‘Yes, I want to keep my anonymity. But you can tell them that I am well known for my connection to the
C language’. It was not until 2001 that another anonymous
entry received an award.
-BTW: The 1984/mullender remains one of my (Landon Curt Noll) all time favorites.
+BTW: The 1984/mullender remains one of my (Landon Curt Noll) all time favorites.
The name used in the posting of the 1st winning IOCCC
entry
posting was International Obfuscated C Code Contest or
@@ -5493,7 +5496,8 @@ going back to push into the temp-test-ioccc
repo
-occurred on Sun Sep 18 11:15:49 2022 -0700.
+occurred on Sun Sep 18 11:15:49 2022 -0700, by Cody Boone
+Ferguson.
At this same time, the temp-test-ioccc website went live.
Edits were made by an IOCCC judge
to their local git repository and were pushed into the temp-test-ioccc
@@ -5545,9 +5549,9 @@ from winners.html, via the 202y mm dd The Great Fork Merge
-As of 2024 Oct 20 temp-test-ioccc
+As of 2024 Dec 27 temp-test-ioccc
repo
-there were 5975 commits ahead
+there were 6141+ commits ahead
of the IOCCC winner repo.