Policy: Questions, answers, and comments may not be auto-generated on Academia.SE.
While the technology is impressive, these answers are not based on references or personal expertise in academia. Rather, our experience is that they only contain contain common sense advice that is often off-topic. There is also significant potential for harm since the AI might produce plausible-looking answers to difficult questions; these might attract upvotes and give the impression of credibility when in fact the answer could well be incorrect.
If there is some reason why you feel that you need to auto-generate text, it's probably best to seek pre-approval on meta. Note that simply citing the AI model used or disclosing that the text was auto-generated is not sufficient under this policy (though it's a step in the right direction).
What should I do if I see something that I think was written by a chatbot?
Flag it! Good-faith flags on questions or answers will usually be marked "helpful." Good-faith flags on comments are also appreciated, but mechanically such flags are always marked as "declined" unless the comment is deleted.
How will you know if someone has used a chatbot?
We deliberately don't reveal our entire bag of tricks. It is possible there will be some false positives. However, answers that are sufficiently low-quality as to be indistinguishable from a chatbot are also not really desirable, so we don't see this as much of a problem. False negatives are a bit more of a problem, since an answer may seem okay but actually be harmful.
What if I'm asking a question about dealing with chatbots in an academic setting?
The question itself may not be auto-generated. However, if quoting the exact words that the chatbot used is important for your question, you may provide a brief quote from the chatbot.
What if I have a suggestion for improving this policy?
For the next week or so, we'll edit this policy based on discussion in the comments and/or other answers. After that, you should make a new meta post to propose any changes.
Update 31 May 2023
We are aware of this unpopular directive pushed on us from above, which will effectively make policies like this one unenforceable. This policy may need to be updated accordingly, stay tuned.