Cody Boone Ferguson
1ac055fa85
In most cases the word was changed to 'obfuscation' as it was about
obfuscation, not deobfuscation. In some cases like 1995/leo since the
file was (in 1995/leo) about a secret switch it was changed to
'secret.md' (and 'secret.html') but there were others like that as well.
One entry had the words 'spoiling the size rule' but this had been
changed to 'deobfuscating the size rule' which was obviously wrong.
In the latter YYYY/README.md files the judges had written after some
entries (brief summaries) '...
...We'll stop spouting spoilers now. Have fun exploring all the
entries!
but that was changed to:
...We'll stop spouting deobfuscation information now. Have fun
exploring all the entries!
which wasn't really about deobfuscation but just a brief summary of what
the entries did.
And in the most problematic case (at least for me :-), 2018/ferguson) I
had put a joke in:
... but it's the only Easter egg I won't spoil
but it was changed to 'won't deobfuscate' which not only is not what it
is but it spoilt the joke.
In some cases the word was changed back to 'SPOILER' (or similar) but in
most cases not. I believe it should be better now. There are some
caveats, however, as below.
Although make find_missing_links is okay I do not remember if this will
catch links that refer to '%%REPO_URL%%' or other pandoc tokens. This
means I might have to go back to some earlier years to verify links are
okay. That should not take that much time I hope.
It might also be that some wording can still be improved some but it is
hoped this will be discovered when checking links and looking over the
manifest (which obviously changed).
1.4 KiB
1.4 KiB
To build:
make
To use:
./prog
Try:
./try.sh
Judges' remarks:
At this point you might be wondering, WTF?*
-
What The Freak (polite form)
-
What's This For? (you may be wondering)
-
What the Fish (python form)
How is this code obfuscated? Well look again:
less prog.c
more prog.c
Where did those underscores come from? Well RTFS!**
** Read the Freaking Source (polite form) ** Read The Freaking Screen (polite form)
If you are still puzzled, look at prog.c with your favorite text editor.
Author's remarks:
Follow these instructions literally!
cat prog.c
gcc -w -o prog prog.c
./prog
You will do a double take.
Hint 1: Do less prog.c. You will see an emphasized string if your
terminal supports bold.
Hint 2: Do wc -c prog.c. This is very long one-liner.
Hint 3: Open the source with an editor like vim or emacs.