Sample Email for those who register for the IOCCC

[lcn2]

The following is an example of the email we plan to send to those who have registered for the IOCCC.

The purpose for this Email is to provide IOCCC submit server login information as well as some important links on how to proceed.

Comments and edits welcome

Sample Email Follows

Hello IOCCC registrant,

Thank you for registering for the International Obfuscated C Code Contest (IOCCC)!

The IOCCC judges (well actually a tool written by them :-)) have generated
an account for you on the IOCCC submit server:

    https://submit.ioccc.org

Please use the following account information when uploading your submissions:

    username: 00000000-0000-4000-8000-000000000000
    password: example-password%123.456

    IMPORTANT: You MUST login and change your password before: YYYY-MM-DD HH:MM:SS.123456 UTC

For information on how to change your IOCCC submit server password, see:

    https://www.ioccc.org/next/pw-change.html

After you have logged in and changed your password, please proceed with Step 5:

    https://www.ioccc.org/quick-start.html#step_5

We recommend that you review the IOCCC Rules and Guidelines, and FAQ:

    https://www.ioccc.org/next/rules.html
    https://www.ioccc.org/next/guidelines.html
    https://www.ioccc.org/faq.html

If you have questions about the Rules and Guidelines, and FAQ, see:

    https://www.ioccc.org/faq.html#question
    https://www.ioccc.org/contact.html

Be sure that you upload your submissions before the date when the contest
enters the judging state.  For information on this deadline, see:

    https://www.ioccc.org/next/rules.html#dates

Also be sure you follow the IOCCC news on the web site and Mastodon:

    https://www.ioccc.org/news.html
    https://fosstodon.org/@ioccc

Best wishes on writing and uploading your obfuscated submissions, and
THANK YOU for taking the time and making an effort to submit to the IOCCC!

-- The IOCCC Judges
   https://www.ioccc.org/contact.html

=-=

p.s. Consider joining the IOCCC Discord server:

    https://discord.gg/Wa42Qujwnw

[SirWumpus]

Novel suggestion, that's probably more trouble than its worth, but what about creating subdomains for key pages, eg.

https://rules.ioccc.org
https://guidelines.ioccc.org
https://faq.ioccc.org
https://contact.ioccc.org
https://news.ioccc.org
https://archive.ioccc.org   https://winners.ioccc.org  (maybe both to the same area).

Might just be me, but I like the "clean" look. It should only be done for the most important parts of the web site. Anyway, its just a thought.

[xexyl]

Novel suggestion, that's probably more trouble than its worth, but what about creating subdomains for key pages, eg.

https://rules.ioccc.org
https://guidelines.ioccc.org
https://faq.ioccc.org
https://contact.ioccc.org
https://news.ioccc.org
https://archive.ioccc.org   https://winners.ioccc.org  (maybe both to the same area).

Might just be me, but I like the "clean" look. It should only be done for the most important parts of the web site. Anyway, its just a thought.

Oh I like that. But I have many subdomains in my (authoritative) DNS server.

The IOCCC uses Let's Encrypt and so do I. There would be two ways to go about the DNS side. One way would be to use the wildcard RR like:

*                   3600        IN      A       a.b.c.d
# you could put AAAA records here too if necessary and you can have other A records also
                                                TXT     "v=spf1 -all"
                                                SPF     "v=spf1 -all"

Yes I use SPF (as you can see :-) ).

Another way would be (since it's not many subdomains in the zone) something like:

rules              3600        IN      CNAME   ioccc.org.
guidelines     3600       IN      CNAME   ioccc.org.
# etc.

And then as for Let's Encrypt it would depend on what is used. I use dehydrated so I just have a line for the names which are for the same cert.

I use apache so I just have VirtualHosts for each one as necessary.

BUT of course the IOCCC uses GitHub and I have no idea how they handle that so it might not be feasible (if it's deemed worth the effort).

However that is how it can be done at the very least on the DNS side. But again maybe with GitHub pages it is different (I guess it is).

EDIT

Fixed dots added due to double space (in DNS zone config).

[xexyl]

Novel suggestion, that's probably more trouble than its worth, but what about creating subdomains for key pages, eg.

https://rules.ioccc.org
https://guidelines.ioccc.org
https://faq.ioccc.org
https://contact.ioccc.org
https://news.ioccc.org
https://archive.ioccc.org   https://winners.ioccc.org  (maybe both to the same area).

Might just be me, but I like the "clean" look. It should only be done for the most important parts of the web site. Anyway, its just a thought.

Oh I like that. But I have many subdomains in my (authoritative) DNS server.

The IOCCC uses Let's Encrypt and so do I. There would be two ways to go about the DNS side. One way would be to use the wildcard RR like:

*                   3600        IN      A       a.b.c.d
# you could put AAAA records here too if necessary and you can have other A records also
                                                TXT     "v=spf1 -all"
                                                SPF     "v=spf1 -all"

Yes I use SPF (as you can see :-) ).

Another way would be (since it's not many subdomains in the zone) something like:

rules              3600        IN      CNAME   ioccc.org.
guidelines     3600       IN      CNAME   ioccc.org.
# etc.

And then as for Let's Encrypt it would depend on what is used. I use dehydrated so I just have a line for the names which are for the same cert.

I use apache so I just have VirtualHosts for each one as necessary.

BUT of course the IOCCC uses GitHub and I have no idea how they handle that so it might not be feasible (if it's deemed worth the effort).

However that is how it can be done at the very least on the DNS side. But again maybe with GitHub pages it is different (I guess it is).

EDIT

Fixed dots added due to double space (in DNS zone config).

Oh and as far as the web pages. That might be more problematic due to the way the website is generated. I would think so as it's in the same location. In my apache config I have a directory for each subdomain. That could be done differently perhaps but I think that even if GitHub would allow this stuff this would be more problematic (not saying it couldn't be done but ...). Of course there is another way it could be done and that is simply set up the subdomains in the zone (making sure to set up with Let's Encrypt) and have the index.html (and/or other pages) forward to the appropriate pages on the main website.

[lcn2]

BUT of course the IOCCC uses GitHub and I have no idea how they handle that so it might not be feasible (if it's deemed worth the effort).

Correct.

[lcn2]

Oh and as far as the web pages. That might be more problematic due to the way the website is generated. I would think so as it's in the same location. In my apache config I have a directory for each subdomain. That could be done differently perhaps but I think that even if GitHub would allow this stuff this would be more problematic (not saying it couldn't be done but ...).

Agreed.

[lcn2]

While GH-discussioncomment-12208815 a novel suggestion, we will NOT rework the URLs of the website. NOR will we setup some sort of dual URLs for the same web page.

Thanks for the suggestion, regardless.

[xexyl]

The following is an example of the email we plan to send to those who have registered for the IOCCC.

The purpose for this Email is to provide IOCCC submit server login information as well as some important links on how to proceed.

Comments and edits welcome

Sample Email Follows

Hello IOCCC registrant,

Thank you for registering for the International Obfuscated C Code Contest (IOCCC)!

The IOCCC judges (well actually a tool written by them :-)) have generated
an account for you on the IOCCC submit server:

    https://submit.ioccc.org

Please use the following account information when uploading your submissions:

    username: 00000000-0000-4000-8000-000000000000
    password: example-password%123.456

    IMPORTANT: You MUST login and change your password before: YYYY-MM-DD HH:MM:SS.123456 UTC

For information on how to change your IOCCC submit server password, see:

    https://www.ioccc.org/next/pw-change.html

After you have logged in and changed your password, please proceed with Step 5:

    https://www.ioccc.org/quick-start.html#step_5

We recommend that you review the IOCCC Rules and Guidelines, and FAQ:

    https://www.ioccc.org/next/rules.html
    https://www.ioccc.org/next/guidelines.html
    https://www.ioccc.org/faq.html

If you have questions about the Rules and Guidelines, and FAQ, see:

    https://www.ioccc.org/faq.html#question
    https://www.ioccc.org/contact.html

Be sure that you upload your submissions before the date when the contest
enters the judging state.  For information on this deadline, see:

    https://www.ioccc.org/next/rules.html#dates

Also be sure you follow the IOCCC news on the web site and Mastodon:

    https://www.ioccc.org/news.html
    https://fosstodon.org/@ioccc

Best wishes on writing and uploading your obfuscated submissions, and
THANK YOU for taking the time and making an effort to submit to the IOCCC!

-- The IOCCC Judges
   https://www.ioccc.org/contact.html

=-=

p.s. Consider joining the IOCCC Discord server:

    https://discord.gg/Wa42Qujwnw

It's good but I would change a couple things: minor grammar things (how surprising from me :-) ).

I would change the words (which appear to be in more than one line):

... the IOCCC Rules and Guidelines, and FAQ

to be instead:

the IOCCC Rules, Guidelines and FAQ

OR if you prefer for the so-called Oxford comma:

the IOCCC Rules, Guidelines, and FAQ

This is a subtle thing but it is technically more correct. You could also (if you wanted though it might not be as correct and some might even argue not as clear though that's subjective) change it to:

the IOCCC Rules/Guidelines and FAQ
or
the IOCCC Rules/Guidelines, and FAQ

Other than that it looks great!

(Disclaimer: still kind of waking up.)

[lcn2]

the IOCCC Rules, Guidelines, and FAQ

We will use the above suggested text.

[lcn2]

Below is the revised sample (complete with fake account and fake passwords 😉).

Comments and suggestions welcome.

Sample Email follows

Hello IOCCC registrant,

Thank you for registering for the International Obfuscated C Code Contest (IOCCC)!

The IOCCC judges (well, actually a tool written by them :-)) have generated
an account for you on the IOCCC submit server:

    https://submit.ioccc.org

Please use the following account information to access the IOCCC submit server.

    username: 00000000-0000-4000-8000-000000000000
    password: example-password%123.456

    IMPORTANT: You MUST login and change your password before: YYYY-MM-DD HH:MM:SS.123456 UTC

For information on how to change your IOCCC submit server password, see:

    https://www.ioccc.org/next/pw-change.html

After you have logged in and changed your password, please proceed with Step 5:

    https://www.ioccc.org/quick-start.html#step_5

We recommend that you review the IOCCC Rules, Guidelines, and FAQ:

    https://www.ioccc.org/next/rules.html
    https://www.ioccc.org/next/guidelines.html
    https://www.ioccc.org/faq.html

If you have questions about the Rules, Guidelines, or FAQ, see:

    https://www.ioccc.org/faq.html#question
    https://www.ioccc.org/contact.html

Be sure that you upload your submissions before the date when the contest
enters the judging state.  For information on this deadline, see:

    https://www.ioccc.org/next/rules.html#dates

Also be sure you follow the IOCCC news on the web site and Mastodon:

    https://www.ioccc.org/news.html
    https://fosstodon.org/@ioccc

Best wishes on writing and uploading your obfuscated submissions, and
THANK YOU for taking the time and making an effort to submit to the IOCCC!

-- The IOCCC Judges
   https://www.ioccc.org/contact.html

=-=

p.s. Consider joining the IOCCC Discord server:

    https://discord.gg/Wa42Qujwnw

p.p.s. PLEASE login and change our password before the above mentioned
       deadline, otherwise the server will deactivate your account!

[xexyl]

Typo: 'our password'.

I would also suggest that we be consistent with the website and have one word 'website' not 'web site'.

Haven't checked the links but other than that it looks good (if you want the Oxford comma :-) ).

[lcn2]

Revised as suggested, @xexyl .. Thanks!

Sample Email follows

Hello IOCCC registrant,

Thank you for registering for the International Obfuscated C Code Contest (IOCCC)!

The IOCCC judges (well, actually a tool written by them :-)) have generated
an account for you on the IOCCC submit server:

    https://submit.ioccc.org

Please use the following account information to access the IOCCC submit server:

    username: 00000000-0000-4000-8000-000000000000
    password: example-password%123.456

    IMPORTANT: You MUST login and change your password before: YYYY-MM-DD HH:MM:SS.123456 UTC

For information on how to change your IOCCC submit server password, see:

    https://www.ioccc.org/next/pw-change.html

After you have logged in and changed your password, please proceed with Step 5:

    https://www.ioccc.org/quick-start.html#step_5

We recommend that you review the IOCCC Rules, Guidelines, and FAQ:

    https://www.ioccc.org/next/rules.html
    https://www.ioccc.org/next/guidelines.html
    https://www.ioccc.org/faq.html

If you have questions about the Rules, Guidelines, or FAQ, see:

    https://www.ioccc.org/faq.html#question

Be sure that you upload your submissions before the date when the contest
enters the judging state.  For information on this deadline, see:

    https://www.ioccc.org/next/rules.html#dates

Also be sure you follow the IOCCC news on the website and Mastodon:

    https://www.ioccc.org/news.html
    https://fosstodon.org/@ioccc

Best wishes on writing and uploading your obfuscated submissions, and
THANK YOU for taking the time and making an effort to submit to the IOCCC!

-- The IOCCC Judges
   https://www.ioccc.org/contact.html

=-=

p.s. Consider joining the IOCCC Discord server:

    https://discord.gg/Wa42Qujwnw

p.p.s. PLEASE login and change your password before the above mentioned
       deadline, otherwise the server will deactivate your account!

[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.