-
Notifications
You must be signed in to change notification settings - Fork 48
/
Copy pathnews.html
933 lines (825 loc) · 46 KB
/
news.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
<!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:[email protected]&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">
Winning authors
</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 and (mis)features
</a>
</div>
<div class="outfit-font">
<a href="./faq.html#fix_an_entry" class="sub-item-link">
Fixing entries
</a>
</div>
<div class="outfit-font">
<a href="./faq.html#fix_author" class="sub-item-link">
Updating author info
</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">
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 and guidelines
</a>
</div>
<div class="outfit-font">
<a href="./markdown.html" class="sub-item-link">
Markdown guidelines
</a>
</div>
<div class="outfit-font">
<a href="./SECURITY.html" class="sub-item-link">
Security policy
</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">
Frequently Asked Questions
</a>
</div>
<div class="outfit-font">
<a href="./quick-start.html#enter" class="sub-item-link">
Enter the IOCCC
</a>
</div>
<div class="outfit-font">
<a href="./faq.html#compiling" class="sub-item-link">
Compiling entries
</a>
</div>
<div class="outfit-font">
<a href="./faq.html#running_entries" class="sub-item-link">
Running entries
</a>
</div>
<div class="outfit-font">
<a href="./faq.html#help" class="sub-item-link">
How to help
</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">
Home page
</a>
</div>
<div class="outfit-font">
<a href="./about.html" class="sub-item-link">
About the IOCCC
</a>
</div>
<div class="outfit-font">
<a href="./judges.html" class="sub-item-link">
The Judges
</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="./contact.html" class="sub-item-link">
Contact us
</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">
Winning authors
</a>
<a class="mobile-submenu-item" href="./location.html">
Location of authors
</a>
<a class="mobile-submenu-item" href="./bugs.html">
Bugs and (mis)features
</a>
<a class="mobile-submenu-item" href="./faq.html#fix_an_entry">
Fixing entries
</a>
<a class="mobile-submenu-item" href="./faq.html#fix_author">
Updating author info
</a>
<a class="mobile-submenu-item" href="./thanks-for-help.html">
Thanks for the help
</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="./news.html">
News
</a>
<a class="mobile-submenu-item" href="./status.html">
Contest status
</a>
<a class="mobile-submenu-item" href="./next/index.html">
Rules and guidelines
</a>
<a class="mobile-submenu-item" href="./markdown.html">
Markdown guidelines
</a>
<a class="mobile-submenu-item" href="./SECURITY.html">
Security policy
</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="./quick-start.html#enter">
Enter the IOCCC
</a>
<a class="mobile-submenu-item" href="./faq.html#compiling">
Compiling entries
</a>
<a class="mobile-submenu-item" href="./faq.html#running_entries">
Running entries
</a>
<a class="mobile-submenu-item" href="./faq.html#help">
How to help
</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">
Home page
</a>
<a class="mobile-submenu-item" href="./about.html">
About the IOCCC
</a>
<a class="mobile-submenu-item" href="./judges.html">
The Judges
</a>
<a class="mobile-submenu-item" href="./contact.html">
Contact us
</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%2Fwww.ioccc.org%2Fnews.html">✓</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 to announcing
major events such as the opening of a new IOCCC, or who won.</p>
<p>See the
FAQ on “<a href="faq.html#try_mastodon">Mastodon</a>”
for more information on Mastodon.</p>
<h3 id="ioccc-discord-community">IOCCC Discord Community</h3>
<p>We invite you to join the <strong>IOCCC Discord Community</strong> via this link: <a href="https://discord.gg/Wa42Qujwnw">https://discord.gg/Wa42Qujwnw</a></p>
<h1 id="news">News</h1>
<h2 id="section">2025-04-19</h2>
<p>The <strong>IOCCC28</strong> <strong>OPEN</strong> period has reached the half-way point.
This is a <em>gentle suggestion</em> to not wait until the last minute to write, test
and upload your submission.</p>
<p>The <strong>IOCCC28</strong> is <a href="https://www.ioccc.org/next/register.html">open for registration</a>.
Those who have registered have until <strong>2025-06-05 04:03:02.010099 UTC</strong> to
<a href="https://www.ioccc.org/next/submit.html">upload their submissions</a>.</p>
<p>See “<a href="https://www.ioccc.org/quick-start.html#enter">how enter the IOCCC</a>” for more information.</p>
<h2 id="section-1">2025-03-15</h2>
<p>We released <a href="https://github.com/ioccc-src/mkiocccentry">mkiocccentry toolkit</a> <strong>version 2.4.4 2025-03-15</strong>.</p>
<p>While you are <strong>NOT</strong> required to use this release in order to submit to <strong>IOCCC28</strong>,
we do <strong>RECOMMEND</strong> that you <strong>install and use</strong> it, because among other things, it provides:</p>
<ul>
<li>Set locale to <strong>C</strong>, the <strong>official locale</strong> of the <strong>IOCCC</strong>.</li>
</ul>
<p>See the <a href="https://github.com/ioccc-src/mkiocccentry/releases/tag/2.4.4">version 2.4.4 release notes</a> for more details.</p>
<h2 id="section-2">2025-03-12</h2>
<p>We released <a href="https://github.com/ioccc-src/mkiocccentry">mkiocccentry toolkit</a> <strong>version 2.4.3 2025-03-11</strong>.</p>
<p>While you are <strong>NOT</strong> required to use this release in order to submit to <strong>IOCCC28</strong>,
we do <strong>RECOMMEND</strong> that you <strong>install and use</strong> it, because among other things, it provides:</p>
<ul>
<li><code>mkiocccentry(1)</code> and <code>txzchk(1)</code> now search for other toolkit tools using <code>$PATH</code></li>
<li><code>mkiocccentry(1)</code> and <code>chkentry(1)</code> are now less strict with most <code>iocccsize(1)</code> warnings</li>
<li><code>mkiocccentry -x</code> will force the overwriting of the submission directory it forms under <code>workdir</code></li>
<li><code>mkiocccentry -U uuid</code> and <code>mkiocccentry -u uuid_file</code> let you set your username</li>
</ul>
<p>See the <a href="https://github.com/ioccc-src/mkiocccentry/releases/tag/2.4.3">version 2.4.3 release notes</a> for more details.</p>
<p><strong>Clarification</strong>: <strong>NUL bytes</strong> are <strong>ALLOWED</strong> in your submission <code>prog.c</code> and related C code.</p>
<p>Please mention in your <code>remarks.md</code> file if your C source contains <strong>NUL bytes</strong>.</p>
<h2 id="section-3">2025-03-05</h2>
<p>The <a href="faq.html#ioccc_start">40th anniversary of the IOCCC</a>, <strong>IOCCC28</strong>, will be <strong>open</strong> for
submissions from <strong>2025-03-05 23:19:17.131107 UTC</strong> to <strong>2025-06-05 04:03:02.010099 UTC</strong>.</p>
<p>Version <strong>28.30 2025-03-03</strong> of the <a href="next/rules.html">IOCCC28 rules</a>,
version <strong>28.44 2025-03-04</strong> of the <a href="next/guidelines.html">IOCCC28 guidelines</a>, and
version <strong>2.4.2 2025-03-02</strong> of the <a href="https://github.com/ioccc-src/mkiocccentry">mkiocccentry toolkit</a>,
are now <a href="next/index.html">official</a>.</p>
<p>See the <a href="quick-start.html#enter">IOCCC quick start guide</a> for how to enter, and
the <a href="faq.html#mkiocccentry">mkiocccentry repo FAQ</a> for
information on the <a href="https://github.com/ioccc-src/mkiocccentry">mkiocccentry toolkit</a> and
the <a href="faq.html">IOCCC FAQ</a> for general information on the <a href="index.html">IOCCC</a>.</p>
<p>In order to <a href="next/submit.html">submit to the IOCCC28</a> you must be
<a href="next/register.html">registered for the IOCCC28</a>. <strong>DO NOT</strong> wait until the last minute
to register as the process can take a bit of time to complete!</p>
<p>Those who registered while the contest was <strong>pending</strong>
should have received their <a href="https://submit.ioccc.org">IOCCC submit server</a>
and initial password by email. If you cannot find that email, contact the
<a href="contact.html#if-you-really-need-to-send-email-the-ioccc-judges">IOCCC Judges by email</a>
for help. We have given early registrants extra time (until <strong>2025 Mar 12 UTC</strong>), to login
and change their initial password.</p>
<h2 id="section-4">2025-02-28</h2>
<p>We have reached our <strong>code freeze</strong> milestone for the <a href="https://github.com/ioccc-src/mkiocccentry">mkiocccentry repo</a> and released a new version of the <a href="faq.html#mkiocccentry">mkiocccentry toolkit</a>!</p>
<p>Final testing is going well. We remain on track to open the <strong>IOCCC28</strong> on <strong>2025-03-05 23:19:17.131107 UTC</strong>.</p>
<p>In a few days, those <a href="https://www.ioccc.org/next/register.html">registered for IOCCC28</a> will receive email with their username and initial password to <a href="https://submit.ioccc.org">submit their code</a>.</p>
<p>We encourage those who wish to enter the <strong>IOCCC28</strong> to <a href="https://www.ioccc.org/next/register.html">registered for IOCCC28</a> today.</p>
<p>Consider joining the IOCCC discord community via this link: <a href="https://discord.gg/Wa42Qujwnw">https://discord.gg/Wa42Qujwnw</a></p>
<h2 id="section-5">2025-02-12</h2>
<p>We have discovered an issue that needs to be resolved, followed by more testing
after the code freeze. We also want to improve the <a href="next/guidelines.html">IOCCC28 guidelines</a>,
and to simplify the write-up of the <a href="next/rules.html">IOCCC28 rules</a>.</p>
<p>The <a href="faq.html#ioccc_start">40th anniversary of the IOCCC</a>, which started
on <strong>2024-12-29 23:58:13.213455 UTC</strong>, is now scheduled to be <strong>open</strong>
from <strong>2025-03-05 23:19:17.131107 UTC</strong> to <strong>2025-06-05 04:03:02.010099 UTC</strong>.
We apologize for this delay.</p>
<h2 id="section-6">2025-01-28</h2>
<p><strong>IMPORTANT DISCORD UPDATE</strong>: Due to a Discord bug/mis-feature, those
who joined the <a href="https://discord.gg/Wa42Qujwnw">IOCCC Discord server</a>
recently lost their access soon afterwards and have to re-join.
We apologise for the inconvenience of having to rejoin.</p>
<p>The IOCCC now has a <a href="https://discord.gg/Wa42Qujwnw">Discord server</a>!
Fans of the IOCCC, hopeful <strong>IOCCC28</strong> contestants, and past winners of the IOCCC
are all encouraged to stop by and say hello.</p>
<p>To join, click this link:
<a href="https://discord.gg/Wa42Qujwnw">https://discord.gg/Wa42Qujwnw</a>.</p>
<h2 id="section-7">2025-01-25</h2>
<p>The IOCCC now has a <a href="https://discord.gg/Wa42Qujwnw">Discord server</a>!
Click the link to join the <a href="https://discord.gg/Wa42Qujwnw">IOCCC Discord server</a>.
Fans of the IOCCC, hopeful <strong>IOCCC28</strong> contestants, and past winners of the IOCCC
are all encouraged to stop by and say hello.</p>
<p>Based on user input and suggestions, we have been working on some new
functionality for the <a href="faq.html#mkiocccentry">mkiocccentry toolkit</a>.
In order to complete and fully test this new functionality, we need
additional time. Therefore the <strong>IOCCC28 open</strong> date has been <strong>moved
forward by 19 days</strong>. Moreover, and also by request, the contest will
remain <strong>open for an additional month</strong>.</p>
<p>The <a href="faq.html#ioccc_start">40th anniversary of the IOCCC</a>, which started
on <strong>2024-12-29 23:58:13.213455 UTC</strong>, is now scheduled to be <strong>open</strong>
from <strong>2025-02-19 23:19:17.130705 UTC</strong> to <strong>2025-05-19 23:29:31.374143
UTC</strong>. We will update the <a href="next/rules.html">IOCCC rules</a> and
<a href="next/guidelines.html">IOCCC guidelines</a> accordingly, before the contest opens.</p>
<h2 id="section-8">2024-12-31</h2>
<p>We have just released <a href="https://github.com/ioccc-src/mkiocccentry/releases/tag/v2.3">version 2.3 of the mkiocccentry repo</a>.
This repo 2.3 release includes important improvements (over repo release 2.1) to the <code>mkiocccentry(1)</code> tool
as well as a critical fix for installing on BSD based systems.</p>
<p>Please download <a href="https://github.com/ioccc-src/mkiocccentry/releases/tag/v2.3">version 2.3 of the mkiocccentry repo</a>,
and compile the <a href="faq.html#mkiocccentry">mkiocccentry tool set</a>. You may also wish to install this code.
See also the <a href="https://github.com/ioccc-src/mkiocccentry/blob/master/FAQ.md">mkiocccentry FAQ</a> for more information.</p>
<h2 id="section-9">2024-12-30</h2>
<p>The IOCCC <a href="next/rules.html#rule13">Rule 13</a> no longer discourages the
use of UTF-8 in C source. Since the days of <code>-std=gnu17</code> 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”.</p>
<p>The IOCCC <a href="next/rules.html#rule8">Rule 8</a> 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.</p>
<p>All of the import IOCCC dates within the <a href="next/rules.html">IOCCC rules</a>
have been moved into the “<a href="next/rules.html#dates">Important IOCCC dates</a>”
section.</p>
<h2 id="section-10">2024-12-28</h2>
<h3 id="good-news-everyone--">Good News Everyone! :-)</h3>
<p>After a 4 year effort by a <a href="thanks-for-help.html">number of people</a>,
with over 6168+ commits, the <strong>Great Fork Merge</strong> has been completed
and the <a href="index.html">Official IOCCC website</a> has been updated!</p>
<p>A significant number of improvements have been made to the
<a href="years.html">IOCCC winning entries</a>.
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 <a href="faq.html#compiling">FAQ Section 4</a> for
information on how to compile.
See the <a href="faq.html#changes">FAQ Section 8</a>
for details on changes made to the entries.</p>
<p>We hope you enjoy the new and improved
<a href="index.html">Official IOCCC website</a>.
This website is backed by the
<a href="https://github.com/ioccc-src/winner">IOCCC winner GitHub repo</a>.
See <a href="faq.html#help">FAQ Section 9</a> for
how you can help <a href="faq.html#fix_website">improve / fix the website</a>,
or fix <a href="bugs.html">known bugs in IOCCC winning entries</a>.</p>
<h3 id="ioccc28-is-starting">IOCCC28 is starting!</h3>
<p>The IOCCC28, the <a href="faq.html#ioccc_start">40th anniversary of the IOCCC</a> is now
scheduled to run from <strong>2024-12-29 23:58:13.213455 UTC</strong> to <strong>2025-04-01 23:29:31.374143 UTC</strong>!!!.</p>
<p>The <a href="status.html">contest status</a> has been changed to “<strong>pending</strong>”
and <a href="status.json">status.json</a> has been updated to reflect this new status.</p>
<p>Proposed and tentative <a href="next/rules.html">IOCCC rules</a> and <a href="next/guidelines.html">IOCCC guidelines</a>
have been released.</p>
<p>See <a href="quick-start.html#enter_questions">FAQ Section 0</a> for more information on how to enter.</p>
<h2 id="section-11">2024-06-08</h2>
<p>We continue to make good progress on the
<a href="https://ioccc-src.github.io/temp-test-ioccc/">temp-test-ioccc website</a>
via the <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc</a> repo.</p>
<p>One of the <a href="thanks-for-help.html">largest html
files</a> has
been checked for broken links which leaves two longer files to go. These two
files are the <a href="bugs.html">bugs.html</a>
file and the “<a href="faq.html">IOCCC FAQ</a>”.</p>
<p>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.</p>
<p>As of today, 08 June 2024, the top level html files are being looked at, with at
least three done already (<a href="judges.html">judges.html</a>, <a href="news.html">news.html</a> and
<a href="status.html">status.html</a>). 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
<a href="news.html">news.html</a> and possibly <a href="status.html">status.html</a> will likely have to be
checked again but as for <a href="news.html">news.html</a> the dates up to and including <em>08
June 2024</em> have been checked for invalid links so that only new news updates
will have to be checked.</p>
<p>Once those are done the html files of all the entries will be looked at. As
those are being reviewed it the <a href="bugs.html">bugs.html</a> might very well be
updated and the “<a href="faq.html">IOCCC FAQ</a>” 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.</p>
<p>Once the <em>submit server</em> server is ready another FAQ will be added and that
entry can be looked at alone.</p>
<h2 id="section-12">2024-05-30</h2>
<p>A number of issues from minor fixes have been applied to the
<a href="https://ioccc-src.github.io/temp-test-ioccc/">temp-test-ioccc website</a>
via the <a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc</a> repo.</p>
<p>437 commits have been applied since 2024-04-20, bringing the total
number to 5260 commits to date. The
<a href="https://github.com/ioccc-src/temp-test-ioccc">temp-test-ioccc</a>
repo is now 5159 commits ahead of the <a href="https://github.com/ioccc-src/winner">IOCCC
winner</a> repo.</p>
<p>Multiple <strong>((top priority))</strong> issues have been resolved or completed.
Only one <strong>((top priority))</strong> issue, <a href="https://github.com/ioccc-src/temp-test-ioccc/issues/2006">issue
2006</a>
remains before we begin the final steps to perform the <strong>Great Fork
Merge</strong> when the <a href="https://www.ioccc.org/index.html">Official IOCCC web
site</a> 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.</p>
<p>The <a href="https://github.com/ioccc-src/temp-test-ioccc/issues/2239">issue 2239</a>
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.</p>
<p>The <strong>IOCCC Submit server</strong> is in active development. We plan to
update the FAQ with screenshots from the IOCCC Submit server as
well as the <strong>IOCCC registration process</strong> prior to starting the
<strong>Great Fork Merge</strong>.</p>
<p>We have decided to <strong>NOT</strong> hold an <strong>IOCCC mock</strong> contest, but instead
ask for beta testing of the new <strong>IOCCC registration process</strong> and
<strong>IOCCC Submit server</strong> when they have left alpha testing phase.
This will speed up the start date of IOCCC28.</p>
<p>It is our plan that IOCCC28 will occur in 2024, the 40th anniversary of the
IOCCC.</p>
<h2 id="section-13">2024-04-30</h2>
<p>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 <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-14">2024-04-20</h2>
<p>Nearly all of the <a href="https://ioccc-src.github.io/temp-test-ioccc/">temp-test-ioccc website</a>
website 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 website, 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 website</a>
will be merged into the <a href="https://www.ioccc.org/index.html">Official IOCCC website</a>.</p>
<p>Stay tuned!</p>
<h2 id="section-15">2024-02-29</h2>
<p>We continue to make good progress on website. 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-16">2023-05-22</h2>
<p>We have been busy preparing for an important / significant update to this website. 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 website 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 website,
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 entries 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-17">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> "status_date" : "Mon Jan 30 02:28:44 PST 2023",
"latest_news" : "Mon Jan 30 02:28:44 PST 2023"</code></pre>
<h2 id="section-18">2022-12-18</h2>
(<span class="citation" data-cites="Virtaava">@Virtaava</span><span class="citation" data-cites="home.social&rpar">@home.social&rpar</span>;</a>
we now maintain a <a href="status.json">status.json</a> page on this website.</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-19">2022-11-29</h2>
<p>We are planning 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'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>
<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-20">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 website as well.</p>
<h2 id="section-21">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-22">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-23">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 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,
<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 © 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%2Fwww.ioccc.org%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>
</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 -->