The try section in the README.md file did not refer to the script.
The URL in the cookie recipe file was updated to refer to the domain
that the old one redirects to just in case the old one ever expires or
no longer redirects to the more recent domain. The thanks file notes
this for reference as an aside for context and historical purposes,
noting both URLs.
And since the try.sh scrambles and descrambles a cookie recipe I will
offer this funny story from decades ago that my mum tells every so
often: my uncle, who lived with my parents, and my father were at home
and they made 12 dozen cookies. They called my mum at her work and told
her: we made twelve dozen cookies and we saved you one! My mum thought
they meant she saved them one dozen cookies, already suggesting they had
eaten too many. But no. They left her one cookie! The reason is they
couldn't get the milk and cookies balanced so the only obvious thing to
do was to eat 143 cookies. Obviously. They were quite sick and nobody
was sympathetic to their ridiculous stunt.
So let that be a lesson to anyone who decides they want to eat 143
cookies: just eat 142 and you'll be just fine, weight gain
notwithstanding! :-) (Okay maybe keep it at 24 .. unless they're
chocolate in which case you might want to eat three, four, five, however
many dozen you can fit in your stomach.)
Only the last paragraph is not sincere. The first really did happen.
These files are generated based on data from /dev/urandom and are
example uses. As anyone running this entry in a copy of the repo (fork
or otherwise) would get that the files are modified in git status (after
running the example commands) it seems to me that they should be deleted
and added to .gitignore which I have now done.
My guess (but it's just a guess) is that when the repo was set up these
commands were run and perhaps a git add . was done from the root
directory.
The 2020 winners are hinted it, but the source code is not there,
nor are the hints. Someone could look into the HTML and
see what was commented out, but that is not a problem because
WHO won is known and the name of their AWARD is known already.
Moreover a number of the winners have talked about what their
entirs do, so the commented out spoiler text is not a bit problem.
One will find HTML commented out with:
<!-- XXX remove when 2020 is ready
2020 links here
XXX remove when 2020 is ready -->
The "XXX remove when 2020 is ready" string is found at the
start and end comment blocks. Again, soneone could read
what was commented out, but that is OK since most of that
information is known or can be known. The following files
have such HTML comment blocks in them.
./winners.html
./years-spoiler.html
./years.html
In addition, ./all/summary.txt was modified to not
include the 2020 entries for the momemt.
The 2020 winner code AND write-ups are NOT part of this set.
p.s. The all/all.tar.bz2 does not contain the 2020 source code (yet?).
Cody Boone Ferguson