From d11ea9e699fbfa1798971756ec830876f49a0e7b Mon Sep 17 00:00:00 2001 From: Cody Boone Ferguson <53008573+xexyl@users.noreply.github.com> Date: Fri, 27 Dec 2024 09:46:09 -0800 Subject: [PATCH 1/5] Various fixes and updates to FAQ --- faq.html | 52 ++++++++++++++++++++++++++++------------------------ faq.md | 52 ++++++++++++++++++++++++++++------------------------ 2 files changed, 56 insertions(+), 48 deletions(-) diff --git a/faq.html b/faq.html index a48db7ca3..6dc386355 100644 --- a/faq.html +++ b/faq.html @@ -2510,7 +2510,7 @@ member. For example:

be a JSON string or it MUST be a JSON null.

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
    "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.

See the “Mastodon Address” section of that page in particular.

The IOCCC Mastodon handle is:

    @ioccc@fosstodon.org
-

The 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" : null
@@ -2567,7 +2567,7 @@ If the mastodon 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:

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 :-) )!

@@ -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 :-) )!

@@ -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.

    On 202y mm dd, the temporary repo was merged back into the IOCCC winner diff --git a/faq.md b/faq.md index 300001862..46ff78063 100644 --- a/faq.md +++ b/faq.md @@ -2535,7 +2535,7 @@ be a _JSON string_ or it **MUST** be a _JSON null_. 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](authors.html#Cody_Boone_Ferguson) as of _Thu Nov 30 23:51:12 UTC 2023_ used: ``` "alt_url" : "https://ioccc.xexyl.net" @@ -2590,7 +2590,7 @@ will always be `null` anyway. ``` This _JSON member_ holds the -[Mastodon social network](https://en.wikipedia.org/wiki/Mastodon_(social_network)) +[Mastodon instance](https://en.wikipedia.org/wiki/Mastodon_(social_network)) handle of the author. There **MUST** be one and only one `mastodon` _JSON member_ and the _JSON value_ **MUST** @@ -2608,12 +2608,12 @@ The IOCCC Mastodon handle is: @ioccc@fosstodon.org ``` -The 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: @@ -2641,7 +2641,7 @@ 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: @@ -3594,10 +3594,10 @@ deprecated](https://access.redhat.com/documentation/en-us/red_hat_enterprise_lin According to this [Linux for Devices tutorial on XOrg](https://www.linuxfordevices.com/tutorials/linux/install-xorg-on-linux) 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](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 it with Wayland, a more modern windowing system.. Although Wayland is not fully @@ -4718,10 +4718,11 @@ 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](bugs.html). If you are having problems compiling or running an IOCCC entry, we recommend that you look in [bugs.html](bugs.html) to see if @@ -5440,7 +5441,7 @@ request](https://github.com/ioccc-src/winner/pulls) against the master [branch](https://github.com/ioccc-src/winner/branches) of the [ioccc-src/winner repo](https://github.com/ioccc-src/winner). -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 @@ -5490,10 +5491,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](#creating-a-github-account) -- [Installing an ssh key to GitHub](#installing-an-ssh-key) +- [Installing an ssh key to GitHub](#installing-an-ssh-key-to-github) - [Forking the IOCCC winner repo](#forking-the-ioccc-winner-repo) - [Cloning the IOCCC winner repo](#cloning-the-ioccc-winner-repo) -- [Making changes, fixes etc.](#making-changes-fixes-etc) +- [Making changes, fixes etc.](#making-changes-fixes-etc.) - [Committing your changes](#committing-your-changes) - [Opening a pull request](#opening-a-pull-request) - [What to do after a merge](#what-to-do-after-a-merge) @@ -5709,7 +5710,7 @@ and then the text field that is labelled _Add a description_ would have: Once you've done this you should click on _Create pull request_. -IMPORTANT NOTE: although the [Judges](https://www.ioccc.org/judges.html) will +**IMPORTANT NOTE**: although the [Judges](https://www.ioccc.org/judges.html) will give more deference to the authors of edited entries the [Judges](https://www.ioccc.org/judges.html) also retain the final editorial say in the matter. @@ -5897,7 +5898,9 @@ FAQ on "[GitHub pull request](#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](#jparse)" +for more help. Before you form your GitHub pull request that modifies a `author_handle.json` file, please run the `make www` command. This @@ -6347,7 +6350,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 @@ -6366,7 +6369,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 @@ -6692,15 +6695,15 @@ After a few minutes we wandered back into my office where I posted a net.lang.c](http://groups.google.com/groups?q=Obfuscated&hl=en&lr=&ie=UTF-8&as_drrb=b&as_mind=1&as_minm=1&as_miny=1983&as_maxd=18&as_maxm=4&as_maxy=1984&selm=789%40nsc.UUCP&rnum=3&filter=0") 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](http://groups.google.com/groups?q=Obfuscated&hl=en&lr=&ie=UTF-8&as_drrb=b&as_mind=1&as_minm=1&as_miny=1983&as_maxd=18&as_maxm=4&as_maxy=1984&selm=795%40nsc.UUCP&rnum=10&filter=0). 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](1993/cmills/index.html)' award. :-) +**BTW**: See the story about the '[Bill Gates](1993/cmills/index.html)' award. :-) OK, back to the story. @@ -6719,7 +6722,7 @@ There were 4 entries that won in 1984: 3. [2nd place](http://groups.google.com/groups?q=Obfuscated&hl=en&lr=&ie=UTF-8&as_drrb=b&as_mind=1&as_minm=1&as_miny=1983&as_maxd=18&as_maxm=4&as_maxy=1984&selm=844%40nsc.UUCP&rnum=6&filter=0) 4. [1st place](http://groups.google.com/groups?q=Obfuscated&hl=en&lr=&ie=UTF-8&as_drrb=b&as_mind=1&as_minm=1&as_miny=1983&as_maxd=18&as_maxm=4&as_maxy=1984&selm=845%40nsc.UUCP&rnum=5&filter=0) -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. @@ -6728,7 +6731,7 @@ They said: '_Yes, I want to keep my anonymity. But you can tell them that I am C language_'. It was not until 2001 that another [anonymous entry](2001/anonymous/index.html) received an award. -BTW: The [1984/mullender](1984/mullender/index.html) remains one of my (Landon Curt Noll) all time favorites. +**BTW**: The [1984/mullender](1984/mullender/index.html) remains one of my (Landon Curt Noll) all time favorites. The name used in the posting of the [1st winning IOCCC entry](http://groups.google.com/groups?q=Obfuscated&hl=en&lr=&ie=UTF-8&as_drrb=b&as_mind=1&as_minm=1&as_miny=1983&as_maxd=18&as_maxm=4&as_maxy=1984&selm=837%40nsc.UUCP&rnum=2&filter=0) @@ -6886,7 +6889,8 @@ going back to [2020 Dec the repo was forked on **Sun Sep 18 17:30:00 2022 -0700**. The first [push into the temp-test-ioccc repo](https://github.com/ioccc-src/temp-test-ioccc/commit/edbc3089e1b755d85a020af7975bbc7df3737a5f) -occurred on Sun Sep 18 11:15:49 2022 -0700. +occurred on Sun Sep 18 11:15:49 2022 -0700, by [Cody Boone +Ferguson](authors.html#Cody_Boone_Ferguson). At this same time, the [temp-test-ioccc website](https://ioccc-src.github.io/temp-test-ioccc/) went live. @@ -6945,9 +6949,9 @@ from `winners.html`, via the [gen-authors.sh](%%REPO_URL%%/bin/gen-authors.sh) t -As of 2024 Oct 20 [temp-test-ioccc +As of 2024 Dec 27 [temp-test-ioccc repo](https://github.com/ioccc-src/temp-test-ioccc) -there were [5975 commits ahead](https://github.com/ioccc-src/winner/compare/master...ioccc-src:temp-test-ioccc:master) +there were [6141+ commits ahead](https://github.com/ioccc-src/winner/compare/master...ioccc-src:temp-test-ioccc:master) of the [IOCCC winner repo](https://github.com/ioccc-src/winner). From aadc26e407bd2184fbf61d6f55709a3dc8771ecb Mon Sep 17 00:00:00 2001 From: Cody Boone Ferguson <53008573+xexyl@users.noreply.github.com> Date: Fri, 27 Dec 2024 09:50:07 -0800 Subject: [PATCH 2/5] Typo fix in FAQ --- faq.html | 2 +- faq.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/faq.html b/faq.html index 6dc386355..36aecc940 100644 --- a/faq.html +++ b/faq.html @@ -5551,7 +5551,7 @@ from winners.html, via the temp-test-ioccc repo -there were 6141+ commits ahead +there was 6141+ commits ahead of the IOCCC winner repo.

    On 202y mm dd, the temporary repo was merged back into the IOCCC winner diff --git a/faq.md b/faq.md index 46ff78063..9b78e78b2 100644 --- a/faq.md +++ b/faq.md @@ -6951,7 +6951,7 @@ from `winners.html`, via the [gen-authors.sh](%%REPO_URL%%/bin/gen-authors.sh) t As of 2024 Dec 27 [temp-test-ioccc repo](https://github.com/ioccc-src/temp-test-ioccc) -there were [6141+ commits ahead](https://github.com/ioccc-src/winner/compare/master...ioccc-src:temp-test-ioccc:master) +there was [6141+ commits ahead](https://github.com/ioccc-src/winner/compare/master...ioccc-src:temp-test-ioccc:master) of the [IOCCC winner repo](https://github.com/ioccc-src/winner). From 970dba0fb2d14bc12876e4f62cdbae8f1962462c Mon Sep 17 00:00:00 2001 From: Cody Boone Ferguson <53008573+xexyl@users.noreply.github.com> Date: Fri, 27 Dec 2024 09:52:38 -0800 Subject: [PATCH 3/5] Fix broken link to submit server in FAQ --- faq.html | 2 +- faq.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/faq.html b/faq.html index 36aecc940..af40a477e 100644 --- a/faq.html +++ b/faq.html @@ -609,7 +609,7 @@ then follow the directions on How to regist

    Once you have registered for the IOCCC, and once the contest is OPEN, one of the IOCCC judges will send via email within a few days, -your IOCCC submit server Username and +your IOCCC submit server Username and Initial password.

    PLEASE NOTE: After registering, it could take up to a few days before an IOCCC judge sends the that email, so PLEASE diff --git a/faq.md b/faq.md index 9b78e78b2..30cfd47fc 100644 --- a/faq.md +++ b/faq.md @@ -205,7 +205,7 @@ then follow the directions on **[How to register for the IOCCC](next/register.ht Once you have [registered for the IOCCC](next/register.html), and once the contest is **[OPEN](status.html#open)**, one of the [IOCCC judges](judges.html) will send via email within a few days, -your [IOCCC submit server](https:/submit.ioccc.org) **Username** and +your [IOCCC submit server](https://submit.ioccc.org) **Username** and **Initial password**. **PLEASE NOTE**: After registering, it could take up to a **few days** From 47ac7c7468d4af4d73328e0e6ebe2866d0885a2f Mon Sep 17 00:00:00 2001 From: Cody Boone Ferguson <53008573+xexyl@users.noreply.github.com> Date: Fri, 27 Dec 2024 09:53:36 -0800 Subject: [PATCH 4/5] Fix another link to submit server in FAQ --- faq.html | 2 +- faq.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/faq.html b/faq.html index af40a477e..029000cc6 100644 --- a/faq.html +++ b/faq.html @@ -628,7 +628,7 @@ for assistance.

    4. Login to the submit server and change your password

    Using the Username and Initial password you receive via -email in step 3, you need to login to the IOCCC submit +email in step 3, you need to login to the IOCCC submit server.

    IMPORTANT NOTE: You must change your password WITHIN 72 HOURS from when one of the IOCCC judges sent that email.

    diff --git a/faq.md b/faq.md index 30cfd47fc..e90dfb684 100644 --- a/faq.md +++ b/faq.md @@ -232,7 +232,7 @@ for assistance. Using the **Username** and **Initial password** you receive via email in [step 3](#step_3), you need to login to the [IOCCC submit -server](https:/submit.ioccc.org). +server](https://submit.ioccc.org). **IMPORTANT NOTE**: You must change your password **WITHIN 72 HOURS** from when one of the [IOCCC judges](judges.html) sent that email. From 2d3ee0b06aa2938a76e566b889799ce85b6e0139 Mon Sep 17 00:00:00 2001 From: Cody Boone Ferguson <53008573+xexyl@users.noreply.github.com> Date: Fri, 27 Dec 2024 10:02:17 -0800 Subject: [PATCH 5/5] Another typo fix in FAQ --- faq.html | 9 +++++---- faq.md | 9 +++++---- 2 files changed, 10 insertions(+), 8 deletions(-) diff --git a/faq.html b/faq.html index 029000cc6..ff4c5a720 100644 --- a/faq.html +++ b/faq.html @@ -613,10 +613,11 @@ your IOCCC submit server Username Initial password.

    PLEASE NOTE: After registering, it could take up to a few days before an IOCCC judge sends the that email, so PLEASE -be patient.

    +be patient    . This means that you should GIVE YOURSELF TIME before the +contest closes!

    IMPORTANT NOTE: Unless the contest is open, -the you will NOT receive your Username and Initial password -by email. For example, if contest is pending, +then you will NOT receive your Username and Initial password +by email. For example, if the contest is pending, you will have to WAIT UNTIL THE CONTEST IS OPEN.

    Please check the current status of the IOCCC and visit the How to register for the IOCCC for detailed instructions.

    @@ -4908,7 +4909,7 @@ least in most cases; other terms might be used, including on a rare occasion spoiler, this depending on context.

    We ask that the deobfuscated code be identical in functionality to the winning IOCCC entry code.

    -

    PLEASE NOTE: Be aware that IOCCC entry code may contain extremely subtle and +

    PLEASE NOTE: Beware that IOCCC entry code may contain extremely subtle and obscure side effects (i.e., features). Those wishing to contribute a deobfuscated version of code should strive to mimic the original (or existing) IOCCC entry code as much as possible. Some authors can be contacted diff --git a/faq.md b/faq.md index e90dfb684..935ab9dd2 100644 --- a/faq.md +++ b/faq.md @@ -210,11 +210,12 @@ your [IOCCC submit server](https://submit.ioccc.org) **Username** and **PLEASE NOTE**: After registering, it could take up to a **few days** before an [IOCCC judge](judges.html) sends the that email, so **PLEASE -be patient**. +be patient**. This means that you should **GIVE YOURSELF TIME** before the +contest closes! **IMPORTANT NOTE**: Unless the contest is [open](status.html#open), -the you will **NOT** receive your **Username** and **Initial password** -by email. For example, if contest is [pending](status.html#pending), +then you will **NOT** receive your **Username** and **Initial password** +by email. For example, if the contest is [pending](status.html#pending), you will have to **WAIT UNTIL THE CONTEST IS [OPEN](status.html#open)**. Please check the [current status of the IOCCC](status.html) and @@ -6095,7 +6096,7 @@ _spoiler_, this depending on context. We ask that the **deobfuscated** code be **identical in functionality** to the winning IOCCC entry code. -**_PLEASE_ NOTE**: Be aware that IOCCC entry code may contain **extremely subtle and +**_PLEASE_ NOTE**: Beware that IOCCC entry code may contain **extremely subtle and obscure side effects** (i.e., features). Those wishing to contribute a **deobfuscated** version of code should **strive to mimic** the original (or existing) IOCCC entry code as much as possible. Some authors can be contacted