IOCCC Judges

2/2 However we plan to post more detailed updates, especially when an contest is underway, directly to #mastodon: @ioccc@fosstodon.org Non-mastodon users can bookmark and follow: @ioccc" target="_blank" rel="nofollow noopener">fosstodon.org/@ioccc

1/2 The #IOCCC was asked how someone who isn’t on #mastodon can follow our news updates. High level news 📰 still resides at: #news" target="_blank" rel="nofollow noopener">ioccc.org/index.html#news

The #IOCCC joined fosstodon.org/auth/sign_up With the #Mastodon username: @ioccc@fosstodon.org The fosstodon.org Mastodon server is well run by a group of dedicated volunteers and has a tech focus who is well suited for the #IOCCC.

We received multiple reports that those tried to join the original Mastodon server were unable to do. That server is somewhat slow and oversubscribed. We recommend that you instead join from one of the other well run #Mastodon servers: joinmastodon.org/servers

The International Obfuscated C Code Contest (#IOCCC) will abandon active use of this twitter account. We'll post announcements (news, start dates, winners, etc.) via our new #mastodon account: @ioccc@fosstodon.org Please follow us on Mastodon. See: #news" target="_blank" rel="nofollow noopener">ioccc.org/index.html#news

We continue to work on the improved IOCCC contest tool chain and submit server. Making great progress.

@tblodt All of which costs 💵, unfortunately

Unfortunately netlify charges for their service and has bandwidth caps. IOCCC, when winners are announced has enormous download rates that would simply be too costly for us.

@famontesi @ProgrammingCom @CProgramming1 @CColemanFoxNews @fun_c_ @WalterBright @molecularmusing @ioccc @foonathan @c64_gio @mariusbancila @CProgram_app @samuelbars @nim_lang @TrevorCFritz @Riller_10 @conal @RasmusKallqvist #softwaredeveloper #cryptocurrency #Coding

By posting IOCCC winning code first w/o delay, by using the GitHub pull request process to fix/improve winners (code & writeup), and providing winners a way to update (or remove) their contact information, the overall @IOCCC will improve. There WILL be a #IOCCC28 .. we promise!

When #IOCCC28 happens, we will have a refracted ioccc.org, IOCCC entry packaging tool, and improved submission process. Winners will be announced by pushing winning source to ioccc.org GitHub repo w/o delay. Winners can fix/improve via Pull requests.

We won't actually judge code submitted to #MOCKIOCCC. Winners of the MOCKIOCCC will be based on those who provide us with the best feedback, 1st to report a given bug, etc. All this is to sure we are ready for when the real #IOCCC28 happens!

The #MOCKIOCCC will be your way to provide @ioccc with valuable feedback on the IOCCC contest process. We don't to subject the real #IOCCC28 on an untested process: hence the need for a MOCKIOCCC to be held first.

On the topic of the next IOCCC: We are hard at work building a new entry packaging tool (written in C of course 🤓) that will significantly benefit the IOCCC. When this packaging tool is code and test complete, we plan to invite you to comment on and test it.

If the file was foo.html, then the browser would be given Meta Refresh HTML. However none of the winners in 1988-2004 contain HTML pages. So when we move the C source, hint files, extra files those 1988-2004 URLs will break because they are no HTML files.

GitHub's hosting of ioccc.org offers limited redirect methods. We do NOT have access to GitHub's server config. Use of server side code and .htaccess is not allowed, so we are limited to using Meta Refresh. Unfortunately Meta Refresh won't work for 1988-2004.

We part of our refactoring of ioccc.org, as hosted by GitHub via our github.com/ioccc-src/winn… repo, we need to move winners 1988-2004 into their own sub-directories. Sadly Meta Refresh won't work for most non-HTML web pages, so existing URLs will break. Sorry!

@fanf GitHub pages only support static HTML: things like .htaccess are unavailable. We could use META tags to redirect a few critical pages per winner (prog.c & hint files). Not ideal: slow & litters file tree, so we wouldn't to do want this for the long term. Would that help @fanf?

@ioccc sounds like a good improvement in consistency, but can you please make the web server return redirects from the old URLs to the new ones?

We plan to change the @IOCCC layout for winners of 1988-2004 to match the per-directory layout of 1984-1987 & 2005-2020. This a needed step as we improve our web site & for how we announce future winners. We apologize breaking any links to those entries. ioccc.org