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
I started to write a whole thing about how "this might make sense if each community could turn it on or off," and explaining the difference in my eyes. However, my counter-example started out as a...
Answer
#1: Initial revision
I started to write a whole thing about how "this might make sense if each community could turn it on or off," and explaining the difference in my eyes. However, my counter-example started out as a programming question-and-answer, and I realized that... First, you often want to ask a technical question by loading information into it (logs, for example), but you don't want that mass of content to clutter the question to the point that nobody reads it. Likewise, a programming answer especially might come in two forms, the "this is the thing that you need to fix to get your presented code running" answer *and* the "here's your code rewritten to not only fix your problem but head off some other potential issues. Combine those cases with (in effect) spoiler warnings (presumably the originally envisioned use, when calling about puzzles) *and* content warnings when somebody needs to present information that some readers will want to skip, and details start to make a lot of sense across the board...assuming that implementing it - in a way that makes sense for users who aren't comfortable with "just mix Markdown and HTML - wouldn't take too much effort, of course.