diff --git a/next/pw-change.html b/next/pw-change.html
index eac38a34f..ed3fb1dbc 100644
--- a/next/pw-change.html
+++ b/next/pw-change.html
@@ -428,7 +428,7 @@
Using the Username and Initial password you receive via
email in step 3, you need to login to the IOCCC submit
server.
-IMPORTANT NOTE: You must change your password WITHIN 72 HOURS
+
IMPORTANT NOTE: You must change your password within a fortnight (14 days)
from when one of the IOCCC judges sent that email.
NOTE: The IOCCC submit server will be ready
for submissions ONLY WHEN THE CONTEST IS open. See
@@ -463,12 +463,14 @@ Your password MUST be:
- New password must NOT have been Pwned
Pwned passwords are passwords that have been previously exposed in some published data breach.
-Again, if you do not change your password within 72 hours YOUR ACCOUNT WILL BE
-CLOSED and you’ll have to register again! In that case it’ll say something
-like:
+Again, if you do not change your password within fortnight (14 days)
+your account will be closed and it’ll say something line:
ERROR: Sorry (tm Canada 🇨🇦) you cannot login at this time.
+If that happens, you will need to
+send email to the IOCCC judges
+to ask for your password to be reset.
Assuming you did login in time, you should put in your login (UUID username),
your old (initial) password and a new password and then click “Change Password”.
NOTE: if you have put in your old password, you’ll get the following error:
diff --git a/next/pw-change.md b/next/pw-change.md
index e31cff818..0e5ff0ad1 100644
--- a/next/pw-change.md
+++ b/next/pw-change.md
@@ -4,7 +4,7 @@ Using the **Username** and **Initial password** you receive via
email in [step 3](../quick-start.html#step_3), you need to login to the [IOCCC submit
server](https://submit.ioccc.org).
-**IMPORTANT NOTE**: You must change your password **WITHIN 72 HOURS**
+**IMPORTANT NOTE**: You must change your password within a fortnight (**14 days**)
from when one of the [IOCCC judges](../judges.html) sent that email.
**NOTE**: The [IOCCC submit server](https://submit.ioccc.org) will be ready
@@ -45,12 +45,15 @@ new password.
>
> [Pwned](https://haveibeenpwned.com/Passwords) passwords are passwords that have been previously exposed in some published data breach.
-Again, if you do not change your password within 72 hours **YOUR ACCOUNT WILL BE
-CLOSED** and you'll have to register again! In that case it'll say something
-like:
+Again, if you do not change your password within fortnight (**14 days**)
+your account will be closed and it'll say something line:
> **ERROR: Sorry (tm Canada 🇨🇦) you cannot login at this time.**
+If that happens, you will need to
+[send email to the IOCCC judges](if-you-really-need-to-send-email-the-ioccc-judges)
+to ask for your password to be reset.
+
Assuming you did login in time, you should put in your login (UUID username),
your old (initial) password and a new password and then click "Change Password".
diff --git a/next/rules.html b/next/rules.html
index 5bdc186b3..770fbc232 100644
--- a/next/rules.html
+++ b/next/rules.html
@@ -675,16 +675,12 @@ becomes open.
Once that email with your Username and Initial password is sent, you
-will have 72 hours to change your submit server initial password.
+will have fortnight (14 days) to change your submit server initial password.
-If you do not change your Initial password in time, you will have
-to contact an IOCCC judge by email and ask them to reset
-your password. Not only is this a hassle for everyone involved, it will
-delay your IOCCC registration process, perhaps by a number of days that
-egrep(1) would be able to pattern match. By egrep(1), we refer to the
-long standing UNIX utility that should just run and NOT whine about
-the command being allegedly deprecated.
+If you do not change your Initial password in time, you will have to
+send email to the IOCCC judges
+to ask for your password to be reset.
Because it takes time (maybe even a few days) to process your registration
diff --git a/next/rules.md b/next/rules.md
index 8964c7645..8d922d4f4 100644
--- a/next/rules.md
+++ b/next/rules.md
@@ -345,17 +345,13 @@ becomes **[open](../faq.html#open)**.
Once that email with your **Username** and **Initial password** is sent, you
-will have **72 hours** to [change your submit server initial password](pw-change.html).
+will have fortnight (**14 days**) to [change your submit server initial password](pw-change.html).
-If you do not change your **Initial password** in time, **you will have
-to [contact an IOCCC judge](../contact.html)** by email and ask them to reset
-your password. Not only is this a hassle for everyone involved, it will
-delay your IOCCC registration process, perhaps by a number of days that
-`egrep(1)` would be able to pattern match. By `egrep(1)`, we refer to the
-long standing **UNIX** utility that should just run and **NOT** whine about
-the command being allegedly deprecated.
+If you do not change your **Initial password** in time, you will have to
+[send email to the IOCCC judges](if-you-really-need-to-send-email-the-ioccc-judges)
+to ask for your password to be reset.
diff --git a/sitemap.xml b/sitemap.xml
index 22ae8326f..fba2d3d3c 100644
--- a/sitemap.xml
+++ b/sitemap.xml
@@ -15226,7 +15226,7 @@
https://www.ioccc.org/bin/cvt-submission.sh
- 2025-04-16T20:59:19+00:00
+ 2025-05-02T23:10:17+00:00
https://www.ioccc.org/bin/entry2csv.sh
@@ -15518,11 +15518,11 @@
https://www.ioccc.org/next/pw-change.html
- 2025-04-16T20:59:19+00:00
+ 2025-05-02T23:21:36+00:00
https://www.ioccc.org/next/pw-change.md
- 2025-04-16T20:59:19+00:00
+ 2025-05-02T23:18:21+00:00
https://www.ioccc.org/next/README.md
@@ -15546,11 +15546,11 @@
https://www.ioccc.org/next/rules.html
- 2025-04-17T23:44:51+00:00
+ 2025-05-02T23:21:37+00:00
https://www.ioccc.org/next/rules.md
- 2025-04-17T23:44:27+00:00
+ 2025-05-02T23:20:26+00:00
https://www.ioccc.org/next/submit.html
@@ -15598,7 +15598,7 @@
https://www.ioccc.org/status.html
- 2025-04-29T18:20:29+00:00
+ 2025-05-02T23:21:41+00:00
https://www.ioccc.org/status.json