Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

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

40%
+0 −1
Q&A Should details tags work in comments?

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...

posted 6mo ago by John C‭

Answer
#1: Initial revision by user avatar John C‭ · 2024-06-15T21:49:11Z (6 months ago)
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.