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.

Comments on Should we remove closed questions from the question list?

Parent

Should we remove closed questions from the question list?

+7
−1

Should we exclude closed questions from the question list?

Closed questions (and their answers) would still be linked on the owners' profiles, would be included in search results, and would produce the usual notifications from activity on them. This change would only be to get them out of the main view.

If a question is closed and being worked on (to fix the issues), this lets the author do so out of view. If the issues that caused it to be closed are addressed and the question is reopened, it returns to view. Meanwhile, it's not "in the way" and likely not attracting more downvotes. ("I know it's broken; you don't need to keep telling me!", the author might be thinking in response to more and more downvotes while trying to edit.)

If a question is closed and not being worked on to fix the issues, then it's unlikely to be helpful for it to be listed. While it sometimes happens that a third party sees a question, knows what the author was trying to ask, and fixes it (I've done this), it's uncommon. I can think of a few options we might consider to mitigate this: search by closure status, a filter, a user preference, show to people with the Curate ability. I'd like to understand how big a concern it is first and then we can decide what to do about it.

This question is not meant to preclude other housekeeping automation. I'm asking if withdrawing closed questions from the main public view would be a useful first step.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

This suggestion is similar (3 comments)
Post
+7
−2

Closed questions should remain visible to the general users (unregistered and first-time users is a different issue). Reasons:

  1. It avoids site policy being enacted "behind closed doors".
  2. It illustrates what the norms are. Seeing what questions got closed can be useful, especially for new users, to understand what's allowed and what's not.
  3. It allows discussion of what should be closed. If questions get closed and then silently disappear, most users won't have the chance to argue on meta that the question shouldn't have been closed.
  4. If you're worried about your closed question accumulating more downvotes, too bad. That's a consequence of writing a bad question. You can always fix it or delete it.
  5. It allows others to suggest changes in comments.

Response to comments

What do you think about the suggestion in this answer of having a toggle?

I don't have a problem with a toggle, since that's something individual users choose to do. The default should be to see closed questions. If that bothers someone enough, then they can shut that off is they wish. They should, though, first see what it's like when seeing everything. That way they should have a better idea of what they're not going to see, and what the consequences of that might be.

This has to weighed against the first site impression of new users

Right, which is why I said in the first sentence "unregistered and first-time users is a different issue".

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

2 comment threads

New user experience (2 comments)
toggle? (1 comment)
New user experience
Lundin‭ wrote almost 3 years ago

This has to weighed against the first site impression of new users, which was why this was proposed to begin with. If they see nothing but closed and down-voted questions, then that suggests that the content of the community overall is of low quality. In particular this might scare away new users who happen to also be domain experts.

Lundin‭ wrote almost 3 years ago · edited almost 3 years ago

Also, we know from experience of SE that educating new users by providing optional reading material regarding how to use the site simply doesn't work - nobody reads it. I would assume that this is not only true for help files but also closed posts, it's wishful thinking that new users would go around and study closed posts before posting a question of their own. Some do of course, the most sensible new users "silently lurk" at the site for a while before posting, but those users are rarely problematic and often have enough common sense to tell what kind of questions that may be considered problematic. These users aren't the problem. The problem is those who don't read anything about the site before posting, they just dive right in and post bad or off-topic questions. The worst kind are those who don't even stop to reflect why their previous question was closed but keep posting similar questions. The site needs ways to slow such users down and either educate them or police them.