[falcor84]

It's not an entirely different problem because the main method through which moderators are mean is in closing new questions as dupes. A more positive q&a community might "steel-man" the question and try to find what's different about it, but SO's culture leaned heavily towards essentially telling people "go away, you don't have anything new and worthwhile for us".

[Permit]

> It's not an entirely different problem because the main method through which moderators are mean is in closing new questions as dupes

This discussion needs a grounded definition of "toxic" then.

Elsewhere in this thread I see:

> I disagree with this. You can tell someone that a question is not appropriate for a community without being a jerk. Or you can tell them that there needs to be more information in a question without being a jerk. I do not think being mean is a prerequisite for successful curation of information.

So we're all speaking about different things it appears.

[zahlman]

> This discussion needs a grounded definition of "toxic" then.

When I wrote about the issue on MSE (https://meta.stackexchange.com/a/394952/173477) a couple years ago I explicitly called out that the terminology is not productive. It generally seems to describe dissatisfaction with the user experience that results from a failure to meet the user's expectations; but the entire reason for the conflict is that the user's expectations are not aligned with what the existing community seeks to provide.

And yes, the ambiguity you note has been spammed all over the Internet (everywhere Stack Overflow is discussed) the entire time. Some people are upset about how things are done; others consider what is done to be inherently problematic. And you can't even clearly communicate about this. For example, someone who writes "You can tell someone that a question is not appropriate for a community without being a jerk." might have in mind "don't point people at the policy document as if they should have known better, and don't give specific interpretation as if their reading comprehension is lacking"; but might also have in mind "point people at the policy document, and give specific interpretation, because otherwise there's no way for them to know". Or it might be "say something nice, but don't close the question because that sends the wrong message inherently" (this interpretation is fundamentally misguided and fundamentally misunderstands both the purpose and consequences of question closure).

And yes, every now and then, the person making the complaint actually encountered someone who said something unambiguously nasty. For those cases, there is a flagging system and a Code of Conduct. (But most Code of Conduct violations come from new users complaining when they find out that they aren't entitled to an open, answered question. And that's bad enough that many people don't comment to explain closures specifically to avoid de-anonymizing themselves.)

[zahlman]

1. They overwhelmingly are not moderators, and they are not doing moderation by closing questions. This is curation, and duplicate closures overwhelmingly are done by subject-matter experts: users with a gold badge in one or more of the tags originally applied to the question. The requirement for such a badge is based on answering questions:

> Earn at least 1000 total score for at least 200 non-community wiki answers in the $TAG tag. These users can single-handedly mark $TAG questions as duplicates and reopen them as needed.

So these are definitely not people averse to the idea of answering questions.

2. I can guarantee you that the overwhelming majority of these cases are not people trying to be "mean". Users are actively incentivized against closing duplicates, which has historically led to nowhere near enough duplicate questions being recognized and closed (although there have been many proposals to fix this). Dupe-hammering questions "to be mean" is considered abusive, and suspicion of it is grounds to go to the meta site and discuss the matter.

No, people close these questions because they genuinely believe the question is a duplicate, and genuinely believe they improve the site with this closure. It's important to understand that: a) people who ask a question are not entitled to a personalized answer; b) leaving duplicate questions open actively harms the site by allowing answers to get spread around, making it harder for the next person to find all the good ones; c) the Stack Overflow conception of duplication is not based on just what the OP understands or finds useful, but on what everyone else afterward will find useful.

For example, there are over a thousand duplicate links to https://stackoverflow.com/questions/45621722 , most of which is from my own effort — spending many consecutive days closing dozens of questions a day (and/or redirecting duplicate closures so that everything could point at a "canonical"). Yes, that's a question about how to indent Python code properly. I identified candidates for this from a search query and carefully reviewed each one, verifying the issue and sending other duplicates to more specific canonicals in many cases (such as https://stackoverflow.com/questions/10239668). And put considerable effort into improvements to questions and existing answers, writing my own answer, and adding links and guidelines for other curators so that they can choose more appropriate duplicate targets in some cases. I also looked at a wider search that probably had a fairly high false positive rate, but implies that there could be thousands more that I missed.

3. When your question is closed as a duplicate, you immediately get a link to an answer. You don't even need to wait for someone to write it! It's someone saying "here, I was able to find it for you, thanks perhaps to my familiarity with other people asking it".

4. Stack Overflow users really do "try to find what's different about" the question. It just... doesn't actually matter in a large majority of cases. "I need to do X with a tuple, not a list" — well, you do it the same way. "I need to Y the Xs" — well, it seems like you understand how to Y an X and the real problem is with finding the Xs; here's the existing Q&A about finding Xs; you shouldn't need someone else to explain how to feed that into your Y-the-things loop, or if you do, we can probably find a separate duplicate for that. Things like that happen constantly.

Sometimes a question shows up with multiple duplicates. This almost always falls into two patterns: the user is really asking multiple separate things (due to failing to try to break up a problem into logical steps) and each one is a duplicate; or the question is constantly asked but nobody knows a good version of the question, and gives multiple links to previous attempts out of frustration with constantly seeing it. (The latter is bad; someone is supposed to write the good version and send everything else there. But that typically requires behind-the-scenes coordination. Better would be if the first bad attempt got fixed, but you know.)

5. Closing a question is emphatically not about telling people to go away. The intended message (unless the question is off topic or the OP just made a typo or had a brainfart) is "please stay and fix this". However, it's perfectly reasonable that an explicit attempt to catalog and organize useful information treats redundant indices by pointing them at the same target rather than copies of the target. And questions are indices in the Q&A model.