mirror/ioccc
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
master
ioccc/news.md
T

899 lines
39 KiB
Markdown
Raw Permalink Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
<div id="news">
# News
</div>
<blockquote>
<table>
<tr>
<td colspan="3" style="padding-top: 12px;">
<span class="pseudo_h3">&nbsp;&nbsp;Support the IOCCC</span>
<span class="small_click_below">&nbsp;&nbsp;&nbsp;click below to support</span>
</td>
</tr>
<tr>
<td>
&nbsp;&nbsp;&nbsp;&nbsp;<a href="https://patreon.com/IOCCC"><img src="png/patreon.128x19.png" alt="Patreon logo" width=128 height=19></a>
</td>
<td>
&nbsp;&nbsp;&nbsp;&nbsp;<a href="https://coff.ee/ioccc"><img src="png/buymeacoffee.128x38.png" alt="Buy Me A Coffee logo" width=128 height=38></a>
</td>
<td>
&nbsp;&nbsp;&nbsp;&nbsp;<a href="https://github.com/sponsors/ioccc-src"><img src="png/GitHub.128x51.png" alt="GitHub logo" width=128 height=51></a>
</td>
</tr>
</table>
</blockquote>
<blockquote>
<table>
<tr>
<td colspan="3" style="padding-top: 12px;">
<span class="pseudo_h3">&nbsp;&nbsp;IOCCC on Social Media</span>
<span class="small_click_below">&nbsp;&nbsp;&nbsp;click below to visit</span>
</td>
</tr>
<tr>
<td style="padding-top: 8px;">
&nbsp;&nbsp;&nbsp;&nbsp;<a href="https://discord.gg/Wa42Qujwnw"><img src="png/Discord.128x37.png" alt="Discord logo" width=128 height=37></a>
</td>
<td style="padding-top: 12px; padding-bottom: 3px;">
&nbsp;&nbsp;&nbsp;&nbsp;<a href="https://fosstodon.org/@ioccc"><img src="png/mastodon.128x38.png" alt="Mastodon logo" width=128 height=38></a>
</td>
<td>
&nbsp;&nbsp;&nbsp;&nbsp;<a href="https://www.youtube.com/@OurFavoriteUniverse"><img src="png/YouTube.128x46.png" alt="YouTube logo" width=128 height=46></a>
</td>
</tr>
</table>
</blockquote>
<div id="20260118">
## 2026-01-18
</div>
The **IOCCC29** remains open to people who wish to [register for the IOCCC](next/register.html)
and then [upload submissions](next/submit.html) until `2026-03-13 17:19:23.293137 UTC`.
The servers, services, and software used to build, manage, and maintain
this site as well as to run the IOCCC itself are due, in part, to the
support from:
* [LaurieWired](https://www.youtube.com/@lauriewired)
<a href="https://www.youtube.com/@lauriewired"><img src="png/lauriewired_logo.png" alt="LaurieWired logo"
width=262 height=142></a>
<div id="20251130">
## 2025-11-30
</div>
The **IOCCC29** will run from `2025-12-03 20:25:12.045045 UTC` to `2026-03-13 17:19:23.293137 UTC`.
This contest will enter the [pending state](faq.html#pending) on `2025-12-03 20:25:12.045045 UTC`,
allowing people to [register for the IOCCC](next/register.html).
Please [provide feedback](faq.html#feedback) on the [IOCCC rules](next/rules.html),
[IOCCC guidelines](next/guidelines.html), and
on the [IOCCC mkiocccentry tools](https://github.com/ioccc-src/mkiocccentry),
especially while the [contest status](status.html) is **pending**.
This contest will enter the [open state](faq.html#open) on `2025-12-15 18:21:24.273033 UTC`,
allowing people to [upload submissions](next/submit.html).
See [entering the IOCCC](quick-start.html#enter).
This contest will enter the [judging state](faq.html#judging) on `2026-03-13 17:19:23.293137 UTC`,
when people will no longer be allowed to upload submissions.
The above **dates and times may change _AT ANY TIME_** until the [contest status](status.html) is **open**.
The above timestamps are in "_YYYY-MM-DD HH:MM:SS.micros UTC_" format.
<div id="20250806">
## 2025-08-06
</div>
The award presentations from the longer 4.5 hour [Our Favorite
Universe](https://www.youtube.com/@OurFavoriteUniverse) YouTube show
have been individually uploaded as short videos. Moreover, the main
page of each [IOCCC28 winning entry](years.html#2024) now contains a
link to their own individual YouTube show.
A number of improvements including corrections and improved
descriptions have been made to the [IOCCC Official Website](index.html).
We recommend you update your [IOCCC winner GibHub repo](https://github.com/ioccc-src/winner)
forks and/or download the [IOCCC winning entries of 2024](https://www.ioccc.org/2024/2024.tar.bz2)
compressed tarball.
<div id="20250802">
## 2025-08-02
</div>
### IMPORTANT UPDATE
We swapped by accident, both `2024/anders` and `2024/straadt`. Sorry (tm Canada 🇨🇦) about that!
If you downloaded the **IOCCC28** code before **2025 Aug 03 09:40:00 UTC**, please re-fetch the tarballs.
We **SINCERELY APOLOGIZE** to both **Anders Kaare Straadt** and **Sebastian Macke** for the mix up!
### IOCCC28 winning entries
The 40th Anniversary International Obfuscated C Code Contest has been
released, and we are delighted to share the winning entries from **IOCCC28**!
The source code for the IOCCC winner is now available on our
[IOCCC winner GitHub repo](https://github.com/ioccc-src/winner) as well as on
the [Official IOCCC website](index.html).
Congratulations to:
* [2024/burton](2024/burton/index.html) - Prize in pentagrammatology - _wordle hard mode solver_
* [2024/cable1](2024/cable1/index.html) - Prize in bot talk - _LLM inference engine_
* [2024/cable2](2024/cable2/index.html) - Prize in murky waters - _salmon recipe_
* [2024/carlini](2024/carlini/index.html) - Prize in perfect timing - _Intel 4004 emulation_
* [2024/codemeow](2024/codemeow/index.html) - Prize in tray planting - _bonsai generator_
* [2024/endoh1](2024/endoh1/index.html) - Prize in patient pointillism - _slow ray tracer in CPP_
* [2024/endoh2](2024/endoh2/index.html) - Prize in solid body physics - _rotating rigid body simulation_
* [2024/ferguson1](2024/ferguson1/index.html) - Prize in diabolical logistics - _A Pact With the Devil On the Oregon Trail_
* [2024/ferguson2](2024/ferguson2/index.html) - Prize in yil-tas - _Navajo Code Talker translator_
* [2024/howe](2024/howe/index.html) - Nice accent eh-ward - _mini vi_
* [2024/kramer](2024/kramer/index.html) - Prize in linguistic arithmetic - _natural language numerical calculator_
* [2024/kurdyukov1](2024/kurdyukov1/index.html) - Prize in phased periodicity - _phase of the Moon_
* [2024/kurdyukov2](2024/kurdyukov2/index.html) - Prize in art restoration - _JPEG artifact removal_
* [2024/kurdyukov3](2024/kurdyukov3/index.html) - Prize in virtual quietus - _gaming VM and doom_
* [2024/kurdyukov4](2024/kurdyukov4/index.html) - Prize in embiggening - _encode without literals_
* [2024/macke](2024/macke/index.html) - Prize in imitative rebooting - _OpenRISC CPU and Linux_
* [2024/maffiodo](2024/maffiodo/index.html) - Prize in creative interpretation - _Jav\*script interpreter_
* [2024/mills](2024/mills/index.html) - Prize in ℤ₃ - _Infocom v3 story interpreter_
* [2024/stedolan](2024/stedolan/index.html) - Best one liner - _icon from MD5_
* [2024/straadt](2024/straadt/index.html) - Prize in sound coding - _layered music generator_
* [2024/tmarrec](2024/tmarrec/index.html) - Prize in cyclonic coding - _3D tornado simulation_
* [2024/tompng](2024/tompng/index.html) - Prize in quasi bijection - _vortex encryptor decryptor_
* [2024/weaver](2024/weaver/index.html) - Sur prize - _rickroll_
The winning entries of **IOCCC28** were presented live on the YouTube Channel
"[Our Favorite Universe](https://www.youtube.com/@OurFavoriteUniverse)"
starting at **2025-08-02 18:00:00.00000 UTC**. A recording of the event is available
via the following link:
> [IOCCC28 Winning Entries | IOCCC Awards Presentation and Source Code Reveal](https://www.youtube.com/live/UDzGwTalVAc?si=0OyzacLR_PsylR1g)
We plan to periodically produce shows featuring some of the best of the
[IOCCC winning entries](years.html), commencing in a few weeks.
We kindly request that you **subscribe** to the
"[Our Favorite Universe](https://www.youtube.com/@OurFavoriteUniverse)"
YouTube Channel, and enable notifications (**click on the “Notification Bell” 🔔**)
to receive alerts when new content is scheduled.
## 2025-07-30
Good News Everyone ‼️🤓 We have scheduled the date for the **IOCCC Awards Presentation and Source Code Reveal** for **IOCCC28** to be on **2025 August 02 11:00 (11AM) Pacific**.
The presentation will be on the [Our Favorite Universe](https://www.youtube.com/@OurFavoriteUniverse) YouTube Channel on the show entitled:
> [IOCCC28 Winning Entries | IOCCC Awards Presentation and Source Code Reveal](https://www.youtube.com/live/UDzGwTalVAc?si=0OyzacLR_PsylR1g)
Please **Subscribe** and **click on the "Notification Bell" 🔔**
so that you can be reminded for when we go live.
As promised, the source code to the winners of **IOCCC28** will go live
on the [IOCCC winner GibHub repo](https://github.com/ioccc-src/winner)
as well at the [IOCCC Official Website](index.html) at the end of the
show. A recording of this show will be uploaded to the [Our Favorite
Universe](https://www.youtube.com/@OurFavoriteUniverse) YouTube Channel
for those who cannot watch the live show.
## 2025-07-08
On 2025-07-07, we had a successful 6-hour marathon meeting, accomplishing 2 crucial goals:
0) We have what we believe is the list of winners of **IOCCC28**.
1) We’ve selected a tentative date for the **IOCCC28** winners' live presentation
on the "Our Favorite Universe" YouTube channel. The winning source will be uploaded
to the [Official IOCCC website](index.html) during the show.
We look forward to presenting the 40th Anniversary IOCCC winners live on the
[Our Favorite Universe YouTube channel](https://www.youtube.com/@OurFavoriteUniverse),
reminiscent of the USENIX IOCCC BOFs that followed the BSD BOFs.
More importantly, unlike previous years, you won’t have to wait to view
the winning source. Near the end of the show, we’ll do a "git push"
to the [IOCCC repo](https://github.com/ioccc-src/winner).
We’re putting significant effort to complete the write-up for the
**IOCCC28** winners and figure out how to show them live on the air, solving
some fun logistical challenges along the way.
We’ll share the YouTube show URL about 72 hours before the actual date.
Kindly subscribe to the
[Our Favorite Universe YouTube channel](https://www.youtube.com/@OurFavoriteUniverse),
(it’s free) and click the notification bell (🔔) to receive an alert for when the show is
scheduled by visiting:
[https://www.youtube.com/@OurFavoriteUniverse](https://www.youtube.com/@OurFavoriteUniverse)
## 2025-06-05
The **IOCCC28** period for submission has closed.
We will post a few high level updates on [Mastodon](https://fosstodon.org/@ioccc),
plus some j-random more in-depth fun updates for our
[IOCCC Patrons](https://www.patreon.com/c/IOCCC) while we judge.
**Q**: How long will it take for the @IOCCC Judges to judge **IOCCC28**?
**A**: It all depends on a combination of quantity and quality of the submissions!
We hope to see you all at the live **IOCCC28**
winner reveal show on the
[Our Favorite Universe YouTube channel](https://www.youtube.com/@OurFavoriteUniverse).
The winners will be posted to the IOCCC website at the end of the show.
**SUBSCRIBE** 👍 and click on the **NOTIFICATION BELL** 🔔 to be notified about
when when live **IOCCC28** winner reveal show happens!
## 2025-05-29
The **IOCCC28** OPEN period has only one week left! You have until **2025-06-05 04:03:02.010099 UTC**
to upload your submission(s). For more information see:
> [Entering the IOCCC](https://www.ioccc.org/quick-start.html#enter).
Once winners of **IOCCC28** have been chosen by the [The Judges](judges.html), we’ll reveal them
live on our YouTube channel, [Our Favorite Universe](https://www.youtube.com/@OurFavoriteUniverse)
and post the winning source to the [Official IOCCC website](https://www.ioccc.org/index.html)
at the end of the show. Make sure to subscribe to
[Our Favorite Universe](https://www.ioccc.org/index.html) and click on the notification bell 🔔 to get a
heads up when they’re announced!
## 2025-05-05
The **IOCCC28** OPEN period has one month left! You have until **2025-06-05 04:03:02.010099 UTC**
to upload your submission(s). For more information see:
> [Entering the IOCCC](https://www.ioccc.org/quick-start.html#enter).
If you are not yet registered for the **IOCCC28** and plan to enter the contest, we encourage you register ASAP:
> [How to register for the IOCCC](https://www.ioccc.org/next/register.html)
We released [mkiocccentry toolkit](https://github.com/ioccc-src/mkiocccentry) **version 2.4.8 2025-05-05**.
While you are **NOT** required to use this **NEW release** in order to submit to the **IOCCC28**,
we **RECOMMEND** that you **install and use**
[version version 2.4.8 2025-05-05](https://github.com/ioccc-src/mkiocccentry)
because among other things, it provides:
* Improved the format of how `mkiocccentry(1)` announces doing a `make clobber`.
* Improved `chkentry(1)` man page and the `chkentry -h` usage message.
## 2025-04-26
We released [mkiocccentry toolkit](https://github.com/ioccc-src/mkiocccentry) **version 2.4.6 2025-04-26**.
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:
* Enhanced the scanning process of topdir, excluding ignored files and directories from the count against the maximum allowed limit.
* Clarified the purpose of a submission title to emphasize that it should not contain names.
* Default handles may now contain UPPERCASE letters.
The **IOCCC28** is [open for registration](https://www.ioccc.org/next/register.html).
Those who have registered have until **2025-06-05 04:03:02.010099 UTC** to
[upload their submissions](https://www.ioccc.org/next/submit.html).
See "[how enter the IOCCC](https://www.ioccc.org/quick-start.html#enter)" for more information.
## 2025-04-19
The **IOCCC28** **OPEN** period has reached the half-way point.
This is a _gentle suggestion_ to not wait until the last minute to write, test
and upload your submission.
The **IOCCC28** is [open for registration](https://www.ioccc.org/next/register.html).
Those who have registered have until **2025-06-05 04:03:02.010099 UTC** to
[upload their submissions](https://www.ioccc.org/next/submit.html).
See "[how enter the IOCCC](https://www.ioccc.org/quick-start.html#enter)" for more information.
## 2025-03-15
We released [mkiocccentry toolkit](https://github.com/ioccc-src/mkiocccentry) **version 2.4.4 2025-03-15**.
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:
* Set locale to **C**, the **official locale** of the **IOCCC**.
See the [version 2.4.4 release notes](https://github.com/ioccc-src/mkiocccentry/releases/tag/2.4.4) for more details.
## 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
submissions from **2025-03-05 23:19:17.131107 UTC** to **2025-06-05 04:03:02.010099 UTC**.
Version **28.30 2025-03-03** of the [IOCCC28 rules](next/rules.html),
version **28.44 2025-03-04** of the [IOCCC28 guidelines](next/guidelines.html), and
version **2.4.2 2025-03-02** of the [mkiocccentry toolkit](https://github.com/ioccc-src/mkiocccentry),
are now [official](next/index.html).
See the [IOCCC quick start guide](quick-start.html#enter) for how to enter, and
the [mkiocccentry repo FAQ](faq.html#mkiocccentry) for
information on the [mkiocccentry toolkit](https://github.com/ioccc-src/mkiocccentry) and
the [IOCCC FAQ](faq.html) for general information on the [IOCCC](index.html).
In order to [submit to the IOCCC28](next/submit.html) you must be
[registered for the IOCCC28](next/register.html). **DO NOT** wait until the last minute
to register as the process can take a bit of time to complete!
Those who registered while the contest was **pending**
should have received their [IOCCC submit server](https://submit.ioccc.org)
and initial password by email. If you cannot find that email, contact the
[IOCCC Judges by email](contact.html#if-you-really-need-to-send-email-the-ioccc-judges)
for help. We have given early registrants extra time (until **2025 Mar 12 UTC**), to login
and change their initial password.
## 2025-02-28
We have reached our **code freeze** milestone for the [mkiocccentry repo](https://github.com/ioccc-src/mkiocccentry) and released a new version of the [mkiocccentry toolkit](faq.html#mkiocccentry)!
Final testing is going well. We remain on track to open the **IOCCC28** on **2025-03-05 23:19:17.131107 UTC**.
In a few days, those [registered for IOCCC28](https://www.ioccc.org/next/register.html) will receive email with their username and initial password to [submit their code](https://submit.ioccc.org).
We encourage those who wish to enter the **IOCCC28** to [registered for IOCCC28](https://www.ioccc.org/next/register.html) today.
Consider joining the IOCCC discord community via this link: [https://discord.gg/Wa42Qujwnw](https://discord.gg/Wa42Qujwnw)
## 2025-02-12
We have discovered an issue that needs to be resolved, followed by more testing
after the code freeze. We also want to improve the [IOCCC28 guidelines](next/guidelines.html),
and to simplify the write-up of the [IOCCC28 rules](next/rules.html).
The [40th anniversary of the IOCCC](faq.html#ioccc_start), which started
on **2024-12-29 23:58:13.213455 UTC**, is now scheduled to be **open**
from **2025-03-05 23:19:17.131107 UTC** to **2025-06-05 04:03:02.010099 UTC**.
We apologize for this delay.
## 2025-01-28
**IMPORTANT DISCORD UPDATE**: Due to a Discord bug/mis-feature, those
who joined the [IOCCC Discord server](https://discord.gg/Wa42Qujwnw)
recently lost their access soon afterwards and have to re-join.
We apologise for the inconvenience of having to rejoin.
The IOCCC now has a [Discord server](https://discord.gg/Wa42Qujwnw)!
Fans of the IOCCC, hopeful **IOCCC28** contestants, and past winners of the IOCCC
are all encouraged to stop by and say hello.
To join, click this link:
[https://discord.gg/Wa42Qujwnw](https://discord.gg/Wa42Qujwnw).
## 2025-01-25
The IOCCC now has a [Discord server](https://discord.gg/Wa42Qujwnw)!
Click the link to join the [IOCCC Discord server](https://discord.gg/Wa42Qujwnw).
Fans of the IOCCC, hopeful **IOCCC28** contestants, and past winners of the IOCCC
are all encouraged to stop by and say hello.
Based on user input and suggestions, we have been working on some new
functionality for the [mkiocccentry toolkit](faq.html#mkiocccentry).
In order to complete and fully test this new functionality, we need
additional time. Therefore the **IOCCC28 open** date has been **moved
forward by 19 days**. Moreover, and also by request, the contest will
remain **open for an additional month**.
The [40th anniversary of the IOCCC](faq.html#ioccc_start), which started
on **2024-12-29 23:58:13.213455 UTC**, is now scheduled to be **open**
from **2025-02-19 23:19:17.130705 UTC** to **2025-05-19 23:29:31.374143
UTC**. We will update the [IOCCC rules](next/rules.html) and
[IOCCC guidelines](next/guidelines.html) accordingly, before the contest opens.
## 2024-12-31
We have just released [version 2.3 of the mkiocccentry repo](https://github.com/ioccc-src/mkiocccentry/releases/tag/v2.3).
This repo 2.3 release includes important improvements (over repo release 2.1) to the `mkiocccentry(1)` tool
as well as a critical fix for installing on BSD based systems.
Please download [version 2.3 of the mkiocccentry repo](https://github.com/ioccc-src/mkiocccentry/releases/tag/v2.3),
and compile the [mkiocccentry tool set](faq.html#mkiocccentry). You may also wish to install this code.
See also the [mkiocccentry FAQ](https://github.com/ioccc-src/mkiocccentry/blob/master/FAQ.md) for more information.
## 2024-12-30
The IOCCC [Rule 12 - UTF-8](next/rules.html#rule12-utf8) no longer discourages the
use of UTF-8 in C source. Since the days of `-std=gnu17` compilers,
UTF-8 characters do not impose a compiler problem. The related guideline
states that "Rule 13 no longer discourages the use of UTF-8 +characters in C code".
The IOCCC [Rule 8 - Submitting requirements](next/rules.html#rule8-submitting-requirements) wording has been fixed. It no longer
states that email will be sent. Instead it talks about potential slot comment
modifications as means to tell the submitter that their submission was received.
All of the import IOCCC dates within the [IOCCC rules](next/rules.html)
have been moved into the "[Important IOCCC dates](next/rules.html#dates)"
section.
## 2024-12-28
### Good News Everyone! :-)
After a 4 year effort by a [number of people](thanks-for-help.html),
with over 6168+ commits, the **Great Fork Merge** has been completed
and the [Official IOCCC website](index.html) has been updated!
A significant number of improvements have been made to the
[IOCCC winning entries](years.html).
Many of the fixes and improvements involve the ability of reasonable modern
Unix/Linux systems to be able to compile and even run older winning entries.
See [FAQ Section 4](faq.html#compiling) for
information on how to compile.
See the [FAQ Section 8](faq.html#changes)
for details on changes made to the entries.
We hope you enjoy the new and improved
[Official IOCCC website](index.html).
This website is backed by the
[IOCCC winner GitHub repo](https://github.com/ioccc-src/winner).
See [FAQ Section 9](faq.html#help) for
how you can help [improve / fix the website](faq.html#fix_website),
or fix [known bugs in IOCCC winning entries](bugs.html).
### IOCCC28 is starting!
The IOCCC28, the [40th anniversary of the IOCCC](faq.html#ioccc_start) is now
scheduled to run from **2024-12-29 23:58:13.213455 UTC** to **2025-04-01 23:29:31.374143 UTC**!!!.
The [contest status](status.html) has been changed to "**pending**"
and [status.json](status.json) has been updated to reflect this new status.
Proposed and tentative [IOCCC rules](next/rules.html) and [IOCCC guidelines](next/guidelines.html)
have been released.
See [FAQ Section 0](quick-start.html#enter_questions) for more information on how to enter.
## 2024-06-08
We continue to make good progress on the
[temp-test-ioccc website](https://ioccc-src.github.io/temp-test-ioccc/)
via the [temp-test-ioccc](https://github.com/ioccc-src/temp-test-ioccc) repo.
One of the [largest html
files](thanks-for-help.html) has
been checked for broken links which leaves two longer files to go. These two
files are the [bugs.html](bugs.html)
file and the "[IOCCC FAQ](faq.html)".
However, where it was thought that those two files would be looked at before the
other html files, it has been decided that they will be done after the other
files as it is very possible that some things in these two files will have to be
changed or added as the other files are reviewed for broken links.
As of today, 08 June 2024, the top level html files are being looked at, with at
least three done already ([judges.html](judges.html), [news.html](news.html) and
[status.html](status.html)). This should not take more than a few days if things
go as planned, as these files are small and should be relatively quick and easy
to check for broken links. Of course, some of these, like the
[news.html](news.html) and possibly [status.html](status.html) will likely have to be
checked again but as for [news.html](news.html) the dates up to and including _08
June 2024_ have been checked for invalid links so that only new news updates
will have to be checked.
Once those are done the html files of all the entries will be looked at. As
those are being reviewed it the [bugs.html](bugs.html) might very well be
updated and the "[IOCCC FAQ](faq.html)" might be as well. This is why, as noted above,
we have decided to review these files last, in order to save time and effort in
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.
Once the _submit server_ server is ready another FAQ will be added and that
entry can be looked at alone.
## 2024-05-30
A number of issues from minor fixes have been applied to the
[temp-test-ioccc website](https://ioccc-src.github.io/temp-test-ioccc/)
via the [temp-test-ioccc](https://github.com/ioccc-src/temp-test-ioccc) repo.
437 commits have been applied since 2024-04-20, bringing the total
number to 5260 commits to date. The
[temp-test-ioccc](https://github.com/ioccc-src/temp-test-ioccc)
repo is now 5159 commits ahead of the [IOCCC
winner](https://github.com/ioccc-src/winner) repo.
Multiple **((top priority))** issues have been resolved or completed.
Only one **((top priority))** issue, [issue
2006](https://github.com/ioccc-src/temp-test-ioccc/issues/2006)
remains before we begin the final steps to perform the **Great Fork
Merge** when the [Official IOCCC web
site](https://www.ioccc.org/index.html) will be updated. And although there are
a lot of files to look at for this issue, most of them should go relatively
quickly, once these are started. One of the slower files is almost done and then
there are two more before we can look at the other files.
The [issue 2239](https://github.com/ioccc-src/temp-test-ioccc/issues/2239)
TODO list has 10 out of 51 sub-tasks completed. That might not
seem like much progress, but keep in mind that some of those 10
tasks took many months and thousands of commits to complete.
Moreover, most of the remaining 41 TODO items are short "checkbox"
tasks. The final 31 TODO items are planned to be completed in about
a single day.
The **IOCCC Submit server** is in active development. We plan to
update the FAQ with screenshots from the IOCCC Submit server as
well as the **IOCCC registration process** prior to starting the
**Great Fork Merge**.
We have decided to **NOT** hold an **IOCCC mock** contest, but instead
ask for beta testing of the new **IOCCC registration process** and
**IOCCC Submit server** when they have left alpha testing phase.
This will speed up the start date of IOCCC28.
It is our plan that IOCCC28 will occur in 2024, the 40th anniversary of the
IOCCC.
## 2024-04-30
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 _hamburger-style_ menu icon in place of
drop-down menus at the very top of the page (called the _topbar_).
Any mobile device with a screen wider than 1024 pixels will need
to _press and hold_ to force the _topbar_ pull-down menu to activate.
We had to introduce the use of JavaScript to activate a _hamburger-style_
menu icon due to the way mobile device screen touching works. Those
devices without JavaScript (or when JavaScript has been disabled)
will be given a link to a web page that presents the equivalent menu.
Fixed generated HTML files where a link to a local file was invalid.
Previous problems included malformed markdown, the local file was
missing, the local file is generated by make or the entry itself, etc.
The generated HTML files (via `bin` tools) and other HTML files are
now conform with HTML 5 standards. The **Nu Html Checker** reports
**no error, warnings, nor info** messages.
The *Nu Html Checker** change from _2024-04-20_ is that the HTML
files that are static (not generated `bin` tools) report **no error,
warnings, nor info** messages, changes involving fixing invalid
links to local files have been corrected, and changes involving the
_topbar_ are now HTML 5 conforming.
## 2024-04-20
Nearly all of the [temp-test-ioccc website](https://ioccc-src.github.io/temp-test-ioccc/)
website has undergone editorial review. Nearly all [IOCCC winning entries](years.html)
compile on modern systems and many have `try.sh` scripts to help you run them.
For those that cannot compile and/or do not work, we have made a
[Bugs and &lpar;Mis&rpar;features](bugs.html) page.
We have made nearly 4823 changes to date!
All generated HTML pages are now conform to HTML 5 with the
[Nu Html Checker](https://validator.w3.org/nu/) reporting **no error, warnings, nor info** messages.
The [IOCCC judges](judges.html) have contracted with a web designer
to improve the overall look of the website, while **maintaining
the utilitarian look and feel**, and without introducing any
glaring "_dancing bears_" and other frivolous web features.
We are working towards what we call the
**[Great Fork Merge](https://github.com/ioccc-src/temp-test-ioccc/issues/2239)**
where the contents of the [temp-test-ioccc website](https://ioccc-src.github.io/temp-test-ioccc/)
will be merged into the [Official IOCCC website](https://www.ioccc.org/index.html).
Stay tuned!
## 2024-02-29
We continue to make good progress on website. In the [temp-test-ioccc GitHub repo](https://github.com/ioccc-src/temp-test-ioccc) we have made nearly 4600 changes to date!
All web pages, including this one, are now constructed from markdown files and/or JSON data files using tools found in the [bin](bin/index.html) directory.
## 2023-05-22
We have been busy preparing for an important / significant update to this website. In the [temp-test-ioccc GitHub repo](https://github.com/ioccc-src/temp-test-ioccc) we have made nearly 2645 changes to date.
While you are free to look at the [temp-test-ioccc GitHub repo](https://github.com/ioccc-src/temp-test-ioccc),
please **do not link to it** as this repo and related website will disappear once the main
[IOCCC winner repo](https://github.com/ioccc-src/winner) has been updated.
Also be aware that the [temp-test-ioccc GitHub repo](https://github.com/ioccc-src/temp-test-ioccc)
is undergoing rapid changes. There are broken links and other things in mid-change.
Once we are ready to update the [IOCCC winner repo](https://github.com/ioccc-src/winner)
and its associated website,
we will post a news article warning of the pending change that is about to arrive.
These 2645+ changes in the [temp-test-ioccc GitHub repo](https://github.com/ioccc-src/temp-test-ioccc)
include diverse things such as:
* Moving IOCCC entries into their own separate directories
* Fixing lots and lots of typos
* Fixing Makefiles and code to allow for nearly all winning IOCCC entries to be compiled on modern systems
* Reworking the Makefiles to use a consistent set of rules
* Reworking the Makefiles to compile under gcc and clang
* Replacing the various hint files with a index.html markdown that is more consistent across IOCCC years
* Setting up a system whereby authors of IOCCC entries may update their own contact information via a GitHub pull request
* Setting up to generate the top level [years.html](years.html) file via a tool
* Setting up to generate the top level [authors.html](authors.html) file via a tool
* etc.
We have lots more to do. Our work is not finished. We just wanted to let you know that we are making good progress.
In regards to the next IOCCC. We **do plan to hold a 28th IOCCC**. However before we do that, we plan
to hold what will be called **IOCCCMOCK**, a beta-test IOCCC where we plan to test the new
[mkiocccentry tool](https://github.com/ioccc-src/mkiocccentry), a tool that will package
submissions to the IOCCC.
We are working on an improved **IOCCC submit server**
that will allow those who submit entries to be informed about the status of their submission.
This **IOCCC submit server** will be beta tested in the **IOCCCMOCK**.
We are working on a method to rapidly post the winning entries of an IOCCC. No longer will entries
be subject to a long delay between announcing that they have won and their code being made available.
No longer will procrastination delay the public seeing the winning code. Instead the
**announcement of the winning entries of an IOCCC will be done by posting the winning code via a GitHub commit.**
Any corrections, improvement, typo fixes and other fixes will be applied to the winning entries via GitHub pull requests:
by the authors and/or other interested 3rd parties.
All the above represent one of the most significant (and useful) changes to the IOCCC since it started back in 1984.
While we are doing lots of testing, we are sure that issues, mis-features and even bugs will be uncovered
when we **go live**. For this reason, we plan to beta-test the process by holding an **IOCCCMOCK**.
The **IOCCCMOCK** will be like a regular IOCCC except that the judges **will not** judge the code.
Instead, people will be invited to submit a simple _"Hello, world!"_ style program.
Awards will be given to those who:
* submit the best pull requests that fix a bug
* submit the best pull requests that fix a typo
* make the best suggestions for improvements
* have the most fun / make us laugh
* etc.
The **IOCCCMOCK** will allow is to restart the beta-test contest should a major problem be discovered
that needs urgent fixing.
The **IOCCCMOCK** will us to beta-test the new IOCCC process without putting the hard work of those
who submit real IOCCC entries at risk.
Stay tuned!
## 2023-01-30
We added to the
[status.json](status.json) page,
a _"status_date"_ JSON member whose value is the date
of the most recent [status.json](status.json) modification,
in _date(1)_ format.
We also added to the
[status.json](status.json) page,
a _"latest_news"_ JSON member whose value is the date
of the most recent news item.
``` <!---json-->
"status_date" : "Mon Jan 30 02:28:44 PST 2023",
"latest_news" : "Mon Jan 30 02:28:44 PST 2023"
```
## 2022-12-18
As per the suggestion of [Toni Mikkola
&lpar;@Virtaava@home.social&rpar;](https://fosstodon.org/@Virtaava@home.social)
we now maintain a [status.json](status.json) page on this website.
In addition to the IOCCC-style _Easter egg_, you may count on
the JSON status page having a JSON member with name of **"contest"**
that will have a value of either **"closed"** or **"open"**.
When a future **IOCCC** is announced or the IOCCC is currently open,
the JSON member with name of **"contest"** will change from
**"closed"** to **"open"**.
Additional JSON members be added describing the contest such as
the IOCCC contest number, open date, close date, timezone, etc.
The details of such additional JSON members are _TBD_.
When an open IOCCC closes, we won't instantaneously update the
[status.json](status.json) page.
Instead you will have to rely on the additional JSON information
and/or read the [IOCCC news](#news),
and/or follow us on Mastodon via **@ioccc@fosstodon.org**.
## 2022-11-29
We are planning to abandon our
[IOCCC Twitter feed](https://twitter.com/ioccc)
in favor of our new [IOCCC Mastodon](https://fosstodon.org/@ioccc) feed.
Our Mastodon username is: **@ioccc@fosstodon.org**.
```
Please note: As of the date of this posting, our account was just setup,
so there isn't much to read there, yet.
```
In the future we plan to use Mastodon as our official announcement platform.
This will include announcing:
* IOCCC news updates
* Start of a new IOCCC
* Updates on the IOCCC judging process
* Who won the IOCCC
* et**C**. :-)
When registering for a new IOCCC, we will no longer ask for an optional twitter handle.
Instead, you will be asked if you wish to provide a Mastodon username when you submit your IOCCC entry.
Use of Mastodon is **NOT** required to enter the IOCCC, but nevertheless is encouraged.
Proving a Mastodon username will be entirely **optional**.
Non-mastodon users can follow the IOCCC postings via:
[fosstodon.org/@ioccc](https://fosstodon.org/@ioccc).
If you do not yet have a Mastodon account, you may obtain a **free mastodon account via**:
[joinmastodon.org](https://joinmastodon.org).
If you do have / obtain a Mastodon account, **please do us a favor and follow the IOCCC at**:
```
@ioccc@fosstodon.org
```
The IOCCC wishes to thank the good folk running the
[fosstodon.org](https://hub.fosstodon.org/about/)
Mastodon hub.
Their technology focused
[Fosstodon Hub](https://hub.fosstodon.org)
is made possible by volunteers,
and those who voluntarily
[support](https://hub.fosstodon.org/support/) the cost of their server.
Stay tuned in Mastodon as we update you on our progress towards the next IOCCC!
## 2022-11-19
Source code has been released for version **0.8.1 2022-11-19** of the
[mkiocccentry repo](https://github.com/ioccc-src/mkiocccentry),
a GitHub repo that includes the official iocccsize tool,
and a tool will form a compressed tarball of their entry.
We are working on a submit server that will allow a registered IOCCC contestant
to upload the above mentioned compressed tarball: when the contest is open of course.
Once we reach version 1.0, we plan to invite the public to test and comment.
We plan to hold in 2023, what we will call **IOCCCMOCK**, a trial IOCCC contest where the
judges will go through the motions (without judging the content) of an IOCCC:
testing the above mentioned tools and testing the submit server.
We are working on complete rebuild of this website as well.
## 2022-01-15
Source code has been released for version **0.24 2022-01-15** of the
[mkiocccentry tool](https://github.com/ioccc-src/mkiocccentry),
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).
## 2021-12-27
[The Judges](judges.html)
are continuing to work on re-tooling how we run the IOCCC.
We are writing tools under various repositories our
[IOCCC GitHub organization site](https://github.com/ioccc-src).
**We plan to hold IOCCC28 in 2023.**
Sorry for the delay, but we think you will appreciate the re-tooling
when it is completed.
Stay tuned!
## 2021-10-21
[The Judges](judges.html)
are re-tooling how we run the IOCCC.
Our goal is to build a smoother, more rapid process centered around
[GitHub](https://github.com/ioccc-src/winner).
For example, when we announce the winning entries of the IOCCC,
we will do so by committing their code to the
[Winning entries](years.html)
of the IOCCC repo, so that people will be able immediately
view the winning source.
We plan to refactor and modernize the IOCCC website.
We also plan to build a new and improved way to submit entries the next IOCCC.
As a result of all this work we need to do,
**we plan to hold IOCCC28 in 2023 instead of 2021**.
Sorry for the delay, but we think you will appreciate the re-tooling
when it is completed.
**Stay tuned for how you may be able to help in the IOCCC redesign for IOCCC28!**
<hr style="width:10%;text-align:left;margin-left:0">
Jump to: [top](#)
<!--
Copyright © 1984-2025 by Landon Curt Noll. All Rights Reserved.
You are free to share and adapt this file under the terms of this license:
Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)
For more information, see:
https://creativecommons.org/licenses/by-sa/4.0/
-->
Reference in new issue View Git Blame Copy Permalink