diff --git a/Makefile b/Makefile index ca00a5472..56b793ea2 100644 --- a/Makefile +++ b/Makefile @@ -282,7 +282,7 @@ clobber: thanks gen_other_html quick_other_html quick_entry_index find_invalid_json \ gen_year_index quick_year_index quick_www www untar_entry_tarball untar_year_tarball \ form_entry_tarball form_year_tarball tar gen_status gen_sitemap \ - sitemap timestamp update csv2entry entry2csv about contact + sitemap timestamp update csv2entry entry2csv about contact gen_pw_change # Suggest rules in this section # @@ -314,6 +314,7 @@ help: @echo 'make verify_entry_files ;: check to be sure all files in all entries exist' @echo 'make sort_gitignore ;: sort .gitignore files according to rules in bin/sgi.sh' @echo 'make gen_authors ;: generate the top level authors.html page' + @echo 'make gen_pw_change ;: generate the next/pw-change.html page' @echo 'make quick_authors ;: build authors.html if out of date with author JSON files' @echo 'make gen_location ;: generate the top level location.html page' @echo 'make quick_location ;: build location.html if out of date with author JSON files' @@ -466,6 +467,8 @@ gen_authors: ${GEN_AUTHORS} ${GEN_AUTHORS} -v 1 @echo '=-=-=-=-= IOCCC complete make $@ =-=-=-=-=' + + # build authors.html if it is out of date from any author/author_handle.json file # quick_authors: ${GEN_AUTHORS} @@ -691,6 +694,14 @@ gen_next: ${GEN_TOP_HTML} next/README.md next/guidelines.md next/rules.md next/r ${GEN_TOP_HTML} -v 1 next/pw-change @echo '=-=-=-=-= IOCCC complete make $@ =-=-=-=-=' +gen_pw_change: + @echo '=-=-=-=-= IOCCC begin make $@ =-=-=-=-=' + @echo "Did your password get breached?" + ${GEN_TOP_HTML} -v 1 next/pw-change + @echo '=-=-=-=-= IOCCC complete make $@ =-=-=-=-=' + @echo "Perhaps you should change your password!" + @echo '=-=-=-=-= IOCCC complete make $@ =-=-=-=-=' + markdown: ${GEN_TOP_HTML} markdown.md @echo '=-=-=-=-= IOCCC begin make $@ =-=-=-=-=' @echo "You want to markdown?" diff --git a/next/pw-change.html b/next/pw-change.html index 0fd22a8a2..cf33a82ab 100644 --- a/next/pw-change.html +++ b/next/pw-change.html @@ -430,35 +430,39 @@ email in step 3, you need to login to t server.

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

-

NOTE: The IOCCC submit server -is ready for submissions ONLY WHEN THE CONTEST IS open. -See current status of the IOCCC for details on the contest status.

+

NOTE: The IOCCC submit server will be ready +for submissions ONLY WHEN THE CONTEST IS open. See +current status of the IOCCC for details on the contest status.

IMPORTANT NOTE: When the contest is closed, the IOCCC submit server -may be offline and unreachable as a web site.

+may be offline and unreachable as a website.

To login and change your password, open https://submit.ioccc.org in your browser. It should look like this:

-

submit server login screen

-

The username is the UUID you were provided when you registered for the IOCCC and -the password is the initial password you were provided with. Click “Login”.

-

If this is the first time you have logged in with this UUID, you will -be required to change your password.

-

Assuming everything is fine, it should look something like:

-

The username is the UUID you are provided when a judge replies to your request +to register for the IOCCC and the password is the initial password you are +given. Click “Login”.

+

After you log in, if this is the first time you have logged in with this UUID, +you will be required to change your password. Assuming everything is fine, that +would look something like:

+

submit server password change required

-

As you can see, you have to change your password. Put in your login (UUID -username), your old (initial) password and a new password. For instance:

-

submit server changing password

+

As you can see, on your first login you MUST change your password. If you do +not do this within 72 hours YOUR ACCOUNT WILL BE CLOSED and you’ll have to +register again!

+

Put in your login (UUID username), your old (initial) password and a new password.

Click “Change Password”.

-

Once this is done, you will be able to log in again with your UUID +

NOTE: if you have put in your old password, you’ll see something like:

+

submit server password change error

+

Once you’ve changed your password you will be able to log in again with your UUID username and new password. This is what it will look like when you change your password:

-

submit server password changed

When the contest is open, proceed with diff --git a/next/pw-change.md b/next/pw-change.md index 099e11cd6..c0165bb40 100644 --- a/next/pw-change.md +++ b/next/pw-change.md @@ -7,47 +7,52 @@ 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. -**NOTE**: The [IOCCC submit server](https://submit.ioccc.org) -is ready for submissions **ONLY WHEN THE CONTEST IS [open](../faq.html#open)**. -See [current status of the IOCCC](../status.html) for details on the contest status. +**NOTE**: The [IOCCC submit server](https://submit.ioccc.org) will be ready +for submissions **ONLY WHEN THE CONTEST IS [open](../faq.html#open)**. See +[current status of the IOCCC](../status.html) for details on the contest status. **IMPORTANT NOTE**: When the contest is [closed](../faq.html#closed), the [IOCCC submit server](https://submit.ioccc.org) -may be offline and unreachable as a web site. +may be offline and unreachable as a website. To login and change your password, open [https://submit.ioccc.org](https://submit.ioccc.org) in your browser. It should look like this: -submit server login screen -The username is the UUID you were provided when you registered for the IOCCC and -the password is the initial password you were provided with. Click "Login". +The username is the UUID you are provided when a judge replies to your request +to register for the IOCCC and the password is the initial password you are +given. Click "Login". -If this is the first time you have logged in with this UUID, you will -be required to change your password. +After you log in, if this is the first time you have logged in with this UUID, +you will be required to change your password. Assuming everything is fine, that +would look something like: -Assuming everything is fine, it should look something like: - -submit server password change required -As you can see, you have to change your password. Put in your login (UUID -username), your old (initial) password and a new password. For instance: +As you can see, on your first login you **MUST** change your password. If you do +not do this within 72 hours **YOUR ACCOUNT WILL BE CLOSED** and you'll have to +register again! -submit server changing password +Put in your login (UUID username), your old (initial) password and a new password. Click "Change Password". -Once this is done, you will be able to log in again with your UUID +**NOTE**: if you have put in your old password, you'll see something like: + +submit server password change error + +Once you've changed your password you will be able to log in again with your UUID username and new password. This is what it will look like when you change your password: -submit server password changed diff --git a/next/register.html b/next/register.html index 7bfed2aba..633cf1dd4 100644 --- a/next/register.html +++ b/next/register.html @@ -456,10 +456,10 @@ in order to register for the IOCCC.

Subscription consent for ‘ioccc28-reg’

-

NOTE: Beware that your email service, application and/or Internet -Service Provider (ISP) might modify email subject lines. For example, some string -might have been prepended or appended to the subject line. Beware of -this when you search for the Subscription consent” email.

+

NOTE: be aware that some email services, applications and/or Internet +Service Providers (ISP) modify email subject lines. For example, some string +might have been prepended or appended to the subject line. Be aware of +this when you search for the “Subscription consent” email.

NOTE: The “Subscription consent” email is usually sent by the FreeLists List Manager within a minute after clicking the ((Next >>)) button. If you don’t see the “Subscription consent” email, check your spam folder.

diff --git a/next/register.md b/next/register.md index 5aabe177c..ad3b90e16 100644 --- a/next/register.md +++ b/next/register.md @@ -43,10 +43,10 @@ The email message will have the subject: > Subscription consent for 'ioccc28-reg' -**NOTE**: Beware that your email service, application and/or Internet -Service Provider (ISP) might modify email subject lines. For example, some string -might have been prepended or appended to the subject line. Beware of -this when you search for the Subscription consent" email. +**NOTE**: be aware that some email services, applications and/or Internet +Service Providers (ISP) modify email subject lines. For example, some string +might have been prepended or appended to the subject line. Be aware of +this when you search for the "Subscription consent" email. **NOTE**: The "Subscription consent" email is usually sent by the FreeLists List Manager within a minute after clicking the **((Next >>))** button. diff --git a/next/rules.html b/next/rules.html index 845467a3b..daf9add47 100644 --- a/next/rules.html +++ b/next/rules.html @@ -461,7 +461,7 @@ writing by contacting the judges.

-These IOCCC rules are version 28.26 2025-02-28. +These IOCCC rules are version 28.27 2025-03-01.

The markdown form of these rules is @@ -850,9 +850,20 @@ See also Rule 17.

Rule 9

-Each person may submit up to and including 10.000000 (ten in base 10) entries per contest. +Each person may register ONLY one account and each account may submit up to +and including 10.000000 (ten in base 10) entries per contest.

Each submission must be submitted separately.

+

+If this seems unreasonable we suggest you wait until the next contest, and in +the interim ponder this modified quote purportedly said by Bill Gates: +

+

+

+

10 submissions ought to be enough for anybody. :-)

+

– Bill Gates

+
+

Jump to: top

Rule 10

@@ -945,8 +956,8 @@ Your xz compressed tarball submission file must pass the tests

-The resulting directory produced when your xz compressed tarball submission file uncompressed, -must pass the pass the checks performed by: +The resulting directory produced when your xz compressed tarball submission file uncompressed +must pass the checks performed by:

-These [IOCCC rules](rules.html) are version **28.26 2025-02-28**. +These [IOCCC rules](rules.html) are version **28.27 2025-03-01**.

@@ -581,11 +581,22 @@ Jump to: [top](#)

-Each person may submit up to and including **10.000000** (ten in base 10) entries per contest. +Each person may register **ONLY** one account and each account may submit up to +and including **10.000000** (ten in base 10) entries per contest.

**Each submission _must be submitted separately_**. +

+If this seems unreasonable we suggest you wait until the next contest, and in +the interim ponder this modified quote purportedly said by Bill Gates: +

+ +

+> 10 submissions ought to be enough for anybody. :-) +> +> -- Bill Gates +

Jump to: [top](#) @@ -717,8 +728,8 @@ Your **xz compressed tarball** submission file must pass the tests performed by: *

`fnamchk(1)`

-The resulting directory produced when your **xz compressed tarball** submission file uncompressed, -must pass the pass the checks performed by: +The resulting directory produced when your **xz compressed tarball** submission file uncompressed +must pass the checks performed by:

*

`chkentry(1)`

@@ -734,7 +745,8 @@ The `.auth.json` and `.info.json` must be compatible with what hat `mkiocccentry would produce as well as pass the tests performed by:

-*

`jparse(1)`

+*

`jparse(3)`

+*

`chkentry(1)`

### TL;DR Rule 17 - Use `mkiocccentry(1)` to form your submission @@ -749,7 +761,7 @@ Using command line flags or input prompts to override checks and limits made by the above mentioned tools is **NOT** recommended and may result in your submission being rejected by the [IOCCC submit server](https://submit.ioccc.org) and/or the [IOCCC -Judges[(../judges.html). +Judges](../judges.html).

See the @@ -841,7 +853,7 @@ removed by the `clobber` rule.

Your `Makefile` **MUST** use a syntax that is compatible with `bash(1)` -and GNU `make(1)`. You are **ENCOURAGED** to use set `SHELL= bash` in +and GNU `make(1)`. You are **ENCOURAGED** to use `SHELL= bash` in your `Makefile`.

diff --git a/next/submit.html b/next/submit.html index c710d95cc..6a1a22a8f 100644 --- a/next/submit.html +++ b/next/submit.html @@ -435,34 +435,38 @@ might be offline and unreachable as a website.

To login, open https://submit.ioccc.org in your browser. Fill in your login credentials and click “Login”. It might look something like:

-

submit server login page

-

If you’ve not logged in before, you’ll have to change your password first. See -the file pw-change.html for more details. After that you will -have to log back in.

+

NOTE: if the contest is NOT open you will see something like this instead: +submit server contest closed

+

Assuming it is open, and if you’ve not logged in before, you’ll have to change +your password first. See the file pw-change.html for more +details. After that you will have to log back in.

Once you’ve logged in, you will see submit slots. Each slot is for one submission so if you update a submission, make sure you choose the right one so -you do not overwrite the wrong one!

+you do not replace the wrong one!

Here is what it looks like without any uploads and no slot selected:

-

submit server slots

Select a slot and then select a file by clicking the button “Choose File”. After doing this, it should look something like:

-

submit server slot and file selected

If you need to change the file to upload, you can mouseover the file and click it. If you wait a moment it’ll show the current filename. It will look something like this:

-

submit server change file

Once you’re certain you have selected the correct file, click “Submit”, below the file selection step.

When it’s uploaded it should look something like this:

-

submit server submission uploaded

Here you see the details, in particular:

@@ -481,14 +485,14 @@ tarball listing) your submissions. Here is what it will look like when the judges have verified that your tarball / submission has been validated (NOT judged), by txzchk(1) and chkentry(1):

-

submit server status updated

For details on txzchk, see the FAQ on “txzchk”.

For details on chkentry, see the FAQ on “chkentry”.

-

If you need more information on what chkentry checks, see the +

If you need more information on the two JSON files, see FAQ on the “.info.json file” and the FAQ on the “.auth.json file”.

diff --git a/next/submit.md b/next/submit.md index 5342015d9..dcf6d4376 100644 --- a/next/submit.md +++ b/next/submit.md @@ -13,29 +13,33 @@ To login, open [https://submit.ioccc.org](https://submit.ioccc.org) in your browser. Fill in your login credentials and click "Login". It might look something like: -submit server login page +**NOTE**: if the contest is NOT open you will see something like this instead: +submit server contest closed -If you've not logged in before, you'll have to change your password first. See -the file [pw-change.html](pw-change.html) for more details. After that you will -have to log back in. +Assuming it is open, and if you've not logged in before, you'll have to change +your password first. See the file [pw-change.html](pw-change.html) for more +details. After that you will have to log back in. Once you've logged in, you will see submit slots. Each slot is for one submission so if you update a submission, make sure you choose the right one so -you do not overwrite the wrong one! +you do not replace the wrong one! Here is what it looks like without any uploads and no slot selected: -submit server slots Select a slot and then select a file by clicking the button "Choose File". After doing this, it should look something like: -submit server slot and file selected @@ -43,7 +47,7 @@ If you need to change the file to upload, you can mouseover the file and click it. If you wait a moment it'll show the current filename. It will look something like this: -submit server change file @@ -52,7 +56,7 @@ the file selection step. When it's uploaded it should look something like this: -submit server submission uploaded @@ -74,7 +78,7 @@ your submissions. Here is what it will look like when the judges have verified that your tarball / submission has been validated (NOT judged), by `txzchk(1)` and `chkentry(1)`: -submit server status updated @@ -84,13 +88,12 @@ FAQ on "[txzchk](../faq.html#txzchk)". For details on `chkentry`, see the FAQ on "[chkentry](../faq.html#chkentry)". -If you need more information on what `chkentry` checks, see the +If you need more information on the two JSON files, see FAQ on the [".info.json file](../faq.html#info_json)" and the FAQ on the "[.auth.json file](../faq.html#auth_json)". -