moodle.org not affected - added link to post

[digitalsparky]

Before submitting your pull-request:

• name of the pull request should be "Add: domain, domain, domain (proxy + DNS)" or "Remove: domain (static), domain (DNS only), domain (static)"
• do not ask for removal of actually affected websites (any websites using cloudflare reverse proxy)

HOW TO REMOVE YOUR SITE

1. Verify the site is static and contains no user or sensitive data (I will remove it immediately once I confirm)

OR

1. Verify ownership, send me an email from @yourdomain.com, post a random nonce on the domain, or provide keybase proof
2. Verify you did not use the Cloudflare proxy service during the affected period

[coderobe]

Please change not affected to no leaked data found in several search engine caches, unless there were no critical components proxied through CF during the affected time period.

[digitalsparky]

moodle.org does not have the affected features enabled on it, thus not affected.

[coderobe]

That is not correct, moodle.org user data was at risk just because it was proxied through CF at the time. Please take a look at issue #127 and issue #87 for additional info.

[digitalsparky]

Updated message

[digitalsparky]

Fair enough, updated message as requested.