(Redirected from S:WHYREJECT)


If your Scratch Wiki account request was rejected, you probably received a message similar to the one below:

Unfortunately, your Scratch Wiki account request was not accepted because you did not read https://en.scratch-wiki.info/wiki/S:CONTRIB prior to submitting your request. You may submit a new account request in about a week. If you have any questions, please read https://en.scratch-wiki.info/wiki/S:WHYREJECT for more information.

If your request was rejected and you think you did read the account request instructions or you are still interested in obtaining a Wiki account, this page should help answer your questions.

Note Warning: Before you tell us you did read S:CONTRIB, please read the "Do not tell us you did read S:CONTRIB" section.

But I did read the page!

If you received the rejection message above or something similar, you did not follow all of the instructions on that page in your request notes. Generally, when we give that rejection message, the request completely missed several elements on the page, though we still reject requests if they miss any important items. We check that users follow all of the instructions on that page, and we expect users to read the whole page.

Do not tell us you did read S:CONTRIB

This section in a nutshell: We will not change the status of your request because of you telling us you read S:CONTRIB.

Your request notes speak for themselves as to whether or not you read S:CONTRIB. Telling us you did read it is a waste of time and we will just point you here. Once we reject your request, you must submit another request if you still want an account (see the "Can I request again?" section).

What did I miss?

This section in a nutshell: We will not tell you what you missed in order to ensure you read the page completely.

In order to prevent people from taking shortcuts and just fixing one quick thing without reading the page completely, we probably will not say what you missed. Look through the account request instructions and see what items you may not have followed. If you still can't figure it out, try reading the sample request notes for examples of good and bad requests as well as a list of the common mistakes we see.

Can I request again?

This section in a nutshell: Yes, but you have to wait about a week.

Yes, you can submit another request, but you have to wait a bit. It takes one or two weeks for old requests to clear out of the list, so once your request clears out, you can submit a new one.

Why the wait?

We have the wait in for several reasons. First, it prevents users from spamming us with multiple requests. Second, it helps encourage users to make sure they read through the instructions carefully. Third and finally, it allows us to refer to recently rejected requests if necessary.

Why do you use that rejection message?

We use that rejection message to make it clear that the reason we are rejecting the request is the fact that it didn't meet the requirements on the account request instructions.

This seems overly harsh for missing one minor thing

We will only outright reject requests when they are missing significant parts of what we ask for or otherwise do not follow the guidelines (such as multiple significant spelling/grammar mistakes). When a request meets almost all of the requirements, then we will instead point out what the user missed and ask them to submit a follow-up comment correcting it, and if the follow-up comment satisfactorily addresses the issue with the original request, then the request will be accepted.

Common mistakes

We often see requests that have these mistakes in them:

  • Skipping the second section (what to add)
  • Not including enough examples (we ask for three flaws and two things to add)
  • Not actually providing examples for the flaws, just listing categories
  • Listing "flaws" that are not actually mistakes in the article
  • Improper spelling/grammar/sentence structure
  • Not being specific with examples of what to add
  • Not referring to the flawed article (i.e. making examples about flaws in other articles)
  • Copying flaws from the sample request notes