Files
ioccc/news.html
T

688 lines
29 KiB
HTML
Raw 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.
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<!-- START: two lines up starts content from: inc/top.default.html -->
<!-- END: this line ends content from: inc/top.default.html -->
<!-- START: this line starts content from: inc/head.default.html -->
<head>
<link rel="stylesheet" href="./ioccc.css">
<link href="https://fonts.googleapis.com/css2?family=Outfit:wght@100..900&display=swap" rel="stylesheet">
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=yes">
<title>The International Obfuscated C Code Contest</title>
<link rel="icon" type="image/x-icon" href="./favicon.ico">
<meta name="description" content="News and notices of the IOCCC">
<meta name="keywords" content="IOCCC, IOCCC news, news">
</head>
<!-- !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! -->
<!-- !!! DO NOT MODIFY THIS FILE - This file is generated by a tool !!! -->
<!-- !!! DO NOT MODIFY THIS FILE - This file is generated by a tool !!! -->
<!-- !!! DO NOT MODIFY THIS FILE - This file is generated by a tool !!! -->
<!-- !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! -->
<!-- END: this line ends content from: inc/head.default.html -->
<!-- -->
<!-- This web page was formed via the tool: bin/gen-top-html.sh -->
<!-- The content of main section of this web page came from: news.md -->
<!-- -->
<!-- !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! -->
<!-- !!! Do not modify this web page, instead modify the file: news.md !!! -->
<!-- !!! Do not modify this web page, instead modify the file: news.md !!! -->
<!-- !!! Do not modify this web page, instead modify the file: news.md !!! -->
<!-- !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! -->
<!-- Markdown content was converted into HTML via the tool: bin/md2html.sh -->
<!-- START: this line starts content from: inc/body.default.html -->
<body>
<!-- END: this line ends content from: inc/body.default.html -->
<!-- START: this line starts content from: inc/topbar.default.html -->
<div class="theader">
<nav class="topbar">
<div class="container">
<div class="logo">
<a href="./index.html" class="logo-link">
IOCCC
</a>
</div>
<div class="topbar-items">
<div class="item">
<span class="item-header">
Entries
</span>
<div class="sub-item">
<div class="outfit-font">
<a href="./years.html" class="sub-item-link">
Winning Entries
</a>
</div>
<div class="outfit-font">
<a href="./authors.html" class="sub-item-link">
People who have won
</a>
</div>
<div class="outfit-font">
<a href="./location.html" class="sub-item-link">
Location of authors
</a>
</div>
<div class="outfit-font">
<a href="./bugs.html" class="sub-item-link">
Bugs &amp; (Mis)features
</a>
</div>
</div>
</div>
<div class="item">
<span class="item-header">
Status
</span>
<div class="sub-item">
<div class="outfit-font">
<a href="./news.html" class="sub-item-link">
IOCCC News
</a>
</div>
<div class="outfit-font">
<a href="./status.html" class="sub-item-link">
Contest status
</a>
</div>
<div class="outfit-font">
<a href="./next/index.html" class="sub-item-link">
Rules &amp; Guidelines
</a>
</div>
</div>
</div>
<div class="item">
<span class="item-header">
FAQ
</span>
<div class="sub-item">
<div class="outfit-font">
<a href="./faq.html" class="sub-item-link">
FAQ
</a>
</div>
<div class="outfit-font">
<a href="./faq.html#submit" class="sub-item-link">
How to enter the IOCCC
</a>
</div>
<div class="outfit-font">
<a href="./faq.html#fix_an_entry" class="sub-item-link">
Fixing IOCCC entries
</a>
</div>
<div class="outfit-font">
<a href="./faq.html#fix_web_site" class="sub-item-link">
Fixing the web site
</a>
</div>
<div class="outfit-font">
<a href="./faq.html#fix_author" class="sub-item-link">
Fixing author info
</a>
</div>
</div>
</div>
<div class="item">
<span class="item-header">
About
</span>
<div class="sub-item">
<div class="outfit-font">
<a href="./index.html" class="sub-item-link">
IOCCC Home
</a>
</div>
<div class="outfit-font">
<a href="./judges.html" class="sub-item-link">
The IOCCC Judges
</a>
</div>
<div class="outfit-font">
<a href="./contact.html" class="sub-item-link">
Contacting the IOCCC
</a>
</div>
<div class="outfit-font">
<a href="./thanks-for-help.html" class="sub-item-link">
Thanks for the help
</a>
</div>
<div class="outfit-font">
<a href="./markdown.html" class="sub-item-link">
IOCCC markdown
</a>
</div>
</div>
</div>
</div>
</div>
</nav>
<div class="header-mobile-menu">
<noscript>
<a href="./nojs-menu.html" class="topbar-js-label">
Please Enable JavaScript
</a>
</noscript>
<button id="header-open-menu-button" class="topbar-mobile-menu">
<img
src="./png/hamburger-icon-open.png"
alt="hamburger style menu icon - open state"
width=48
height=48>
</button>
<button id="header-close-menu-button" class="hide-content">
<img
src="./png/hamburger-icon-closed.png"
alt="hamburger style menu icon - closed state"
width=48
height=48>
</button>
<div id="mobile-menu-panel" class="hide-content">
<div class="mobile-menu-container">
<div class="mobile-menu-wrapper">
<div class="mobile-menu-item">
Entries
</div>
<div class="mobile-submenu-wrapper">
<a class="mobile-submenu-item" href="./years.html">
Winning Entries
</a>
<a class="mobile-submenu-item" href="./authors.html">
People who have won
</a>
<a class="mobile-submenu-item" href="./location.html">
Location of authors
</a>
<a class="mobile-submenu-item" href="./bugs.html">
Bugs &amp; (Mis)features
</a>
</div>
</div>
<div class="mobile-menu-wrapper">
<div class="mobile-menu-item">
Status
</div>
<div class="mobile-submenu-wrapper">
<a class="mobile-submenu-item" href="./status.html">
Contest status
</a>
<a class="mobile-submenu-item" href="./next/index.html">
Rules &amp; Guidelines
</a>
<a class="mobile-submenu-item" href="./news.html">
IOCCC News
</a>
</div>
</div>
<div class="mobile-menu-wrapper">
<div class="mobile-menu-item">
FAQ
</div>
<div class="mobile-submenu-wrapper">
<a class="mobile-submenu-item" href="./faq.html">
Frequently Asked Questions
</a>
<a class="mobile-submenu-item" href="./faq.html#submit">
How to enter the IOCCC
</a>
<a class="mobile-submenu-item" href="./faq.html#fix_an_entry">
Fixing IOCCC entries
</a>
<a class="mobile-submenu-item" href="./faq.html#fix_web_site">
Fixing the web site
</a>
<a class="mobile-submenu-item" href="./faq.html#fix_author">
Fixing author info
</a>
</div>
</div>
<div class="mobile-menu-wrapper">
<div class="mobile-menu-item">
About
</div>
<div class="mobile-submenu-wrapper">
<a class="mobile-submenu-item" href="./index.html">
IOCCC Home
</a>
<a class="mobile-submenu-item" href="./judges.html">
The IOCCC Judges
</a>
<a class="mobile-submenu-item" href="./contact.html">
Contacting the IOCCC
</a>
<a class="mobile-submenu-item" href="./thanks-for-help.html">
Thanks for the help
</a>
</div>
</div>
</div>
</div>
</div>
</div>
<script>
var headerOpenMenuButton = document.getElementById("header-open-menu-button");
var headerCloseMenuButton = document.getElementById("header-close-menu-button");
var mobileMenuPanel = document.getElementById("mobile-menu-panel");
headerOpenMenuButton.addEventListener("click", () => {
headerOpenMenuButton.classList.remove("topbar-mobile-menu");
headerOpenMenuButton.classList.add("hide-content");
headerCloseMenuButton.classList.remove("hide-content");
headerCloseMenuButton.classList.add("topbar-mobile-menu");
mobileMenuPanel.classList.remove("hide-content");
mobileMenuPanel.classList.add("topbar-mobile-panel");
});
headerCloseMenuButton.addEventListener("click", () => {
headerCloseMenuButton.classList.remove("topbar-mobile-menu");
headerCloseMenuButton.classList.add("hide-content");
mobileMenuPanel.classList.add("hide-content");
mobileMenuPanel.classList.remove("topbar-mobile-panel");
headerOpenMenuButton.classList.add("topbar-mobile-menu");
headerOpenMenuButton.classList.remove("hide-content");
});
</script>
<!-- END: this line ends content from: inc/topbar.default.html -->
<!-- START: this line starts content from: inc/header.default.html -->
<div class="header">
<a href="./2011/zucker/index.html">
<img src="./png/ioccc.png"
alt="IOCCC image by Matt Zucker"
width=300
height=110>
</a>
<h1>The International Obfuscated C Code Contest</h1>
<h2>IOCCC News</h2>
</div>
<!-- END: this line ends content from: inc/header.default.html -->
<!-- START: this line starts content from: inc/navbar.empty.html -->
<div class="navbar">
<a class="Right" href="https://validator.w3.org/nu/?doc=https%3A%2F%2Fioccc-src.github.io%2Ftemp-test-ioccc%2Fnews.html">&#x2713;</a>
</div>
<!-- END: this line ends content from: inc/navbar.empty.html -->
<!-- START: this line starts content from: inc/before-content.default.html -->
<div class="content" id="content">
<!-- END: this line ends content from: inc/before-content.default.html -->
<!-- START: this line starts content for HTML phase 21 by: bin/pandoc-wrapper.sh via bin/md2html.sh -->
<!-- BEFORE: 1st line of markdown file: news.md -->
<h1 id="for-more-news-try-mastodon">For more news, try mastodon</h1>
<h3 id="please-follow-the-ioccc-on-mastodon">Please follow** the <a href="https://fosstodon.org/@ioccc">IOCCC on Mastodon</a></h3>
<p>We use Mastodon to make minor announcements, in addition announcing
major events such as the opening of a new IOCCC, or who won.</p>
<p>See “<a href="faq.html#try_mastodon">FAQ 6.12: What is Mastodon and why does IOCCC use it?</a>” for more
information on Mastodon.</p>
<h2 id="section">2024-04-30</h2>
<p>The web site now is viewing by mobile devices such as cell phones
and tablets. Devices with a screen resolution 1024 pixels and
narrower are given a <em>hamburger-style</em> menu icon in place of
drop-down menus at the very top of the page (called the <em>topbar</em>).</p>
<p>Any mobile device with a screen wider than 1024 pixels will need
to <em>press and hold</em> to force the <em>topbar</em> pull-down menu to activate.</p>
<p>We had to introduce the use of JavaScript to activate a <em>hamburger-style</em>
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.</p>
<p>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.</p>
<p>The generated HTML files (via <code>bin</code> tools) and other HTML files are
now conform with HTML 5 standards. The <strong>Nu Html Checker</strong> reports
<strong>no error, warnings, nor info</strong> messages.</p>
<p>The *Nu Html Checker<strong> change from <em>2024-04-20</em> is that the HTML
files that are static (not generated <code>bin</code> tools) report </strong>no error,
warnings, nor info** messages, changes involving fixing invalid
links to local files have been corrected, and changes involving the
<em>topbar</em> are now HTML 5 conforming.</p>
<h2 id="section-1">2024-04-20</h2>
<p>Nearly all of the <a href="https://ioccc-src.github.io/temp-test-ioccc/">temp-test-ioccc web site</a>
web site has undergone editorial review. Nearly all <a href="years.html">IOCCC winning entries</a>
compile on modern systems and many have <code>try.sh</code> scripts to help you run them.
For those that cannot compile and/or do not work, we have made a
<a href="bugs.html">Bugs and (Mis)features</a> page.</p>
<p>We have made nearly 4823 changes to date!</p>
<p>All generated HTML pages are now conform to HTML 5 with the
<a href="https://validator.w3.org/nu/">Nu Html Checker</a> reporting <strong>no error, warnings, nor info</strong> messages.</p>
<p>The <a href="judges.html">IOCCC judges</a> have contracted with a web designer
to improve the overall look of the web site, while <strong>maintaining
the utilitarian look and feel</strong>, and without introducing any
glaring “<em>dancing bears</em>” and other frivolous web features.</p>
<p>We are working towards what we call the
<strong><a href="https://github.com/ioccc-src/temp-test-ioccc/issues/2239">Great Fork Merge</a></strong>
where the contents of the <a href="https://ioccc-src.github.io/temp-test-ioccc/">temp-test-ioccc web site</a>
will be merged into the <a href="https://www.ioccc.org/index.html">Official IOCCC web site</a>.</p>
<p>Stay tuned!</p>
<h2 id="section-2">2024-02-29</h2>
<p>We continue to make good progress on web site. In the <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc GitHub repo</a> we have made nearly 4600 changes to date!</p>
<p>All web pages, including this one, are now constructed from markdown files and/or JSON data files using tools found in the <a href="bin/index.html">bin</a> directory.</p>
<h2 id="section-3">2023-05-22</h2>
<p>We have been busy preparing for an important / significant update to this web site. In the <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc GitHub repo</a> we have made nearly 2645 changes to date.</p>
<p>While you are free to look at the <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc GitHub repo</a>,
please <strong>do not link to it</strong> as this repo and related web site will disappear once the main
<a href="https://github.com/ioccc-src/winner">IOCCC winner repo</a> has been updated.</p>
<p>Also be aware that the <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc GitHub repo</a>
is undergoing rapid changes. There are broken links and other things in mid-change.</p>
<p>Once we are ready to update the <a href="https://github.com/ioccc-src/winner">IOCCC winner repo</a>
and its associated web site,
we will post a news article warning of the pending change that is about to arrive.</p>
<p>These 2645+ changes in the <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc GitHub repo</a>
include diverse things such as:</p>
<ul>
<li>Moving IOCCC entries into their own separate directories</li>
<li>Fixing lots and lots of typos</li>
<li>Fixing Makefiles and code to allow for nearly all winning IOCCC entries to be compiled on modern systems</li>
<li>Reworking the Makefiles to use a consistent set of rules</li>
<li>Reworking the Makefiles to compile under gcc and clang</li>
<li>Replacing the various hint files with a index.html markdown that is more consistent across IOCCC years</li>
<li>Setting up a system whereby authors of IOCCC entries may update their own contact information via a GitHub pull request</li>
<li>Setting up to generate the top level <a href="years.html">years.html</a> file via a tool</li>
<li>Setting up to generate the top level <a href="authors.html">authors.html</a> file via a tool</li>
<li>etc.</li>
</ul>
<p>We have lots more to do. Our work is not finished. We just wanted to let you know that we are making good progress.</p>
<p>In regards to the next IOCCC. We <strong>do plan to hold a 28th IOCCC</strong>. However before we do that, we plan
to hold what will be called <strong>IOCCCMOCK</strong>, a beta-test IOCCC where we plan to test the new
<a href="https://github.com/ioccc-src/mkiocccentry">mkiocccentry tool</a>, a tool that will package
submissions to the IOCCC.</p>
<p>We are working on an improved <strong>IOCCC submit server</strong>
that will allow those who submit entires to be informed about the status of their submission.
This <strong>IOCCC submit server</strong> will be beta tested in the <strong>IOCCCMOCK</strong>.</p>
<p>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
<strong>announcement of the winning entries of an IOCCC will be done by posting the winning code via a GitHub commit.</strong>
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.</p>
<p>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 <strong>go live</strong>. For this reason, we plan to beta-test the process by holding an <strong>IOCCCMOCK</strong>.
The <strong>IOCCCMOCK</strong> will be like a regular IOCCC except that the judges <strong>will not</strong> judge the code.
Instead, people will be invited to submit a simple <em>“Hello, world!”</em> style program.
Awards will be given to those who:</p>
<ul>
<li>submit the best pull requests that fix a bug</li>
<li>submit the best pull requests that fix a typo</li>
<li>make the best suggestions for improvements</li>
<li>have the most fun / make us laugh</li>
<li>etc.</li>
</ul>
<p>The <strong>IOCCCMOCK</strong> will allow is to restart the beta-test contest should a major problem be discovered
that needs urgent fixing.
The <strong>IOCCCMOCK</strong> will us to beta-test the new IOCCC process without putting the hard work of those
who submit real IOCCC entries at risk.</p>
<p>Stay tuned!</p>
<h2 id="section-4">2023-01-30</h2>
<p>We added to the
<a href="status.json">status.json</a> page,
a <em>“status_date”</em> JSON member whose value is the date
of the most recent <a href="status.json">status.json</a> modification,
in <em>date(1)</em> format.</p>
<p>We also added to the
<a href="status.json">status.json</a> page,
a <em>“latest_news”</em> JSON member whose value is the date
of the most recent news item.</p>
<pre><code> &quot;status_date&quot; : &quot;Mon Jan 30 02:28:44 PST 2023&quot;,
&quot;latest_news&quot; : &quot;Mon Jan 30 02:28:44 PST 2023&quot;</code></pre>
<h2 id="section-5">2022-12-18</h2>
<p>As per the suggestion of <a href="https://fosstodon.org/@Virtaava@home.social">Toni Mikkola</a>
(_<span class="citation" data-cites="Virtaava">@Virtaava</span><span class="citation" data-cites="home.social_">@home.social_</span>) we now maintain a
<a href="status.json">status.json</a> page on this web site.</p>
<p>In addition to the IOCCC-style <em>easter egg</em>, you may count on
the JSON status page having a JSON member with name of <strong>“contest”</strong>
that will have a value of either <strong>“closed”</strong> or <strong>“open”</strong>.
When a future <strong>IOCCC</strong> is announced or the IOCCC is currently open,
the JSON member with name of <strong>“contest”</strong> will change from
<strong>“closed”</strong> to <strong>“open”</strong>.</p>
<p>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 <em>TBD</em>.</p>
<p>When an open IOCCC closes, we won’t instantaneously update the
<a href="status.json">status.json</a> page.
Instead you will have to rely on the additional JSON information
and/or read the <a href="#news">IOCCC news</a>,
and/or follow us on Mastodon via <strong><span class="citation" data-cites="ioccc">@ioccc</span><span class="citation" data-cites="fosstodon.org">@fosstodon.org</span></strong>.</p>
<h2 id="section-6">2022-11-29</h2>
<p>We are plan to abandon our
<a href="https://twitter.com/ioccc">IOCCC Twitter feed</a>
in favor of our new <a href="https://fosstodon.org/@ioccc">IOCCC Mastodon</a> feed.</p>
<p>Our Mastodon username is: <strong><span class="citation" data-cites="ioccc">@ioccc</span><span class="citation" data-cites="fosstodon.org">@fosstodon.org</span></strong>.</p>
<pre><code> Please note: As of the date of this posting, our account was just setup,
so there isn&#39;t much to read there, yet.</code></pre>
<p>In the future we plan to use Mastodon as our official announcement platform.
This will include announcing:</p>
<ul>
<li>IOCCC news updates</li>
<li>Start of a new IOCCC</li>
<li>Updates on the IOCCC judging process</li>
<li>Who won the IOCCC</li>
<li>et<strong>C</strong>. :-)</li>
</ul>
<p>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 <strong>NOT</strong> required to enter the IOCCC, but nevertheless is encouraged.
Proving a Mastodon username will be entirely <strong>optional</strong>.</p>
<p>Non-mastodon users can follow the IOCCC postings via:
<a href="https://fosstodon.org/@ioccc">fosstodon.org/<span class="citation" data-cites="ioccc">@ioccc</span></a>.</p>
<p>If you do not yet have a Mastodon account, you may obtain a <strong>free mastodon account via</strong>:
<a href="https://joinmastodon.org">joinmastodon.org</a>.</p>
<p>If you do have / obtain a Mastodon account, <strong>please do us a favor and follow the IOCCC at</strong>:</p>
<pre><code> **@ioccc@fosstodon.org**</code></pre>
<p>The IOCCC wishes to thank the good folk running the
<a href="https://hub.fosstodon.org/about/">fosstodon.org</a>
Mastodon hub.
Their technology focused
<a href="https://hub.fosstodon.org">Fosstodon Hub</a>
is made possible by volunteers,
and those who voluntarily
<a href="https://hub.fosstodon.org/support/">support</a> the cost of their server.</p>
<p>Stay tuned in Mastodon as we update you on our progress towards the next IOCCC!</p>
<h2 id="section-7">2022-11-19</h2>
<p>Source code has been released for version <strong>0.8.1 2022-11-19</strong> of the
<a href="https://github.com/ioccc-src/mkiocccentry">mkiocccentry repo</a>,
a GitHub repo that includes the official iocccsize tool,
and a tool will form a compressed tarball of their entry.</p>
<p>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.</p>
<p>Once we reach version 1.0, we plan to invite the public to test and comment.</p>
<p>We plan to hold in 2023, what we will call <strong>IOCCCMOCK</strong>, 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.</p>
<p>We are working on complete rebuild of this web site as well.</p>
<h2 id="section-8">2022-01-15</h2>
<p>Source code has been released for version <strong>0.24 2022-01-15</strong> of the
<a href="https://github.com/ioccc-src/mkiocccentry">mkiocccentry tool</a>,
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).</p>
<h2 id="section-9">2021-12-27</h2>
<p><a href="judges.html">The Judges</a>
are continuing to work on re-tooling how we run the IOCCC.
We are writing tools under various repositories our
<a href="https://github.com/ioccc-src">IOCCC GitHub organization site</a>.</p>
<p><strong>We plan to hold IOCCC28 in 2023.</strong>
Sorry for the delay, but we think you will appreciate the re-tooling
when it is completed.
Stay tuned!</p>
<h2 id="section-10">2021-10-21</h2>
<p><a href="judges.html">The Judges</a>
are re-tooling how we run the IOCCC.
Our goal is to build a smoother, more rapid process centered around
<a href="https://github.com/ioccc-src/winner">GitHub</a>.</p>
<p>For example, when we announce the winning entries of the IOCCC,
we will do so by committing their code to the
<a href="years.html">Winning entries</a>
of the IOCCC repo, so that people will be able immediately
view the winning source.</p>
<p>We plan to refactor and modernize the IOCCC web site.
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,
<strong>we plan to hold IOCCC28 in 2023 instead of 2021</strong>.
Sorry for the delay, but we think you will appreciate the re-tooling
when it is completed.</p>
<p><strong>Stay tuned for how you may be able to help in the IOCCC redesign for IOCCC28!</strong></p>
<hr style="width:10%;text-align:left;margin-left:0">
<p>Jump to: <a href="#">top</a></p>
<!--
Copyright © 1984-2024 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/
-->
<!-- AFTER: last line of markdown file: news.md -->
<!-- END: this line ends content for HTML phase 21 by: bin/pandoc-wrapper.sh via bin/md2html.sh -->
<!-- START: this line starts content from: inc/after-content.default.html -->
</div>
<!-- END: this line ends content from: inc/after-content.default.html -->
<!-- START: this line starts content from: inc/footer.default.html -->
<!--
Copyright © 1984-2024 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/
-->
<div class="footer">
<div id="copyright"><h3>Copyright &copy; 1984-2024 by Landon Curt Noll:
<a href="https://creativecommons.org/faq/#what-does-some-rights-reserved-mean"
target="_blank"
rel="license noopener noreferrer">Some Rights Reserved</a></h3>
<p>
This work is <b>licensed by Landon Curt Noll</b> under
<b><a href="https://creativecommons.org/licenses/by-sa/4.0/?ref=chooser-v1"
target="_blank"
rel="license noopener noreferrer"
style="display:inline-block;">CC BY-SA 4.0</a></b>.
<img style="height:22px!important;margin-left:3px;vertical-align:text-bottom;"
src="./png/cc.png"
alt="cc inside circle symbol">
<img style="height:22px!important;margin-left:3px;vertical-align:text-bottom;"
src="./png/by.png"
alt="person inside circle symbol">
<img style="height:22px!important;margin-left:3px;vertical-align:text-bottom;"
src="./png/sa.png"
alt="arrow looping back on itself inside circle symbol"><br>
You should <b>carefully review</b> the
<b><a href="https://creativecommons.org/licenses/by-sa/4.0/legalcode.en"
target="_blank"
rel="license noopener noreferrer">CC BY-SA 4.0 LEGAL CODE</a></b>
before using the licensed material.<br>
You may wish to review the
<b><a href="./license.html"
target="_blank"
rel="license noopener noreferrer">highlights of some of the key features and terms</a></b>
of <b>CC BY-SA 4.0</b>.<br>
</p>
</div>
<div id="coda"><h3>Coda</h3>
<p>
<a href="https://validator.w3.org/nu/?doc=https%3A%2F%2Fioccc-src.github.io%2Ftemp-test-ioccc%2Fnews.html" rel="nofollow">Nu HTML check this web page</a><br>
<a href="#top">Jump to top</a> <a href="#content">Jump to Content</a> <a href="#inventory">Jump to Inventory</a><br>
</p>
</div>
</div>
<!-- END: this line ends content from: inc/footer.default.html -->
<!-- START: this line starts content from: inc/bottom.default.html -->
</body>
</html>
<!-- END: this line ends content from: inc/bottom.default.html -->