Question: Issues that aren’t really major issues but are still issues

[xexyl]

TODO

• Close this issue when the great fork merge happens.

Original comment

Like the thread in the other repo this is to help us keep the actual issues free from clutter.

I'll start out by showing the problem of not being able to fork this repo instead of winner.git. I'll do that in a follow-up comment.

[xexyl]

UPDATE on forking: it's resolved!

My idea worked: deleting my fork and re-forking it allowed me to create a fork of this repo.

Now I can actually make changes. I do not, I'm afraid, see that happening today, and I will actually be taking a break now rather than replying to the other comments (though the break might be short) but I will get to them later on if not in a bit (though technically that IS later on).

[lcn2]

🤩

[xexyl]

🤩

What is this in reply to please ?

[xexyl]

Testing

Would it be possible to have a test subdomain of the main IOCCC website OR a temp / test subdirectory that has all the changes of THIS repo so we can make sure everything looks and works okay ? It might be a good way to verify that everything can be merged to the real website later on.

[xexyl]

...and I hope you're having a nice sleep my friend!

I'm going to be updating the keys (more recently recommended encryption standards) on the zones (DNSSEC keys I mean) and that will take a bit of time agains this repo but I'm a bit too tired for this and not that so that's okay. I did it with two domains yesterday as some keys were missing but I figure I might as well do it for the others too.

At least I think I'll be doing that now :-) .. either way I'll reply to your comments in the other issues later on.

UPDATE 0

Was troubleshooting a strange problem .. solved that so now I can continue the above. Then if I have time I'll reply to the other comments. Else I'll do that after a break. I then maybe (we'll see!) can get more work done on this repo.

UPDATE 1

... it wasn't solved after all but what is done works well enough for now. I didn't finish the task because of it. I will be taking a quick break and then I will work on the comments here. Hopefully by the time you're awake I will be done with that.

[xexyl]

Questions about moving forwards

What issues have things that can be done before the json tools are made?

If there are any what are they? I guess some (perhaps not all) typos and consistency in some (not all - an example where it's probably possible is the Makefiles) would be something that can be done. Is this so? Anything else that you can think of?

I'll be doing other things now and might not work on this today. I'm feeling pretty worn out right now. That certainly might change but right now I definitely need to do something else.

[lcn2]

Questions about moving forwards

What issues have things that can be done before the json tools are made?

If there are any what are they? I guess some (perhaps not all) typos and consistency in some (not all - an example where it's probably possible is the Makefiles) would be something that can be done. Is this so? Anything else that you can think of?

Issue #1, issue #2, and issue #3 can be done.

[lcn2]

We have not forgotten about comment 1418905409.

[xexyl]

Questions about moving forwards

What issues have things that can be done before the json tools are made?
If there are any what are they? I guess some (perhaps not all) typos and consistency in some (not all - an example where it's probably possible is the Makefiles) would be something that can be done. Is this so? Anything else that you can think of?

Issue #1, issue #2, and issue #3 can be done.

But if the fourth one might impact some of these is this wise? That's kind of what I was getting at. I mean some things in the issues can be done but what can't be or what shouldn't be might be a better way of putting it?

[xexyl]

We have not forgotten about comment 1418905409.

Oh thank you!

[lcn2]

Questions about moving forwards

What issues have things that can be done before the json tools are made?

If there are any what are they? I guess some (perhaps not all) typos and consistency in some (not all - an example where it's probably possible is the Makefiles) would be something that can be done. Is this so? Anything else that you can think of?

Issue #1, issue #2, and issue #3 can be done.

But if the fourth one might impact some of these is this wise? That's kind of what I was getting at. I mean some things in the issues can be done but what can't be or what shouldn't be might be a better way of putting it?

As you didn't seem inclined to want to edit years.html when you went about renaming and removing files .. that is OK, we just have to adjust our approach to that fact .. we will have to accelerate the building of the pre-directory .winner.json files via a tool that we will write .. a tool that needed to be written eventually anyway, BTW.

Also now, before this forked repo can be merged into the main IOCCC winner repo and web site, another tool to build the years.html web page from all .winner.json files .. also one that we need to also write eventually anyway .. will need to automatically build the years.html web page before the the main IOCCC winner repo and web site can be updated.

[xexyl]

Questions about moving forwards

What issues have things that can be done before the json tools are made?

If there are any what are they? I guess some (perhaps not all) typos and consistency in some (not all - an example where it's probably possible is the Makefiles) would be something that can be done. Is this so? Anything else that you can think of?

Issue #1, issue #2, and issue #3 can be done.

But if the fourth one might impact some of these is this wise? That's kind of what I was getting at. I mean some things in the issues can be done but what can't be or what shouldn't be might be a better way of putting it?

As you didn't seem inclined to want to edit years.html when you went about renaming and removing files .. that is OK, we just have to adjust our approach to that fact .. we will have to accelerate the building of the pre-directory .winner.json files via a tool that we will write .. a tool that needed to be written eventually anyway, BTW.

Also now, before this forked repo can be merged into the main IOCCC winner repo and web site, another tool to build the years.html web page from all .winner.json files .. also one that we need to also write eventually anyway .. will need to automatically build the years.html web page before the the main IOCCC winner repo and web site can be updated.

Hmm .. what should have been changed in years.html ? What did I miss ?

[xexyl]

Though it's true I didn't want to do a major update as I think editing html files directly is risky. Then again maybe editing markdown is as well without testing it.

So what should be done please? I will look at doing it if that's helpful?

[lcn2]

We were taken out to dinner at a new place by a friend and ate something that was "off". Lack of sleep and frequent access to "you know what" (🚽🧻) while humming the SouthPark "Mr. Hanley💩" song, is our current focus until it flushes out of our system.

To maintain something to do, we have our iPhone to answer questions and provide feedback and encouragement .. interrupted as just happened now from time to time until things are flushed out of our system .. followed by rest .. followed by resetting our sleep clock.

In between all that, we will design the tool in our head, to generate the .winner.json files, the tool to build the years.html page, and the format of the author based JSON files.

[xexyl]

We were taken out to dinner at a new place by a friend and ate something that was "off". Lack of sleep and frequent access to "you know what" (🚽🧻) while humming the SouthPark "Mr. Hanley💩" song, is our current focus until it flushes out of our system.

I shouldn't laugh but I did! I'm sorry. It's the way you worded it. I also know what having to use that in the night a lot is like. Does not help with my sleep issues I can tell you. I hope you feel better soon.

If it's liquid (and I do not mean the yellow/clear one) too please remember to remain hydrated! You can even make your own isotonic drink by putting ½ teaspoon of salt into 1 cup of warm water. I've known this for years but it was also mentioned in the medical book I finally got through (quite quickly .. I did say it was light reading .. it was fun and I learnt a lot from it - not at all the only medical book I've read) so it's recently on my mind.

To maintain something to do, we have our iPhone to answer questions and provide feedback and encouragement .. interrupted as just happened now from time to time until things are flushed out of our system .. followed by rest .. followed by resetting our sleep clock.

Best wishes!

In between all that, we will design the tool in our head, to generate the .winner.json files, the tool to build the years.html page, and the format of the author based JSON files.

Sounds good.

[lcn2]

If it's liquid (and I do not mean the yellow/clear one) too please remember to remain hydrated! You can even make your own isotonic drink by putting ½ teaspoon of salt into 1 cup of warm water. I've known this for years but it was also mentioned in the medical book I finally got through (quite quickly .. I did say it was light reading .. it was fun and I learnt a lot from it - not at all the only medical book I've read) so it's recently on my mind.

Thanks, we are keeping well hydrated, which means more frequent trips .. but that is part of the process.

We have people in the house that are checking in on us too.

[xexyl]

The strings of the form "years.html#2020_ferguson2" refer to name tag in the top level years.html file. And thus will refer to the 2020/ferguson2/ winning entry directory (a rather fine entry if you ask us 🤓). So the file 2020/ferguson2/.winner.json will contain things like the manifest for that particular entry as well as JSON stuff for the list if authors .. which in this case will be "Cody_Ferguson".

Thank you for the great compliment! I enjoyed making that one. I found it fitting that I finished it on 30 April 2020, exactly 75 years after a certain man ended his life, he who started the Second World War and brought the world to such misery (though ironically we've gained things from it .. a sad thing about humans is that we both strive for and thrive on conflict).

I don't wish any harm on them either. We're all human beings and we could all be the worst sadist in different situations. This is well documented but it's something that a lot of people have a problem accepting. There's so much to that but it's OT for even OT so I won't go there. I just wanted to thank you!

I enjoyed the fact that some previous entries played with the Morse code which could be used with my Enigma machine (I found a bug in one of those two entries but I don't remember which one without looking at my remarks .. perhaps that should be mentioned somehow in the remarks but how? I guess to start out I can extract the bug I found for you to think about).

I only thought of the idea for that entry after the contest closed but due to Covid you opening it I lucked out. I had a feeling that entry had a good chance of winning - as well as Snake (which was by far the most fun for me to write ... and play).

[xexyl]

If it's liquid (and I do not mean the yellow/clear one) too please remember to remain hydrated! You can even make your own isotonic drink by putting ½ teaspoon of salt into 1 cup of warm water. I've known this for years but it was also mentioned in the medical book I finally got through (quite quickly .. I did say it was light reading .. it was fun and I learnt a lot from it - not at all the only medical book I've read) so it's recently on my mind.

Thanks, we are keeping well hydrated, which means more frequent trips .. but that is part of the process.

I know how that goes far too well! :-( ... I had two huge kidney stones (see below for fun word) in 2020 so I have to be extra careful. But I also have a highly sensitive bladder (normal function but hypersensitive) so it's a problem in other ways. I know this because of a horrible medical procedure.

We have people in the house that are checking in on us too.

That's good.

Fun word for kidney stone: renal calculus. Can you figure out why ? I guess you can but I can tell you if you don't know.

[lcn2]

Hmm .. what should have been changed in years.html ? What did I miss ?

See in issue #3, the stuff at the top about years.html links.

[lcn2]

🤩

What is this in reply to please ?

comment 1422487862

[xexyl]

Hmm .. what should have been changed in years.html ? What did I miss ?

See in issue #3, the stuff at the top about years.html links.

Oops. My mistake. I'll fix those. I have to remember what files changed.

[xexyl]

Hmm .. what should have been changed in years.html ? What did I miss ?

See in issue #3, the stuff at the top about years.html links.

Oops. My mistake. I'll fix those. I have to remember what files changed.

Oh actually. I did update it. It includes README.md. Did I miss others?

UPDATE 0

Though it does refer to README.html. Any such lines should be deleted, right?

UPDATE 1

What about hint.html ? author.html ?

[xexyl]

🤩

What is this in reply to please ?

comment 1422487862

Ah .. I thought it was a laugh so I wasn't sure what was funny. But that could be my misinterpreting that emoji (my vision certainly does not help there either)! Maybe it's just a happy smile or something.

[lcn2]

Hmm .. what should have been changed in years.html ? What did I miss ?

See in issue #3, the stuff at the top about years.html links.

Oops. My mistake. I'll fix those. I have to remember what files changed.

Oh actually. I did update it. It includes README.md. Did I miss others?

UPDATE 0

Though it does refer to README.html. Any such lines should be deleted, right?

UPDATE 1

What about hint.html ? author.html ?

For now, all files in a winning directory need a link in the years.html file.

And for now, those files can cannot be directly displayed (and thus force someone to download them) should be link into the github repo, not the web site. This "hack" allows someone to use the GitHub view to see the contents of a file.

For an example, see how near the bottom of years.html we have links such as:

<UL TYPE=square>
<LI><A HREF="1984/laman/index.html">index.html</A> - <B>README</B>
<LI><A HREF="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1984/laman/laman.c">laman.c</A>
<LI><A HREF="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1984/laman/Makefile">Makefile</A>
<LI><A HREF="1984/laman/README.md">README.md</A> - <I>original README</I>
<LI><A HREF="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1984/laman/orig.Makefile">orig.Makefile</A> - <I>original Makefile</I>
</UL>
<A NAME="1984_mullender"></A>
<P><B>mullender</B></P>

The links into the GitHub repo give the user quick viewer of the code for those files that might otherwise compel the browser to download it instead (which isn't much fun).

This is touched on in issue #3, BTW.

BTW: Later on we will change the HTML to directly display the content, similar to how GitHub does it, without causing a "download file" to occur.

BTW: For the compressed tarballs that might be present, the link WILL force a downloads .. which presumably is what the user wants. But this is a technicality to be addressed later.

[xexyl]

Hmm .. what should have been changed in years.html ? What did I miss ?

See in issue #3, the stuff at the top about years.html links.

Oops. My mistake. I'll fix those. I have to remember what files changed.

Oh actually. I did update it. It includes README.md. Did I miss others?

UPDATE 0

Though it does refer to README.html. Any such lines should be deleted, right?

UPDATE 1

What about hint.html ? author.html ?

For now, all files in a winning directory need a link in the years.html file.

Right. I was more thinking of those related to the files I renamed/removed.

And for now, those files can cannot be directly displayed (and thus force someone to download them) should be link into the github repo, not the web site. This "hack" allows someone to use the GitHub view to see the contents of a file.

Yes that's an unfortunate issue indeed!

For an example, see how near the bottom of years.html we have links such as:

<UL TYPE=square>
<LI><A HREF="1984/laman/index.html">index.html</A> - <B>README</B>
<LI><A HREF="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1984/laman/laman.c">laman.c</A>
<LI><A HREF="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1984/laman/Makefile">Makefile</A>
<LI><A HREF="1984/laman/README.md">README.md</A> - <I>original README</I>
<LI><A HREF="https://github.com/ioccc-src/temp-test-ioccc/blob/master/1984/laman/orig.Makefile">orig.Makefile</A> - <I>original Makefile</I>
</UL>
<A NAME="1984_mullender"></A>
<P><B>mullender</B></P>

The links into the GitHub repo give the user quick viewer of the code for those files that might otherwise compel the browser to download it instead (which isn't much fun).

Agreed.

This is touched on in issue #3, BTW.

Resolving it you mean? Ah .. you mean the directory clean up and consistency checks.

BTW: Later on we will change the HTML to directly display the content, similar to how GitHub does it, without causing a "download file" to occur.

That will be nice for sure.

But in the meantime this means all the links have to be updated, is that correct? Any idea how to best go about this ? It seems like it might be tedious unless a simple (or not many) regex can be contrived.

BTW: For the compressed tarballs that might be present, the link WILL force a downloads .. which presumably is what the user wants. But this is a technicality to be addressed later.

Of course.

[xexyl]

Do you want to add the GitHub check template to the repo ?

Unrelated I just fixed the FAQ - a missing entry from 2020 in a theme for entries not likely to win.

I also noticed the joke in there:

Fun reference to WarGames.

[xexyl]

How's the submit server going ?

[lcn2]

How's the submit server going ?

Thanks for asking. We are making good progress on the "you are required to changed your initial password" / initial login procedure. Next TODO is the "change your password" web page template.

[xexyl]

How's the submit server going ?

Thanks for asking. We are making good progress on the "you are required to changed your initial password" / initial login procedure. Next TODO is the "change your password" web page template.

Good luck and best wishes!

[xexyl]

[xexyl]

^ I wanted a person but it was 'not allowed'. Thus I decided for an alien instead. Of course you're familiar with the frog and boiling water that has been discredited. That is what it was a reference to though, and it's also sadly what we humans are doing to ourselves and the planet. Unfortunately the image had to be cropped to be easier to see as the image dimensions were too tall. That's why you can see at the bottom and maybe top what looks like something missing.

[xexyl]

FYI: expect an update for the cake recipe file because it's been made today and it seems like it might be nice to have a picture of the cake prior to icing it.

That update won't happen today but I am setting a reminder for tomorrow morning.

[xexyl]

Too bad Bill Ferney isn't there. Don't like the films for obvious reasons but this is the best I could do (quickly at least).

[xexyl]

[lcn2]

FYI: expect an update for the cake recipe file because it's been made today and it seems like it might be nice to have a picture of the cake prior to icing it.

That update won't happen today but I am setting a reminder for tomorrow morning.

Please consider waiting until after IOCCC28 to revise.

[xexyl]

FYI: expect an update for the cake recipe file because it's been made today and it seems like it might be nice to have a picture of the cake prior to icing it.
That update won't happen today but I am setting a reminder for tomorrow morning.

Please consider waiting until after IOCCC28 to revise.

I can do that if you like. I'll extract the photos and put it in the temp website repo directory so I will know to do it later. I'll set a reminder also.

No problem on my behalf!

[xexyl]

I have a hilarious video to share with you, a thanksgiving one, but unfortunately GitHub limits posts to 10MB and it's 16 :(

Trying to figure out what to do .. could post it on mastodon I suppose but might do something else.

[xexyl]

I have a hilarious video to share with you, a thanksgiving one, but unfortunately GitHub limits posts to 10MB and it's 16 :(

Trying to figure out what to do .. could post it on mastodon I suppose but might do something else.

Anyway I do hope you have a good and safe holiday, for whatever it might be worth!

[lcn2]

I have a hilarious video to share with you, a thanksgiving one, but unfortunately GitHub limits posts to 10MB and it's 16 :(

Trying to figure out what to do .. could post it on mastodon I suppose but might do something else.

Anyway I do hope you have a good and safe holiday, for whatever it might be worth!

Best wishes on any holiday you might have, too.

[xexyl]

I have a hilarious video to share with you, a thanksgiving one, but unfortunately GitHub limits posts to 10MB and it's 16 :(

Trying to figure out what to do .. could post it on mastodon I suppose but might do something else.

Anyway I do hope you have a good and safe holiday, for whatever it might be worth!

Best wishes on any holiday you might have, too.

Appreciate it.

Been going through photos mostly. It's getting close to my dinner time (my usual dinner time - I eat quite early). Small group. Nothing special. Maybe games. I've finished with the photos for the day .. have more to do tomorrow.

[lcn2]

We believe we have addressed all of the current questions that still need answering at this time. If we've missed something or something else needs to be clarified, please ask again.

[xexyl]

FYI: I made a bug fix in the debug output for strings in jparse. Nothing important for mkiocccentry though. I also improved documentation on the debug output (how I found it of course). Although not important for mkiocccentry you might wish to pull when you have time (I know you're focused on the contest now but just wanted to give this quick update).

I'll look at the other thread and then do other things. I somehow doubt I'll get the try script commit in today. Sorry but other things need to be done and it's later than I'd like it to be.

[xexyl]

Hilarious German advent calendar cartoon:

[xexyl]

Reposting this: had a typo in filename (hard to see in GIMP with my vision) and because you seemed to miss it.

[lcn2]

Hello 👋🏻

We hope you are doing well.

We have been online moving from on part of the property to another. We're moving from a guest bedroom that we had been “camping out in” while the area (a Garret) we plan to live in was being remodeled. The final construction 🏗️ remodeling was being finished while we were in Nigeria 🇳🇬.

Last night we spent our first night in my new place, surrounded by boxes, trying to find essential things, etc. While we managed to get enough going to setup a WiFi connection to the Internet 🛜, there is still plenty of unpacking needed to be done.

Late this morning we will have a technical review of the submit tool repo with the Swiss engineer who first designed the system. Well, we will do that after we wake up and find enough morning effectual in boxes to have a shower 🚿, get dressed and get ready for the meeting later this morning.

Once the review is complete and whatever critical edits have been made in the submit tool repo we will then plan to publish a TODO list relative to taking screenshots that are needed for the FAQ. Such a published TODO list will be posted as a comment in issue #2239, NOT here.

This is only a personal note about recent activities that impact but do not directly relate to this repo.

Happy December 🙂

UPDATE 0

The TODO list that will be posted as a comment in issue #2239, once the technical review has been completed, will include a request for a typo and comment review of the submit tool repo that will be needed prior to the FAQ update: but the technical review and technical revisions need to to be made first.

And by FAQ update we ONLY refer to the FAQs that relate to the registration and submit process, NOT the entire FAQ. We only refer to the next 2 open TODO items ("Create an initial text of the details of the ...") in issue #2239.

[xexyl]

Hello 👋🏻

We hope you are doing well.

Well I got some things done with jparse (modularising something and also some documentation updates). Unfortunately that was difficult as I was very bleary eyed. I think I have the try script (or almost all of it) for next/ done but I have a question and since my eyes are so bleary I'm not going to commit today as I can't tell if I do have everything (besides the question needing an answer that I asked in the other issue).

We have been online moving from on part of the property to another. We're moving from a guest bedroom that we had been “camping out in” while the area (a Garret) we plan to live in was being remodeled. The final construction 🏗️ remodeling was being finished while we were in Nigeria 🇳🇬.

Best wishes!

Last night we spent our first night in my new place, surrounded by boxes, trying to find essential things, etc. While we managed to get enough going to setup a WiFi connection to the Internet 🛜, there is still plenty of unpacking needed to be done.

Someone slipped .. 'we spent ... my' :-) Anyway, hope it was okay in the new room and hope the unboxing things goes well. Better hurry so you can make sure Boxing Day goes well!

Late this morning we will have a technical review of the submit tool repo with the Swiss engineer who first designed the system. Well, we will do that after we wake up and find enough morning effectual in boxes to have a shower 🚿, get dressed and get ready for the meeting later this morning.

Good luck with that!

Once the review is complete and whatever critical edits have been made in the submit tool repo we will then plan to publish a TODO list relative to taking screenshots that are needed for the FAQ. Such a published TODO list will be posted in issue #2239, NOT here.

Of course!

This is only a personal note about recent activities that impact but do not directly relate to this repo.

Nice to hear though .. thanks and best wishes!

Happy December 🙂

You too! I don't know but I am pondering watching Bad Santa today. But it depends on if I can get other things done (if I can see enough to do so).

Good luck with the unpacking!

[xexyl]

Just had some fun...

[xexyl]

UPDATE 0

The TODO list that will be posted as a comment in issue #2239, once the technical review has been completed, will include a request for a typo and comment review of the submit tool repo that will be needed prior to the FAQ update: but the technical review and technical revisions need to to be made first.

And by FAQ update we ONLY refer to the FAQs that relate to the registration and submit process, NOT the entire FAQ. We only refer to the next 2 open TODO items ("Create an initial text of the details of the ...") in issue #2239.

Sure!

[xexyl]

First thought when I saw the photos some years back ... but redid it a bit now.

[xexyl]

I was hoping to do checks on the recent edits today but it's been a really odd day. Instead though enjoy this that I encountered (coming up in next comment) ... maybe tomorrow I can do the checks. The day just did not go as I planned. Not bad but quite different.

[xexyl]

[xexyl]

I guess you know the difference so I won't explain it but if that's not so I guess you'd probably look it up. Anyway:

[xexyl]

Seems about right!

[xexyl]

Seems about right!

It'd be slightly better with making changing 3 to 'grab the nearest towel' and then making 'leave building' number 4 .. but as a Dutch friend of mine (who I haven't heard from in years) said: can't have it all.

[xexyl]

Good morning! I just did this with Safari .. thought you'd enjoy it (normally I'd write hypothesised but since NASA is American ...):

[xexyl]

That's for the future though. This is the current one: