Skip to main content
replaced http://codereview.stackexchange.com/ with https://codereview.stackexchange.com/
Source Link

When in doubt, I always refer to the on-topic helpcenteron-topic helpcenter. In this case, there is no notion about malicious code (and/or code which could be used in a malicious manner, for those who care about the difference).

One could also check the "What questions should I avoid asking?" page"What questions should I avoid asking?" page, where malicious code isn't listed either.

Now we've established your question is not off-topic, let's take a look at how good questions are formulated and what you're proposing:

I tried to whittle the code down as much as I could to a "base" program so that a script kiddie wouldn't stumble across it and wreck havoc.

Although I can understand your sentiment and agree with your intent, it's a problem on Code Review. We like context. A lot. Good context allows us to write good reviews. Great context allows us to write great reviews.

Please, don't refrain from telling us exactly what it's supposed to do. Extra benefit from this is it allows us to safely test your code without causing harm to our own computers and/or data, which might happen if you downplay the risks too much.

As @rolfl said, you may get some negative reactions. That's the risk of posting controversial questions. However, this community won't burn you on it. I totally expect the most of us will treat your question with respect.

When in doubt, I always refer to the on-topic helpcenter. In this case, there is no notion about malicious code (and/or code which could be used in a malicious manner, for those who care about the difference).

One could also check the "What questions should I avoid asking?" page, where malicious code isn't listed either.

Now we've established your question is not off-topic, let's take a look at how good questions are formulated and what you're proposing:

I tried to whittle the code down as much as I could to a "base" program so that a script kiddie wouldn't stumble across it and wreck havoc.

Although I can understand your sentiment and agree with your intent, it's a problem on Code Review. We like context. A lot. Good context allows us to write good reviews. Great context allows us to write great reviews.

Please, don't refrain from telling us exactly what it's supposed to do. Extra benefit from this is it allows us to safely test your code without causing harm to our own computers and/or data, which might happen if you downplay the risks too much.

As @rolfl said, you may get some negative reactions. That's the risk of posting controversial questions. However, this community won't burn you on it. I totally expect the most of us will treat your question with respect.

When in doubt, I always refer to the on-topic helpcenter. In this case, there is no notion about malicious code (and/or code which could be used in a malicious manner, for those who care about the difference).

One could also check the "What questions should I avoid asking?" page, where malicious code isn't listed either.

Now we've established your question is not off-topic, let's take a look at how good questions are formulated and what you're proposing:

I tried to whittle the code down as much as I could to a "base" program so that a script kiddie wouldn't stumble across it and wreck havoc.

Although I can understand your sentiment and agree with your intent, it's a problem on Code Review. We like context. A lot. Good context allows us to write good reviews. Great context allows us to write great reviews.

Please, don't refrain from telling us exactly what it's supposed to do. Extra benefit from this is it allows us to safely test your code without causing harm to our own computers and/or data, which might happen if you downplay the risks too much.

As @rolfl said, you may get some negative reactions. That's the risk of posting controversial questions. However, this community won't burn you on it. I totally expect the most of us will treat your question with respect.

Source Link
Mast Mod
  • 13.9k
  • 2
  • 37
  • 89

When in doubt, I always refer to the on-topic helpcenter. In this case, there is no notion about malicious code (and/or code which could be used in a malicious manner, for those who care about the difference).

One could also check the "What questions should I avoid asking?" page, where malicious code isn't listed either.

Now we've established your question is not off-topic, let's take a look at how good questions are formulated and what you're proposing:

I tried to whittle the code down as much as I could to a "base" program so that a script kiddie wouldn't stumble across it and wreck havoc.

Although I can understand your sentiment and agree with your intent, it's a problem on Code Review. We like context. A lot. Good context allows us to write good reviews. Great context allows us to write great reviews.

Please, don't refrain from telling us exactly what it's supposed to do. Extra benefit from this is it allows us to safely test your code without causing harm to our own computers and/or data, which might happen if you downplay the risks too much.

As @rolfl said, you may get some negative reactions. That's the risk of posting controversial questions. However, this community won't burn you on it. I totally expect the most of us will treat your question with respect.