Welcome to Codidact Meta!
Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.
Post History
Should you assume knowledge of all site rules? Should you assume knowledge of only "main" site rules but not all? I'm not sure what distinction you are trying to make here between "all si...
Answer
#3: Post edited
- > * Should you assume knowledge of all site rules?
- > * Should you assume knowledge of only "main" site rules but not all?
- I'm not sure what distinction you are trying to make here between "all site rules" and "only main site rules". In general I think it's reasonable to assume familiarity with rules *but* also allow for that someone might simply have missed something, might not realize the implications of something they posted (most people on Earth don't have English as their first language, and nuances can be difficult to get right in addition to being culturally dependent), and so on.
- In general, [assume good intent](/policy/code-of-conduct).
- > * How friendly should you be? Is it okay to sound angry when you're angry at new users breaking the rules? Do you have to sound friendly and helpful even though you don't genuinely feel that way?
- If you can't be friendly and helpful (or [nice and respectful](/policy/code-of-conduct)) in guiding someone, I really recommend that you don't even try. Raise a moderator flag instead and go on with your day. That's what moderator flags are for. In the words of the code of conduct, [always be constructive](/policy/code-of-conduct).
- > * Should you give feedback in a *negative* tone? Meaning chastising the poster for breaking a rule.
Absolutely not. Again check the code of conduct: [be nice; be respectful; always be constructive](/policy/code-of-conduct).- Chastising a user, even if you feel that the user this is directed at somehow "deserves" it, would certainly be valid reason for *someone else* (that user or another person) to raise a moderator flag regarding that content.
- If you see a *moderator* doing it, raise that with the Codidact team. See the "contact us" link in the page footer.
- The [Codidact code of conduct](/policy/code-of-conduct) really isn't long or complicated, and is intended to lay the land for interactions across the network. If for any reason you feel you can't follow it in posting something, please refrain from that post. It will save everyone grief.
- > * Should you assume knowledge of all site rules?
- > * Should you assume knowledge of only "main" site rules but not all?
- I'm not sure what distinction you are trying to make here between "all site rules" and "only main site rules". In general I think it's reasonable to assume familiarity with rules *but* also allow for that someone might simply have missed something, might not realize the implications of something they posted (most people on Earth don't have English as their first language, and nuances can be difficult to get right in addition to being culturally dependent), and so on.
- In general, [assume good intent](/policy/code-of-conduct).
- > * How friendly should you be? Is it okay to sound angry when you're angry at new users breaking the rules? Do you have to sound friendly and helpful even though you don't genuinely feel that way?
- If you can't be friendly and helpful (or [nice and respectful](/policy/code-of-conduct)) in guiding someone, I really recommend that you don't even try. Raise a moderator flag instead and go on with your day. That's what moderator flags are for. In the words of the code of conduct, [always be constructive](/policy/code-of-conduct).
- > * Should you give feedback in a *negative* tone? Meaning chastising the poster for breaking a rule.
- Absolutely not. Borrowing from the code of conduct: [be nice; be respectful; always be constructive](/policy/code-of-conduct).
- Chastising a user, even if you feel that the user this is directed at somehow "deserves" it, would certainly be valid reason for *someone else* (that user or another person) to raise a moderator flag regarding that content.
- If you see a *moderator* doing it, raise that with the Codidact team. See the "contact us" link in the page footer.
- The [Codidact code of conduct](/policy/code-of-conduct) really isn't long or complicated, and is intended to lay the land for interactions across the network. If for any reason you feel you can't follow it in posting something, please refrain from that post. It will save everyone grief.
#2: Post edited
- > * Should you assume knowledge of all site rules?
- > * Should you assume knowledge of only "main" site rules but not all?
- I'm not sure what distinction you are trying to make here between "all site rules" and "only main site rules". In general I think it's reasonable to assume familiarity with rules *but* also allow for that someone might simply have missed something, might not realize the implications of something they posted (most people on Earth don't have English as their first language, and nuances can be difficult to get right in addition to being culturally dependent), and so on.
- In general, [assume good intent](/policy/code-of-conduct).
- > * How friendly should you be? Is it okay to sound angry when you're angry at new users breaking the rules? Do you have to sound friendly and helpful even though you don't genuinely feel that way?
- If you can't be friendly and helpful (or [nice and respectful](/policy/code-of-conduct)) in guiding someone, I really recommend that you don't even try. Raise a moderator flag instead and go on with your day. That's what moderator flags are for. In the words of the code of conduct, [always be constructive](/policy/code-of-conduct).
- > * Should you give feedback in a *negative* tone? Meaning chastising the poster for breaking a rule.
- Absolutely not. Again check the code of conduct: [be nice; be respectful; always be constructive](/policy/code-of-conduct).
- Chastising a user, even if you feel that the user this is directed at somehow "deserves" it, would certainly be valid reason for *someone else* (that user or another person) to raise a moderator flag regarding that content.
- If you see a *moderator* doing it, raise that with the Codidact team. See the "contact us" link in the page footer.
The [Codidact code of conduct](/policy/code-of-conduct) really isn't long or complicated.
- > * Should you assume knowledge of all site rules?
- > * Should you assume knowledge of only "main" site rules but not all?
- I'm not sure what distinction you are trying to make here between "all site rules" and "only main site rules". In general I think it's reasonable to assume familiarity with rules *but* also allow for that someone might simply have missed something, might not realize the implications of something they posted (most people on Earth don't have English as their first language, and nuances can be difficult to get right in addition to being culturally dependent), and so on.
- In general, [assume good intent](/policy/code-of-conduct).
- > * How friendly should you be? Is it okay to sound angry when you're angry at new users breaking the rules? Do you have to sound friendly and helpful even though you don't genuinely feel that way?
- If you can't be friendly and helpful (or [nice and respectful](/policy/code-of-conduct)) in guiding someone, I really recommend that you don't even try. Raise a moderator flag instead and go on with your day. That's what moderator flags are for. In the words of the code of conduct, [always be constructive](/policy/code-of-conduct).
- > * Should you give feedback in a *negative* tone? Meaning chastising the poster for breaking a rule.
- Absolutely not. Again check the code of conduct: [be nice; be respectful; always be constructive](/policy/code-of-conduct).
- Chastising a user, even if you feel that the user this is directed at somehow "deserves" it, would certainly be valid reason for *someone else* (that user or another person) to raise a moderator flag regarding that content.
- If you see a *moderator* doing it, raise that with the Codidact team. See the "contact us" link in the page footer.
- The [Codidact code of conduct](/policy/code-of-conduct) really isn't long or complicated, and is intended to lay the land for interactions across the network. If for any reason you feel you can't follow it in posting something, please refrain from that post. It will save everyone grief.
#1: Initial revision
> * Should you assume knowledge of all site rules? > * Should you assume knowledge of only "main" site rules but not all? I'm not sure what distinction you are trying to make here between "all site rules" and "only main site rules". In general I think it's reasonable to assume familiarity with rules *but* also allow for that someone might simply have missed something, might not realize the implications of something they posted (most people on Earth don't have English as their first language, and nuances can be difficult to get right in addition to being culturally dependent), and so on. In general, [assume good intent](/policy/code-of-conduct). > * How friendly should you be? Is it okay to sound angry when you're angry at new users breaking the rules? Do you have to sound friendly and helpful even though you don't genuinely feel that way? If you can't be friendly and helpful (or [nice and respectful](/policy/code-of-conduct)) in guiding someone, I really recommend that you don't even try. Raise a moderator flag instead and go on with your day. That's what moderator flags are for. In the words of the code of conduct, [always be constructive](/policy/code-of-conduct). > * Should you give feedback in a *negative* tone? Meaning chastising the poster for breaking a rule. Absolutely not. Again check the code of conduct: [be nice; be respectful; always be constructive](/policy/code-of-conduct). Chastising a user, even if you feel that the user this is directed at somehow "deserves" it, would certainly be valid reason for *someone else* (that user or another person) to raise a moderator flag regarding that content. If you see a *moderator* doing it, raise that with the Codidact team. See the "contact us" link in the page footer. The [Codidact code of conduct](/policy/code-of-conduct) really isn't long or complicated.