My stackoverflow question was closed so here's a blog post about CoreWCF

I used to be very active on StackOverflow, it was a great platform.

After a while, I stopped having to post questions about "common frameworks", either because I could do with the official docs of because there was already a StackOverflow answer for my question.

What was becoming more common was that I would have a question similar to an existing unanswered one. Or that my question would never receive an answer (presumably because my questions were becoming more tricky/niche). So what I started doing was answering my own question (or answering those existing unanswered ones) after solving it on my own. Still, it was fine and I was contributing.

And for some reason, a few years ago my questions started being closed for no apparent reason other than "those who reviewed it have no clue and think that it is invalid". Many times they closed even though I had posted both the question and the answer at the same time (as a way to help others)! The first few times, I fought to get my question reopened and guess what? They all got a few tens of votes in the following year. Not so useless, eh?

Still, that toxic moderation hasn't changed. If anything, it has gotten worse. So I stopped contributing to StackOverflow entirely. If I find information there, that's great, if not, I won't go and add it once I find a solution for myself. I am usually better off opening an issue or discussion directly with the upstream project, bypassing StackOverflow's moderation.

I heard people mentioning that LLMs were hurting StackOverflow badly. I'm here to say that what pushed me away was the toxic moderation, not LLMs.

The moderators were elected. What should StackOverflow have done, held a vote of no confidence? Given them less power; make moderation more democratic?

In my own experience it's not often the elected moderators that are the problem, but those with a golden tag in a specific tag. They're far too eager to close questions because they're the ones culling through a tag often - and then close the question as they quickly think "oh, it's that again".

But it often isn't, they just didn't spend enough time to see nuance.

And neither do they see that even if _they_ understand that the question linked to is the same thing, there is no way the asker can understand what the similarity is from their knowledge point of view (or why the linked duplicate question is the same question).

How do you think they should have handled closing questions, if at all?

Why close questions? Is there a limit on storage space?

dang doesn't go and delete all the infinite failed submissions to HN, after all.

Should all 10,000 questions ( https://stackoverflow.com/questions/linked/218384?lq=1 ) that are duplicates of https://stackoverflow.com/questions/218384/what-is-a-nullpoi... be open and still allow people to try to answer each instance of the person's question?

Heh, I hadn't realized the infamous null pointer/reference question was that well cited. The most egregious cases in the Python tag only have about 3500 (https://stackoverflow.com/questions/20109391) and 1500 (https://stackoverflow.com/questions/1373164/) links respectively.

... Okay, I want to walk back something I said in some other comments here. There is definitely a class of SO questions that get closed as duplicates inappropriately. I tend to forget about the first of the questions because it's not generally a suitable dupe target when it's used: it's a meta question, explaining how to fix your question, rather than actually answering it. But, as you might infer, that means your question should still be closed - it lacks debugging details.

I fought against this trend on meta: https://meta.stackoverflow.com/questions/426205 . Unfortunately, there's another incentive misalignment here: dupe-hammering the question allows users with a gold badge to act more quickly on questions that don't meet site standards but are likely to attract a quick answer that interferes with keeping the site clean.

The second one... honestly probably isn't the best version of the question, but it's attracted good answers and become "canonical". The problem is that thinking in terms of "variable variables" isn't necessarily the right way to think about the problem (dynamically modifying namespaces; or rather, the fact that Python's namespaces are reflected as objects that can in most cases be modified meaningfully) - but it does map pretty well to how a beginner would typically think about the problem. It just tends to overlap with other reasonable questions in a messy way.

On Codidact, I've attempted to address the problem space more proactively, but I think I didn't complete the project I had in mind.