llm/5daab79e-f20f-476c-ab87-82c7ff678250/topic-2-0af97620-1362-47ba-a959-ec1bbce0859c-input.json
You are a comment summarizer. Given a topic and a list of comments tagged with that topic, write a single paragraph summarizing the key points and perspectives expressed in the comments.
TOPIC: Duplicate question closures
COMMENTS:
1. I don’t think there’s anything virtuous or non-virtuous about it. The internet is a big place and search engines aren’t optimized to produce results according to singular sites’ idiosyncrasies.
The obvious flaw in Stack Overflow’s bias toward closing new questions is that over time the best pages are also the oldest and most stale. They even locked questions with enough answers to prevent new content from being added, guaranteeing that they became stale.
Yet at the same time they allowed new questions to be asked and indexed by search engines, but didn’t allow new answers to that new content. So the freshest and most recent content was also the worst.
I don’t see this as a “Google bad” moment. It’s a failure of Stack Overflow in clinging to their oldest content and building rules that made all new posts frustrating and unhelpful.
2. I know the feeling of being happy not being the only one with that same problem (and that somebody bothered to actually ask on SO) and the crushing feeling that the question was closed as off topic (so no reason for me to ask) or marked as duplicate (referencing that is clearly not a duplicate and just showing that the mod took no effort to understand the question)
3. It's not about if it's "worthy of being asked", but mainly that many of us doubt the stories presented here without evidence. Time and time again examples are asked for in HN discussions about SO, but they're never presented.
One other thing often missed is that people answer these questions on their spare time to be nice. A closed question wouldn't necessarily have gotten any good answers anyways. And if you've ever taken part in moderating the review queue, you would've seen the insane amount of low-quality questions flowing in. I saw probably ten variants of "how to center my div" daily being closed as duplicates. The asker might be miffed about getting their question closed (but with a link to a solution..), but if you want to actually get answers to the high quality questions, the noise has to be filtered somehow.
Of course, SO is a bad fit for helping beginners figure out their syntax errors or how to apply a general solution to their specific issue. And you may not like SO for
4. The point here is you worked tech support so you were paid to answer user questions.
However the answerers on So are not paid. Why should tyhy waste their time on a user who has not shown they have put any effort in and asks a question that they have already answered several times before?
5. > The fundamental value proposition of SO is getting an answer to a question
I read an interview once with one of the founders of SO. They said the main value stackoverflow provided wasn't to the person who asked the question. It was for the person who googled it later and found the answer. This is why all the moderation pushes toward deleting duplicates of questions, and having a single accepted answer. They were primarily trying to make google searches more effective for the broader internet. Not provide a service for the question-asker or answerer.
Sad now though, since LLMs have eaten this pie.
6. > This is why all the moderation pushes toward deleting duplicates of questions, and having a single accepted answer.
Having duplicates of the question is precisely why people use LLMs instead of StackOverflow. The majority of all users lack the vocabulary to properly articulate their problems using the jargon of mathematicians and programmers. Prior to LLMs, my use case for StackOverflow was something like this:
30 minutes trying (and failing) to use the right search terms to articulate the problem (remember, there was no contextual understanding, so if you used a word with two meanings and one of those meanings was more popular, you’d have to omit it using the exclusion operator).
30 minutes reading through the threads I found (half of which will have been closed or answered by users who ignored some condition presented by the OP).
5 minutes on implementation.
2 minutes pounding my head on my desk because it shouldn’t have been that hard.
With an LLM, if the problem has been do
7. > Having duplicates of the question is precisely why people use LLMs instead of StackOverflow. The majority of all users lack the vocabulary to properly articulate their problems using the jargon of mathematicians and programmers.
Yes; so the idea is they fail to find the existing question, and ask it again, and get marked as a duplicate; and then everyone else with the same problem can search, possibly find the new duplicate version , and get automatically redirected to the main version with high quality answers.
8. Yes but that only works if the questions are identical . Often however they are merely similar, but closed as duplicates nonetheless.
9. No, that is completely wrong. It is exactly because the questions are not identical that the system works. That is what allows for multiple versions of a popular, important question to catch attention from search engines, and send everyone to the same, correct place.
Perhaps your objection is that, because the target question is not literally identical (for example, maybe a code sample has different variable names, or the setup has an irrelevant difference in the container type used for a collection, etc.) that the answers don't literally answer the new version of the question. That is completely missing the point . It's not a forum. The Q&A format is just the way that information is being presented. Fixing the issue in your, personal code is not, and never has been, the goal.
10. You are positing that only questions with cosmetic or extraneous differences are marked as duplicates.
That's not the case. As a maintainer of a popular project who has engaged with thousands of Qs on SO related to that project, I've seen many Qs marked as duplicate where the actual answer would be different in a non-trivial manner. When I look at who all moderated on those Qs, they are usually users who haven't contributed to that topic at SO.
11. > That's not the case.
Yes, it is. I have been active on both the main and meta sites for many years. I have seen so many of these complaints and they overwhelmingly boil down to that. And I have gotten so unbelievably stressed out on so many occasions trying to explain to people why their trivial objections are missing the point of the site completely.
> I've seen many Qs marked as duplicate where the actual answer would be different in a non-trivial manner.
Please feel free to cite specific examples. I'll be happy to explain policy.
> When I look at who all moderated on those Qs, they are usually users who haven't contributed to that topic at SO.
That is generally irrelevant.
12. > Please feel free to cite specific examples. I'll be happy to explain policy.
How do I search for Qs closed as duplicates with a certain tag?
13. "[tag] is:question duplicate:yes"
But if you had a personal experience, it will be easier to look within your questions on your profile page.
14. > But if you had a personal experience, it will be easier to look within your questions on your profile page.
I answer Qs on this topic, not post them.
----
Here's an example I found:
https://superuser.com/questions/1929615/
(the canonical q is about extracting as mono, the closed q is about muting one channel)
15. You appear to have linked the canonical, which has a few duplicates marked. All are asking about isolating one channel , as far as I can tell. This canonical is literally titled "ffmpeg: isolate one audio channel". One of them also asks about "downmixing" to mono after isolating the channel (which I guess means marking the audio format as mono so that that isolated channel will play on both speakers), but that is trivial. And you see the same basic techniques offered in the answers: to use `-map-channel` or the `pan` audio filter. The other one explicitly wants a panned result, i.e. still stereo but only on one side; the logic for this is clear from the explanation in the canonical answer.
The point is to show the technique, not to meet individual exact needs. Stack Overflow doesn't need separate "how do I get the second line of a file?" and "how do I get the third line of a file?" questions.
16. The dupe is what I linked.
The orig is https://superuser.com/questions/601972
The orig wants a mono output with one of the original channels as signal source. This involves downmixing i.e. rematrixing the audio.
The dupe want to just mute one of the channels, not repan it. One can't apply map_channel to do what the dupe wants.
One can use a couple of methods to achieve the dupe, including pan. But the syntax of pan needed for the dupe case is not the same as the orig, or deducible from it. They need to consult the docs (fortuitously, the dupe case is an illustrated example) or get a direct answer. The 'technique' shown in the orig is not intuitively adaptable to the dupe - one needs to know about the implicit muting that pan applies, which is not documented or evident in the orig answer. So it's not a duplicate of the source Q.
17. > The dupe is what I linked. The orig is
Ah, I don't actually have a SuperUser account, so it was automatically redirecting me.
> The 'technique' shown in the orig is not intuitively adaptable to the dupe
IDK, it looks to me like I could figure it out pretty easily from what's written there, and I'm not by any means an ffmpeg expert.
18. I do not remember any specific examples, but when I still used SO, I've come across many cases personally where a question closely matching a problem I had was closed as a duplicate of another question that asked about a related, but different problem and had an answer that was not appropriate for my problem and the supposedly duplicate question.
This significantly decreased the utility of clicking on SO links for me, to the point where I would avoid going to search results from SO first.
The comments here are teeming with others voicing similar experiences.
It is quite... something to read your response to this, which pretty much comes across as "nu-uh!", garnished with an appeal to "policy".
I think your SO-specific bubble is a little different from most other people's. I've no doubt that overwhelmingly, the dupes are dupes, but on the other hand, the false positives you're discounting are overwhelming the user experience.
19. > many cases personally where a question closely matching a problem I had was closed as a duplicate of another question that asked about a related, but different problem and had an answer that was not appropriate for my problem and the supposedly duplicate question.
Yes.
We consider that duplicate.
Because the point is whether the question is duplicate, not whether the problem is duplicate. The point is not to solve the problem, so it isn't interesting whether the question is "appropriate to" the problem. The point is to give you the information you need .
20. > Yes; so the idea is they fail to find the existing question, and ask it again, and get marked as a duplicate
Users would fail to find the existing question not because there was an abundance of poorly-worded questions, but because there was a dearth of questions asked using lay terminology that the user was likely to use.
Users were not searching for error codes but making naive preliminary searches like “XYZ doesn’t work” and then branching off from there. Having answers worded in a variety of ways allowed for greater odds that the user would find a question written the way he had worded his search.
Redirecting users to an older answer also just added pointless friction compared to allowing for the answer from the original question to be reposted on the duplicate question, in the exceedingly rare instances
I understand the motive behind wanting to exclude questions that are effectively just: “Do my work for me.” The issue is you have users actively telling you that the culling p
21. I think that's a great policy. I don't think anyone wants duplicate questions. The problem is moderation marking unrelated questions as duplicates.
I'd say 9/10 times I find a direct match for my question on SO it's been closed as offtopic with links to one or more questions that are only superficially similar.
There are other problems that they don't even try to address. If 10 people ask the same question, why does only the first person to ask it get to choose the answer? Then lots of "XY" questions where the original asker didn't actually have problem X so selects an answer for Y, leaving the original X unsolved, and now all the duplicates only have an answer for Y too.
22. > The problem is moderation marking unrelated questions as duplicates.
This problem isn't directly solvable (what counts as a "duplicate" is inherently subjective, and therefore mistakes/differences of opinion are inevitable).
I think a deeper problem is that once a question becomes closed (for any reason), it's unlikely that it'll ever be reopened. The factors behind this are social (askers interpret close votes as signals that they should give up), cultural (there's not much training/feedback/guidelines about what "duplicate" means for those with voting privileges), and technical (there's no first-class feature for askers to contest closure, and it takes just as many votes to reopen a question as it does to close it (with the same voter reputation requirement)).
23. > and technical (there's no first-class feature for askers to contest closure
It's not quite that bad: when the OP edits the question, there is a checkbox to assert that the edit resolves the reason for closure. Checking it off puts the question in a queue for reconsideration.
However, there's the social problem (with possibly a technical solution) that the queue is not as discoverable as it ought to be, and provides no real incentive; the queues generally are useful for curators who work well in a mode of "let's clean up problems of type X with site content today", but not for those (like myself) who work well in a mode of e.g. "let's polish the canonical for problem Y and try to search for and link unrecognized duplicates".
Given the imbalance in attention, I agree that reopening a question should have lesser requirements than closing it. But better yet would be if the questions that don't merit reopening, weren't opened in the first place. Then the emphasis could be on getting th
24. > The problem is moderation marking unrelated questions as duplicates.
The idea was, if there's an answer on the other question that solves your question, your question remains in existence as a signpost pointing to the other one without having to pollute and confuse by having a mixture of similar answers across both with different amounts of votes.
25. The disconnect here is that they built it this way, but still call it a question and answer site and give a lot of power over to the person who created the question. They get to mark an answer as the solution for themselves, even if the people coming from Google have another answer as the solution.
If they were to recreate the site and frame it as a symptom and issue site, which is what the interview described, that would yield many different choices on how to navigate the site, and it would do a lot better. In particular, what happens when two different issues have the same symptom. Right now, that question is closed as a duplicate. Under a symptom and issue site, it's obvious that both should stay as distinct issues.
26. Quite often, when my search returned a 'closed as duplicate' reply, I found the allegedly duplicate question did not accurately describe my problem, and the answers to it were often inferior, for my purposes, than those which had been given to my original question before the gate was closed.
27. If this were true, then treating any question as an X-Y problem shouldn't be allowed at all. I.e. answers should at least address the question as posed before/instead of proposing an alternative approach.
In reality the opposite is encouraged. For countless times, I've landed on questions with promising titles/search extracts, only to find irrelevant answers because people grabbed onto some detail in the question irrelevant to my case and provided X-Y answers.
This often also causes subsequent useful questions to be marked as dups even though they no longer contain that irrelevant detail. The appeal process is so unfriendly that most would not bother.
See also: https://news.ycombinator.com/item?id=36068243
28. Sad? No. A good LLM is vastly better than SO ever was. An LLM won't close your question for being off-topic in the opinion of some people but not others. It won't flame you for failing to phrase your question optimally, or argue about exactly which site it should have been posted on. It won't "close as duplicate" because a vaguely-similar question was asked 10 years ago in a completely-different context (and never really got a great answer back then).
Moreover, the LLM has access to all instances of similar problems, while a human can only read one SO page at a time.
The question of what will replace SO in future models, though, is a valid one. People don't realize what a massive advantage Google has over everyone else in that regard. So many site owners go out of their way to try to block OpenAI's crawlers, while simultaneously trying to attract Google's.
29. I think PP means it's more in the tone and passive-aggressive behavior ("closed as duplicate") than somebody explicitly articulating that.
It's a paradox of poor communication that you cannot prove with certainty that there is an intent behind it. There is always the argument that the receiver should have known better (and bother checking local news at Alpha Centauri).
30. There is nothing "passive-aggressive" about closing a question as a duplicate.
It is explicitly understood to be doing a favour to the OP: an already-existing answer to a common question is provided instantly .
31. I will say that I had questions erroneously closed as duplicates several times, but I always understood this as an honest mistake. I can see how the asker could find that frustrating and might feel attacked... but that's just normal friction of human interaction.
32. The person best qualified to assess the relevance of any previous answers is often the OP. Far too often, the already-existing answer is years old and either no longer the best answer, or doesn't actually address a major part of the question. Or it simply was never a very good answer to begin with.
What would be the harm in pointing out previous answers but leaving the question open to further contributions? If the previous answer really is adequate, it won't attract further responses. If it's not, well, now its shortcomings can be addressed.
Closing duplicates makes as much sense as aggressive deletionism on Wikipedia. It generally means that somebody missed their true calling on an HOA board somewhere.
33. > The person best qualified to assess the relevance of any previous answers is often the OP.
The purpose of having the answer there is not to solve the OP's problem . It is to have a question answered that contributes to the canon of work. This way, everyone can benefit from it.
> What would be the harm in pointing out previous answers but leaving the question open to further contributions?
Scattering the answers to functionally the same question across the site. This harms everyone else who wants an answer to that question, and is then subject to luck of the draw as to whether they find the actual consensus high-quality answer.
You might as well ask: what would be the harm in putting a comment in your code mentioning the existence of a function that serves your purpose, but then rewriting the code in-line instead of trying to figure out what the parameters should be for the function call?
> Closing duplicates makes as much sense as aggressive deletionism on Wikipedia.
This analo
34. Where in the process of "ask question" -> "closed as duplicate" are you interacting with another human?
35. > I disagree with most comments that the brusque moderation is the cause of SO's problems
The moderation was precisely the reason I stopped using stackoverflow and started looking for answers and asking questions elsewhere. It was nearly impossible to ask anything without someone replying "Why would you even want to do that, do <something completely different that does not solve my problem> instead!". Or someone claiming it's a duplicate and you should use that ancient answer from another question that 1) barely fits and doesnt solve my problem and 2) is so outdated, it's no longer useful.
Whenever I had to ask something, I had to add a justification as to why I have to do it that way and why previous posts do not solve the issue, and that took more space than the question itself.
I certainly won't miss SO.
36. To the extent that moderation ever prevented questions from getting answers, that was by closing them.
When a question gets closed before an answer comes in, the OP has nine days to fix it before it gets deleted automatically by the system.
The value proposition is getting an answer to a question that is useful to a reasonably broad audience . That very often means a question that someone else asked, the answer to which is useful to you. It is not getting an "answer" to a "question" where an individual dumps some code trying to figure out what's wrong.
37. And 99% of the other stuff, that wasn't just a code dump and "it doesn't work", was also closed.
38. > I disagree with most comments that the brusque moderation is the cause of SO's problems, though it certainly didn't help. SO has had poor moderation from the beginning.
Overwhelmingly, people consider the moderation poor because they expect to be able to come to the site and ask things that are well outside of the site's mission. (It's also common to attribute community actions to "moderators" who in reality have historically done hardly any of it; the site simply didn't scale like that. There have been tens of millions of questions, versus a couple dozen moderators.)
The kinds of questions that people are getting quick, accurate answers for from an LLM are, overwhelmingly, the sort of thing that SO never wanted. Generally because they are specific to the person asking: either that person's issue won't be relevant to other people, or the work hasn't been done to make it recognizable by others.
And then of course you have the duplicates. You would not believe the logic some people
39. It seems you deny each problem that everyone sees in SO. The fact is SO repulsed people, so there is a gap between your interpretation and reality.
> It is as though people think they are being insulted when they are immediately given a link to where they can get the necessary answer, by volunteers.
This, for example. Question can be marked as duplicate without an answer. In this case yes, it feels insulting because the other is asked in such a weird way, that no-one will find the old when they search for the new (for example after a library change) and marking it as duplicate of an unanswered answer if a guarantee that the next SEO user won’t see it.
40. > Question can be marked as duplicate without an answer.
No, they literally cannot. The only valid targets for closure are existing questions that have an upvoted or accepted answer. The system will not permit the closure (or vote to close) otherwise.
If you mean "without writing a direct answer to the new question first", that is the exact point of the system . Literally all you have to do is click the link and read the existing answers.
> it feels insulting because the other is asked in such a weird way, that no-one will find the old when they search for the new
Sure. But someone else knew about the old question, found it for you , and directly pointed you at it so that you could get an answer immediately . And did all of this for free .
And , by doing this, now everyone else who thinks of your phrasing for the question, will be immediately able to find the old question, without even having to wait for someone to recognize the duplicate.
41. I’m sure I’ve had the experience of being told it’s a duplicate, without resolving my problem.
In any case, you may be right, and yet if you search this thread for “horrible” and “obnoxious”, you’ll find dozens of occurrence. Maybe defining the rules of engagement so that the user is wrong every time doesn’t work.
42. >> Question can be marked as duplicate without an answer.
> No, they literally cannot.
You missed that people repeatedly closed question as duplicate when it was not a duplicate.
So it had answer, just to a different mildly related question.
LLM are having problems but they gaslight me in say 3% of cases, not 60% of cases like SO mods.
43. Please feel free to show examples.
44. > It is as though people think they are being insulted when they are immediately given a link to where they can get the necessary answer, by volunteers.
Multiple times my questions closed as duplicates of question that was answering a different question.
Even when I explicitly linked that QA in my question and described how it differs from mine.
45. > This manifested as the war of "closed, non-constructive" on SO. Some really good questions were killed this way because the moderators decided on their own that a question had to have a provable answer to avoid flame wars.
It's literally a Q&A site. Questions need actual answers, not just opinions or "this worked for me".
46. > This manifested as the war of "closed, non-constructive" on SO. Some really good questions were killed this way because the moderators decided on their own that a question had to have a provable answer to avoid flame wars.
Please point at some of these "really good" questions, if you saved any links. (I have privileges to see deleted questions; deletion is normally soft unless there's a legal requirement or something.) I'll be happy to explain why they are not actually what the site wanted and not compatible with the site's goals.
The idea that the question "should have provable answers" wasn't some invention of moderators or the community; it came directly from Atwood ( https://stackoverflow.blog/2011/01/17/real-questions-have-an... ).
> I lost that battle. You can argue taht questions like "should I use Javascript or Typescript?" don't belong on SO (as the moderators did). My position was that even though there's no definite answer, somebody can give you a list of strengths and
47. The example wasn't even finding a right answer so I don't see where you got that..
Searching questions/answers on SO can surface correct paths on situations where the LLMs will keep giving you variants of a few wrong solutions, kind of like the toxic duplicate closers.. Ironically, if SO pruned the history to remove all failures to match its community standards then it would have the same problem.
48. Not a big surprise once LLMs came along: stack overflow developed some pretty unpleasant traits over time. Everything from legitimate questions being closed for no good reason (or being labeled a duplicate even though they often weren’t), out of date answers that never get updated as tech changes, to a generally toxic and condescending culture amongst the top answerers. For all their flaws, LLMs are so much better.
49. The more experienced I got, the subtler my questions/answers. The few times I asked a question, I would start by saying "it may look similar to this, this and that questions, but it is not", only to see my question get closed as duplicate by moderators.
If the moderators are not competent to understand if your question is a duplicate or not, and close it as duplicate when in doubt, then it contributes to the toxic atmosphere, maybe?
50. I noticed a similar thing for Python 3 questions, closed as a duplicate of a Python 2 response. Why they weren't collated and treated as a living document is beyond me.
51. > Especially in places like StackOverflow where the people asking questions are often inexperienced.
Except that SO has a crystal clear policy that the answer to questions should be helpful for everybody reaching it through search, not only the person asking it. And that questions should never be asked twice.
So if by chance, after all this dance the person asking the question actually needs the answer to a different question, you'll just answer it with some completely unrelated information and that will the the mandatory correct answer for everybody that has the original problem for any reason.
52. Which is why LLMs are so much more useful than SO and likely always will be. LLMs do this even. Like trying to write my own queue by scratch and I ask an LLM for feedback I think it’s Gemini that often tells me Python’s deque is better. duh! That’s not the point. So I’ve gotten into the habit of prefacing a lot of my prompts with “this is just for practice” or things of that nature. It actually gets annoying but it’s 1,000x more annoying finding a question on SO that is exactly what you want to know but it’s closed and the replies are like “this isn’t the correct way to do this” or “what you actually want to do is Y”
53. The community is not "toxic". The community is overwhelmed by newcomers believing that they should be the ones who get to decide how the site works (more charitably: assuming that they should be able to use the site the same way as other sites, which are not actually at all the same and have entirely different goals).
I don't know why you put "duplicates" in quotation marks. Closing a duplicate question is doing the OP (and future searchers) a service, by directly associating the question with an existing answer.
54. > legitimate questions being closed for no good reason
They are closed for good reasons. People just have their own ideas about what the reasons should be. Those reasons make sense according to others' ideas about what they'd like Stack Overflow to be, but they are completely wrong for the site's actual goals and purposes. The close reasons are well documented ( https://meta.stackoverflow.com/questions/417476 ) and well considered, having been exhaustively discussed over many years.
> or being labeled a duplicate even though they often weren’t
I have seen so many people complain about this. It is vanishingly rare that I actually agree with them. In the large majority of cases it is comically obvious to me that the closure was correct. For example, there have been many complaints in the Python tag that were on the level of "why did you close my question as a duplicate of how to do X with a list? I clearly asked how to do it with a tuple!" (for values of X where you do it the same way
55. > "why did you close my question as a duplicate of how to do X with a list? I clearly asked how to do it with a tuple!" (for values of X where you do it the same way.)
This is a great example of a question that should not be closed as a duplicate. Lists are not tuples in Python, regardless of how similar potential answers may be.
56. They will no doubt blame this on AI, somehow (ChatGPT release: late 2022, decline start: mid 2020), instead of the toxicity of the community and the site's goals of being a knowledgebase instead of a QA site despite the design.
PS - This comment is closed as a [duplicate] of this comment: https://news.ycombinator.com/item?id=46482620
57. People overestimate the impact of toxicity on number of monthly questions. The initial growth was due to missing answers. After some time there is a saturation point where all basic questions are already answered and can be found via Google. If you ask them again they are marked as dups.
58. I wonder what is the role of moderating duplicate questions. More time passes - more existing data there is and less need for new questions. If you moderate duplicate questions, will they disappear from these charts? Is this decline actually logical?
2020 there was new CEO and moderator council was formed:
https://stackoverflow.blog/2020/01/21/scripting-the-future-o...
59. Ironically they could probably do some really useful deduplication/normalization/search across questions and answers using AI/embeddings today, if only they’d actually allowed people to ask the same questions infinite different ways, and treated the result of that as a giant knowledge graph.
I was into StackOverflow in the early 2010s but ultimately stopped being an active contributor because of the stupid moderation.
60. Actual analysts here that have looked at this graph like... a lot, so let me contextualize certain themes that tend to crop up from these:
- The reduction of questions over time is asymptomatic of SO. When you have a library of every question asked, at some point, you asked most of the easy questions. Have a novel question becomes hard.
- This graph is using the Posts table, not PostsWithDeleted. So, it only tells you of the questions that survived at this point in time, this [0] is the actual graph which while describes a curve that shows the same behavior, it's more "accurate" of the actual post creation.
- This is actually a Good Thing™. For years most of the questions went unanswered, non-voted, non-commented, just because there was too many questions happening all the time. So the general trend is not something that the SO community needs to do anything about. Almost 20% of every question asked is marked as duplicate. If people searched... better™ they wouldn't ask as many questi
61. I guess I'm the only one that was a fan of SO's moderation. I never got too deep into it (answered some TypeScript questions). But the intention to reduce duped questions made a lot of sense to me. I like the idea of a "living document" where energy is focused on updating and improving answers to old versions of the same question. As a user looking for answers it means I can worry less about finding some other variation of the same question that has a more useful answer
I understand some eggs got cracked along the way to making this omelette but overall I'd say about 90% of the time I clicked on a SO link I was rewarded with the answer I was looking for.
Just my two cents
62. The problem with duplicate questions is that they weren't duplicates at all, and mods weren't competent enough to tell a difference.
63. No, but it will show, as someone else already responded, that they don't understand SO systems and processes at all. The question they linked [0] was closed by the asker themselves. It's literally one of the comments [1] on the question. Most questions aren't even closed by moderators, not even by user voting, but by the askers themselves [2], which can be seen on the table as community user. The community user gets attributed of all automated actions and whenever the user agrees with closure of their own question [3]. (The same user also gets attributed of bunch of other stuff [4]
This shows that critics of Stack Overflow don't understand how Stack Overflow works and start assigning things that SO users see normal and expected to some kind of malice or cabal. Now, if you learned how it works, and how long it has been working this way, you will see that cases of abuses are not only rare, they usually get resolved once they are known.
[0]: https://stackoverflow.com/questions/32711321/
64. The linked answer seems like a valid guess for a relevant dupe. Like I said in my comment, "I understand a few eggs got cracked along the way to making this omelette" but I really don't think this was as widespread of a problem as people are making it out to be.
They also have Meta Stack Overflow to appeal if you think your question was unfairly marked as a dupe. From what I read, it seems that most mods back off readily
65. > From what I read, it seems that most mods back off readily
If a reasonable, policy-aware argument is presented, yes. In my experience, though, the large majority of requests are based in irrelevant differences, and OP often comes across and fundamentally opposed to the idea of marking duplicates at all.
66. That was not closed by a moderator. In fact, it was closed automatically by the system, when you agreed that the question was a duplicate. Because of my privilege level I can see that information in the close dialog:
> A community member has associated this post with a similar question. If you believe that the duplicate closure is incorrect, submit an edit to the question to clarify the difference and recommend the question be reopened.
> Closed 10 years ago by paradite, CommunityBot.
> (List of close voters is only viewable by users with the close/reopen votes privilege)
... Actually, your reputation should be sufficient to show you that, too.
Anyway, it seems to me that the linked duplicate does answer the question. You asked why the unit-less value "stopped working", which presumably means that it was interpreted by newer browsers as having a different unit from what you intended; the linked duplicate is asking for the rules that determine the implicit unit when none is specifi
67. If you had used the search feature you’d realize that many similar comments have already been posted on HN. Vote to close.
68. If only those who voted to close would bother to check whether the dup/close issue was ACTUALLY a duplicate. If only there were (substantial) penalties for incorrectly dup/closing. The vast majority of dup/closes seem to not actually be dup/closes. I really wish they would get rid of that feature. Would also prevent code rot (references to ancient versions of the software or compiler you're interested in that are no longer relevant, or solutions that have much easier fixes in modern versions of the software). Not missing StackOverflow in the least. It did not age well. (And the whole copyright thing was just toxically stupid).
69. Presumably over time said AI could figure out if your question had already been answered and in that case would just redirect you too the old thread instead.
70. SO in 2013 was a different world from the SO of the 2020's. In the latter world your post would have been moderator classified as 'duplicate' of some basic textbook copy/pasted method posted by a karma grinding CS student and closed.
71. I have around 2k points, not something to brag about, but probably more than most stackoverflow users. And I know what I am talking about given over a decade of experience in various tech stacks.
But it requires 3,000 points to be able to cast a vote to reopen a question, many of which incorrectly marked as duplicate.
I said to myself, let it die.
72. > many of which incorrectly marked as duplicate.
Please feel free to cite examples. I'll be happy to explain why I think they're duplicates, assuming I do (in my experience, well over 90% of the time I see this complaint, it's quite clear to me that the question is in fact a duplicate).
But more importantly, use the meta site if you think something has been done poorly. It's there for a reason.
73. > This (question being incorrectly closed) is a common complaint, and the situation has not changed for a very long time.
The problem is that people come and say "this question is incorrectly closed", but the question is correctly closed.
Yes, the complaints are common, here and in many other places. That doesn't make them correct. I have been involved in this process for years and what I see is a constant stream of people expecting the site to be something completely different from what it is (and designed and intended to be). People will ask, with a straight face, "why was my question that says 'What is the best...' in the title, closed as 'opinion-based'?" (it's bad enough that I ended up attempting my own explainer on the meta site). Or "how is my question a duplicate when actually I asked two questions in one and only one of them is a duplicate?" (n.b. the question is required to be focused in the first place, such that it doesn't clearly break down into two separate issues like
74. > Not sure why you are always posting the same regurgitated answer to the legitimate concerns here.
I have more reach here than blogging about it, unfortunately.
But, ironically, it also helps illustrate the point about duplicate questions.
> If the “goal” doesnt work, you have to change and fix the “goal” and not force people to “understand” it.
No, that's literally the opposite of how communities work. There is no "force"; there are only conditions on having your contributions welcomed. Having your question closed on Stack Overflow is no more "force" than having your PR rejected on GitHub. You aren't the one who gets to decide whether the goal is "working", because the site is not there to provide you a service of asking questions, any more than Wikipedia is there to provide you a service of sharing opinions on real-world phenomena.
There's no reason that the Stack Overflow community should give, or ever have given, a damn about "the site being in a death spiral". Because that i
75. As someone that spent a fair bit of time answering questions on StackOverflow, what stood out years ago was how much the same thing would be asked every day. Countless duplicates. That has all but ceased with LLMs taking all that volume. Honestly, I don't think that's a huge loss for the knowledge base.
The other thing I've noticed lately is a strong push to get non-programming questions off StackOverflow, and on to other sites like SuperUser, ServerFault, DevOps, etc.
Unfortunately, what's left is so small I don't think there's enough to sustain a community. Without questions to answer, contributors providing the answers disappear, leaving the few questions there often unanswered.
76. I joined Stackoverflow early on since it had a prevalence towards .NET and I’ve been working with Microsoft web technologies since the mid 90’s.
My SO account is coming up to 17 years old and I have nearly 15,000 points, 15 gold badges, including 11 famous questions and similar famous answer badges, also 100 silver and 150 bronze. I spent far much time on that site in the early days, but through it, I also thoroughly enjoyed helping others. I also started to publish articles on CodeProject and it kicked off my long tech blogging “career”, and I still enjoy writing and sharing knowledge with others.
I have visited the site maybe once a year since 2017. It got to the point that trying to post questions was intolerable, since they always got closed. At this point I have given up on it as a resource, even though it helped me tremendously to both learn (to answer questions) and solve challenging problems, and get help for edge cases, especially on niche topics. For me it is a part of my l
77. StackOverflow was a pub where programmers had fun while learning programming. The product of that fun was valuable.
Instead of cultivating the pub, the owners demanded that the visitors be safe, boring and obedient witers of value. This killed the pub and with it the business.
The most visible aspect was the duplicate close. Duplicate closes scare away fresh patrons, blocking precisely the path that old timers took when they joined. And duplicates allow anyone with a grudge to take revenge. After all, there are no new questions, and you will always find a duplicate if you want to.
To create a new Stack Overlflow, create a pub where programmers enjoy drinking a virtual beer, and the value will appear by itself.
78. Some commenters suggest it's not the moderation. I think it is the key problem, and the alternative communities were the accumulated effect. Bad questions and tough answer competition is part of it, but moderation was more important, I think. Because in the end what kept SO relevant was that people made their own questions on up to date topics.
Up until mid-2010s you could make a seriously vague question, and it would be answered, satisfactory or not. (2018 was when I made the last such question. YMMV) After that, almost everything, that hadn't snap-on code answer, was labelled as offtopic or duplicate, and closed, no matter what. (Couple of times I got very rude moderators' comments on the tickets.)
I think this lead some communities to avoid this moderator hell and start their own forums, where you could afford civilized discussion. Discourse is actually very handy for this (Ironically, it was made by the same devs that created SO). Forums of the earlier generation, have too many b
79. LLMs caused this decline. Stop denying that. You don't have to defend LLMs from any perceived blame. This is not a bad thing.
The steep decline in the early months of 2023 actually started with the release of ChatGPT, which is 2022-11-30, and its gradually widening availability to (and awareness of) the public from that date. The plot clearly shows that cliff.
The gentle decline since 2016 does not invalidate this. Were it not for LLMs, the site's post rate would now probably be at around 5000 posts/day, not 300.
LLMs are to "blame" for eating all the trivial questions that would have gotten some nearly copy-pasted answer by some eager reputation points collector, or closed as a duplicate, which nets nobody any rep.
Stack Overflow is not a site for socializing . Do not mistake it for reddit. The "karma" does not mean "I hate you", it means "you haven't put the absolute minimum conceivable amount of effort into your question". This includes at least googling the question before you
80. Here’s how SO could still be useful in the LLM era:
User asks a question, llm provides an immediate answer/reply on the forum. But real people can still jump in to the conversation to add additional insights and correct mistakes.
If you’re a user that asks a duplicate question, it’ll just direct you to the good conversation that already happened.
A symbiosis of immediate usually-good-enough llm answers PLUS human generated content that dives deeper and provides reassurances in correctness
81. For this occasion, I just logged in to my SO profile; I've been a member for 9 years now.
To me, back when I started out learning web dev, as a junior with no experience and barely knowing anything, SO seemed like a paradise for programmers. I could go on there and get unblocked for the complex (but trivial for experts) issues I was facing. Most of the questions I initially posted, which were either closed as duplicates or "not good enough," really did me a lot of discouragement. I wasn't learning anything by being told, "You did it wrong, but we're also not telling you how you could do it better." I agree with the first part; I probably sucked at writing good questions and searching properly. I think it's just a part of the process to make mistakes but SO did not make it better for juniors, at least on the part of giving proper guidance to those who "sucked".
82. It's unfortunate that SO hasn't found a way to leverage LLMs. Lots of questions benefit from some initial search, which is hard enough that moderators likely felt frustrated with actual duplicates, or close enough duplicates, and LLMs seem able to assist. However I hope we don't lose the rare gem answers that SO also had, those expert responses that share not just a programming solution but deeper insight.
83. What if we filter out all the questions closed as dupes, off topic, etc?
84. Signs of over-moderation and increasing toxicity on Stack Overflow became particularly evident around 2016, as reflected by the visible plateau in activity.
Many legitimate questions were closed as duplicates or marked off-topic despite being neither. Numerous high-quality answers were heavily edited to sound more "neutral", often diluting their practical value and original intent.
Some high-profile users (with reputation scores > 10,000) were reportedly incentivized by commercial employers to systematically target and downvote or flag answers that favored competing products. As a result, answers from genuine users that recommended commercial solutions based on personal experience were frequently removed altogether.
Additionally, the platform suffers from a lack of centralized authentication: each Stack Exchange subdomain still operates with its own isolated login system, which creates unnecessary friction and discourages broader user participation.
85. I fairly recently tried to ask a question on SO because the LLMs did not work for that domain. I’m no beginner to SO, having some 13k points from many questions and answers. I made, in my opinion, a good question, referenced my previous attempts, clearly stating my problem and what I tried to do. Almost immediately after posting I got downvoted, no comments, a close- suggestions etc. A similar thing happened the last two times I tried this too. I’m not sure what is going on over there now, but whatever that site was many years ago, it isn’t any more. It’s s shame, because it was such a great thing, but now I am disincentivized to use it because I lose points each time I tip my toes back in.
86. >This post was not virtue signaling enough and therefore closed as duplicate.
SO had the greatest minds but the shitiest moderation
Write a concise, engaging paragraph (3-5 sentences) that captures the main ideas, notable perspectives, and overall sentiment of these comments regarding the topic. Focus on the most interesting and representative viewpoints. Do not use bullet points or lists - write flowing prose.
Duplicate question closures
86