llm/5daab79e-f20f-476c-ab87-82c7ff678250/batch-0-8603506c-f513-4f1a-aee2-38dd24090630-input.json
You are a comment classifier. Given a list of topics and a batch of comments, assign each comment to up to 3 of the most relevant topics.
TOPICS (use these 1-based indices):
1. Toxic moderation culture
2. LLMs replacing Stack Overflow
3. Duplicate question closures
4. Community hostility toward newcomers
5. Question quality standards
6. Knowledge base vs help forum debate
7. Future of LLM training data
8. Reddit and Discord as alternatives
9. Gamification and reputation systems
10. Outdated answers problem
11. SO sale to private equity
12. Google search integration decline
13. Expert knowledge preservation
14. GitHub Discussions adoption
15. Elitist gatekeeping behavior
16. Human interaction loss
17. Question saturation theory
18. Moderator power dynamics
19. AI-generated content concerns
20. Community decline timeline
COMMENTS TO CLASSIFY:
[
{
"id": "46483491",
"text": "Some comments:\n\n- This is a really remarkable graph. I just didn't realize how thoroughly it was over for SO. It stuns me as much as when Encyclopædia Britannica stopped selling print versions a mere 9 years after the publication of Wikipedia, but at an even faster timescale.\n\n- 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. The fundamental value proposition of SO is getting an answer to a question; if you can the same answer faster, you don't need SO. I suspect that the gradual decline, beginning around 2016, is due to growth in a number of other sources of answers. Reddit is kind of a dark horse here, as I began seeing answers on Google to more modern technical questions link to a Reddit thread frequently along with SO from 2016 onwards. I also suspect Discord played a part, though this is harder to gauge; I certainly got a number of answers to questions for, e.g."
}
,
{
"id": "46484235",
"text": "> 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.\n\nI was an early SO user and I don’t agree with this.\n\nThe moderation was always there, but from my perspective it wasn’t until the site really pushed into branching out and expanding Stack Exchange across many topics to become a Quora style competitor that the moderation started taking on a life of its own. Stack Overflow moderator drama felt constant in the later 2010s with endless weird drama spilling across Twitter, Reddit, and the moderator’s personal blogs. That’s about the same time period where it felt like the moderation team was more interested in finding reasons to exercise their moderation power than in maintaining an interesting website.\n\nSince about 2020 every time I click a Stack Overflow link I estimate there’s a 50/50 chance that the question I clicked on would be marked as off topic or closed or somet"
}
,
{
"id": "46485256",
"text": "There was definitely a bit of Pournelle's Iron Law of Bureaucracy [0] at work. I worked there during a lot of the drama you allude to, and... It sucked, for everyone. But also...\n\nFor most of SO's history, the vast majority of visitors (and this questions, answers) came in via Google. Not \"search engines\"; Google. This was pretty much baked in right at the start, and it effectively served as the site's primary user interface for years. And it worked. It worked pretty well! Until it didn't.\n\nAt some point, Google started surfacing fewer \"tried and true\" Q&A examples and more unanswered, poorly-answered or moderated examples. This broke the fundamental assumption that sat behind SO's moderation - that curating a smaller set of posts was preferable to encouraging more, and newer. Suddenly, Google wasn't a very good UI for SO anymore.\n\n...and SO didn't really have a fallback. Heck, for a while during this period they actually stopped showing questions on their homepage unless you were alre"
}
,
{
"id": "46490353",
"text": "> the core assumption remained that there was a never-ending spring of new people feeding the thing.\n\nHi Shog, hope you're doing well! Just thought this bit was insightful; I can fully believe this was the idea and the motivating factor for a lot of the decisions made seemingly in a vacuum (from the outside).\n\nHow much do you think Area51 and the push for the SE network rather than sticking with the Big Three affected things? I always got the impression that they tried to scale into places that ultimately attracted too much noise and overestimated the willingness of (community) moderators to effectively work for free for them to take on the wave of less technical/principled users."
}
,
{
"id": "46493272",
"text": "There was some of that for sure; sites that were all but designed to be attractive nuisances and took near-heroic efforts to moderate at all, with little chance of not causing a lot of drama.\n\nOTOH, topic-specific sites like Mathematics, MathOverflow, Physics, even small ones like Home Improvement or Seasoned Advice... Managed to collect a lot of good stuff: common niche questions with good answers that have a good chance at staying relevant for a long time to come.\n\nIn a sane world, a few relevant ads on these sites would be enough to fund them for decades. But that appears to be another area where Google kinda shit the bed."
}
,
{
"id": "46485368",
"text": "Oh, hey, Shog, good to see you doing well. It was a heck of a ride, hmm?"
}
,
{
"id": "46493207",
"text": "Yes indeed! Glad to see you over on Codidact; I suspect small, bespoke q&a will be the future of the form, at least after Facebook implodes."
}
,
{
"id": "46493829",
"text": "Believe me, I'm full of vision (and hope). But it's hard to write stuff when there's so much to write that I can't find a natural starting point, and when the (lack-of-)network effects are so brutal."
}
,
{
"id": "46486402",
"text": "Best answer so far, too bad way down here."
}
,
{
"id": "46488691",
"text": "It still seems a bit too simplistic… no one imagined that Google could behave less than 100% virtuously in the future? Really?"
}
,
{
"id": "46490281",
"text": "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.\n\nThe 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.\n\nYet 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.\n\nI 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."
}
,
{
"id": "46494198",
"text": "Agreed, think we're getting warmer."
}
,
{
"id": "46490200",
"text": "It worked that way for its first ten plus years. Why would it change? Why/How could you plan for an unknown future. Personally I’m horrible at predicting the future, so I don’t blame them."
}
,
{
"id": "46486534",
"text": "Lots of moderation issues are also UI issues.\n\nI suspect it’s the same issue for whatever is the “meta” in a competitive video game.\n\nOptimization based on the available affordances ?"
}
,
{
"id": "46490474",
"text": "I swear that about 3 of your replies look like LLM content or at best \"LLM-massaged\" messages :-("
}
,
{
"id": "46493179",
"text": "I was writing like a robot before robots could write, dammit!"
}
,
{
"id": "46488686",
"text": "Shog9, excellent comment and very apt. I have to point out that you were also part of the toxicity and bad tone. You very much were part of the problem. Moderation and staff were very much the downfall."
}
,
{
"id": "46489177",
"text": "Shog9 was probably the best person on staff in terms of awareness of the moderation problems and ability to come up with solutions.\n\nUnfortunately, the company abruptly stopped investing in the Q&A platform in ~2015 or so and shifted their development effort into monetization attempts like Jobs, Teams, Docs, Teams (again), etc. -- right around the time the moderation system started to run into serious scaling problems. There were plans, created by Shog and the rest of the community team, for sweeping overhauls to the moderation systems attempting to fix the problems, but they got shelved as the Q&A site was put in maintenance mode.\n\nIt's definitely true that staff is to blame for the site's problems, but not Shog or any of the employees whose usernames you'd recognize as people who actually spent time in the community. Blame the managers who weren't users of the site, decided it wasn't important to the business, and ignored the problems."
}
,
{
"id": "46489401",
"text": "Blame the managers who weren't users of the site, decided it wasn't important to the business, and ignored the problems.\n\nThis always cracks me up. I've seen it so many times, and so many books cover this...\n\nClassic statement is \"never take your eye off the ball\".\n\nSure, you need to plan ahead. You need to move down a path. But take your eye off of today, and you won't get to tomorrow.\n\nMaybe they'll SCO it, and spend the next 10 years suing everyone and their LLM dog.\n\nYou know, I wonder how the board and execs made out suing Linux related... things. End users were threatened too, compelled to pay...\n\nSO could be spun off into a neat tiger, nipping at everyone's toes."
}
,
{
"id": "46490623",
"text": "But was “today “ that profitable? Stack overflow always struck me as a great public good and a poor way to make money. If the current business makes very little money, it may not be worth the work."
}
,
{
"id": "46489319",
"text": "His tone was extremely passive aggressive and rude. I don’t think he made the site better - he contributed to the downfall"
}
,
{
"id": "46493159",
"text": "This sounds plausible - I grew up in the Midwestern US, and thus \"vaguely passive-aggressive\" is pretty much my native language. The hardest part of the job for me was remembering to communicate in an overtly aggressive manner when necessary, developing a habit of drawing a sharp line between \"this is a debate\" and \"this is how it is.\"\n\nSometimes I put that line in the wrong place.\n\nThat said... I can't take credit for any major change in direction (or lack thereof) at SO. To the extent that SO succeeded, it did so because it collectively followed through on its mission while that was still something folks valued; to the extent that it has declined, it is because that mission is no longer valued. Plenty of other spaces with very different people, policies, general vibes... Have followed the same trajectory, both before SO and especially over the past few years.\n\nWith the benefits of hindsight, probably the only thing SO could have done that would have made a significant difference woul"
}
,
{
"id": "46489894",
"text": "Can you provide an example? The only rude Shog9 posts I can think of were aimed at people abusing the system: known, persistent troublemakers, or overzealous curators exhibiting the kinds of behaviours that people in this thread would criticise, probably far more rudely than Shog ever did."
}
,
{
"id": "46485245",
"text": "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)"
}
,
{
"id": "46488038",
"text": "The moderation definitely got kind of nasty in the last 5 years or so. To the point where you would feel unwelcome for asking a question you had already researched, and felt was perfectly sound to ask. However, that didn't stop millions of people from asking questions every day , it just felt kinda shitty to those of us who spent more time answering, when we actually needed to ask one on a topic we were lacking in. (Speaking as someone who never moderated).\n\nMy feeling was always that the super mods were people who had too much time on their hands... and the site would've been better without them (speaking in the past tense, now). But I don't think that's what killed it. LLMs scraping all its content and recycling it into bite-sized Gemini or GPT answers - that's what killed it."
}
,
{
"id": "46485838",
"text": "I asked a question for the first time mid last year. It was a question about \"default\" sizes in HTML layout calculations, with lots of research and links to relevant parts of the spec.\n\nIt was immediately closed as off topic, and there were a bunch of extremely vitriolic comments offended that I'd ask such a question on SO. It was briefly reopened weeks (?) later and then I guess closed again and now is deleted, so you can't even view the question any more.\n\nI'd long heard of abusive moderation but... experiencing it first hand is something else. Anecdote of one, but I know I'm never going to ask there again.\n\nIn case anyone's wondering, I ended up asking on the WhatWG or W3C or something github project (via an issue?). The TLDR was rather eye opening, that basically the spec only codifies points of contention for browsers and old behaviors are generally undocumented. With some pointers I figured out the default size behavior through code diving, and it was complex (as in, hard to use)"
}
,
{
"id": "46494433",
"text": "its not just you, I saw this happen to others' posts many times and it happened to me several times\n\nI gave up on Stack Overflow when my jobs started requiring me to use Terraform and suddenly every time I posted a well researched and well formed question about Terraform, it would immediately get flagged and closed with responses that \"Terraform is not programming and thus questions about Terraform should not be posted on Stack Overflow\", which was insane to me because Stack Overflow has a \"terraform\" tag and category. If you visit it, you will see tons of users trying to post valid questions only to have the mods shut them down angrily."
}
,
{
"id": "46494516",
"text": "Yeah. You're not a real programmer. It's just terraform. You're a stupids and we're smaht, and you should go off into your little corner and cry while we jerk each other off about how smart we are.\n\nGee, I wonder why people don't want to use the site?"
}
,
{
"id": "46486173",
"text": "Questions are never really deleted , post a link so people with enough reputation may have a look and maybe resurrect it if the question is really good."
}
,
{
"id": "46486270",
"text": "Why would anyone with an ounce of self-respect try to beg an stranger with enough internet point to look if their question is worthy of being asked? Do you not realize how the proposal must sound to someone who is not already in the SO in-group?"
}
,
{
"id": "46489015",
"text": "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.\n\nOne 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.\n\nOf 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"
}
,
{
"id": "46490477",
"text": "> Time and time again examples are asked for in HN discussions about SO, but they're never presented.\n\nHaving your SO question closed as off-topic or already answered isn’t believable to you? Just Google with site:StackOverflow.com and you won’t have to click through many results to find something closed.\n\nSpending all of the time to log back into the site and try to find the closed question just to post it to HN to have more people try to nit-pick it again hardly sounds attractive.\n\n> Of course, SO is a bad fit for helping beginners\n\nThe entire point of the story above was that it wasn’t a beginner question."
}
,
{
"id": "46491851",
"text": "> Having your SO question closed as off-topic or already answered isn’t believable to you?\n\nIt is believable. But it being a problem I don't see. If it's off-topic, that's sad for you but no reason to feel angry or it being \"hostile\" or something. It's just off-topic. Same if I started posting lots of local news from my city to HN. It's simply just off-topic and not what the site should contain. If it's already answered, being pointed to that answer by someone spending the time to digging it up is also not rude. Sure, you may feel bad because you feel someone \"reprimanded\" you or something. But that's on you."
}
,
{
"id": "46494509",
"text": "Why do you continue to ask for examples if you're just going to downplay them or explain them away like you did here?"
}
,
{
"id": "46490073",
"text": "> Of course, SO is a bad fit for helping beginners\n\nThis is the takeaway for myself and so many who have contributed to SO over the years, both questions and answers.\n\nSelf-reflection as to why a service has become both redundant and a joke is hard, and had SO started in 2019 maybe they'd have relevance. I'm not sure I see what value they bring now or moving forward."
}
,
{
"id": "46490241",
"text": "Thinking they didn't keep up with the times or that they should've made changes is perfectly fine. It's the vitriol in some of the comments here I really can't stand.\n\nAs for me, I also don't answer much anymore. But not sure if it's due to the community or frankly because most low hanging fruits are gone. Still sometimes visit, though. Even for thing's an LLM can answer, because finding it on SO takes me 2 seconds but waiting for the LLM to write a novella about the wrong thing often takes longer."
}
,
{
"id": "46490399",
"text": "I encourage you to recognize the statements you see as vitriol instead as brand markers as to how SO is known in the world. It's not a small set of folks who feel as if they were treated unfairly first."
}
,
{
"id": "46490648",
"text": "If it's so many, surely someone should be able to provide some example of them being treated unfairly soon! But seriously, I'm fine with people not liking SO. I just don't think the discourse on HN around it is very fruitful and mostly emotional. SO have clearly done something wrong to get that kind of widespread reputation, but I'm also allowed to be disappointed in how it's being discussed."
}
,
{
"id": "46494495",
"text": "You may think you're making some kind of point by repeatedly asking for examples of vitriol on SO, but all it shows is that you haven't looked, or haven't sincerely reflected on what you saw from the perspective of a regular user."
}
,
{
"id": "46490865",
"text": "I think you are seeing emotional response is because SO has really fucked with people’s emotions, it is by far the most toxic place for SWEs to have ever existed and nothing is close 100th to it. expecting a non-emotional responses from SWEs about SO is asking too much (for most)"
}
,
{
"id": "46486694",
"text": "Hm… as the person was new to SO it’s very possible they don’t understand what a good question looks like and I thought it may be helpful to give feedback on what may have gone wrong… but if you see that as “begging” and you don’t think you need any feedback, you have it all sorted out after all, then yeah it’s a waste of everyone’s time."
}
,
{
"id": "46487181",
"text": "Thing is, if that's how you are greeted at stackoverflow, then you'll go elsewhere where you're not treated like an idiot. Stackoverflow's decline was inevitable, even without LLMs."
}
,
{
"id": "46487353",
"text": "And thus SO dies as people will go somewhere they can actually get their question answered."
}
,
{
"id": "46487127",
"text": "This comment sums up everything wrong with Stack Overflow.\n\nI strongly suggest you re-read your comments here and self-reflect."
}
,
{
"id": "46488724",
"text": "Right? It's a perfect example of the problem.\n\nIn college, I worked tech support. My approach was to treat users as people. To see all questions as legitimate, and any knowledge differential on my part as a) the whole point of tech support, and b) an opportunity to help.\n\nBut there were some people who used any differential in knowledge or power as an opportunity to feel superior. And often, to act that way. To think of users as a problem and an interruption, even though they were the only reason we were getting paid.\n\nI've been refusing to contribute to SO for so long that I can't even remember the details. But I still recall the feeling I got from their dismissive jackassery. Having their content ripped off by LLMs is the final blow, but they have richly earned their fate."
}
,
{
"id": "46494136",
"text": "When I worked technical support in college I often worked nights and weekends (long uninterrupted times to work on homework or play games) ... there was a person who would call and ask non-computer questions. They were potentially legitimate questions - \"what cheese should I use for macaroni and cheese?\" Sometimes they just wanted to talk.\n\nNot every text area that you can type a question in is appropriate for asking questions. Not every phone number you can call is the right one for asking random questions. Not every site is set up for being able to cater to particular problems or even particular formats for problems that are otherwise appropriate and legitimate.\n\n... I mean... we don't see coding questions here on HN because this site is not one that is designed for it despite many of the people reading and commenting here being quite capable of answering such questions.\n\nStack Overflow was set up with philosophy of website design that was attempting to not fall into the same pitfall"
}
,
{
"id": "46490504",
"text": "The point here is you worked tech support so you were paid to answer user questions.\n\nHowever 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?"
}
,
{
"id": "46494476",
"text": "> 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?\n\nThis is kind of a weird sentiment to put forth, because other sites namely Quora actually do pay their Answerer's. An acquintance of mine was at one time a top \"Question Answerer\" on Quora and got some kind of compensation for their work.\n\nSo this is not the Question-Asker's problem. This is the problem of Stack Overflow and the people answering the questions."
}
,
{
"id": "46493567",
"text": "Nobody, least of all me, is saying people should work for free. But not being paid to do something you don't want to do is a reason to go do something else, not hang around and be a hostile, superior dick about it, alienating the users."
}
,
{
"id": "46491682",
"text": "I blame the Internet culture of the late 90s early 2000s. Referring to your customers as Lusers and dismissing their \"dumb\" questions was all the rage amongst a group of nerds who had their first opportunity to be the bully."
}
]
Return ONLY a JSON array with this exact structure (no other text):
[
{
"id": "comment_id_1",
"topics": [
1,
3,
5
]
}
,
{
"id": "comment_id_2",
"topics": [
2
]
}
,
...
]
Rules:
- Each comment can have 0 to 3 topics
- Use 1-based topic indices
- Only assign topics that are genuinely relevant to the comment
- If no topics match, use an empty array:
{
"id": "...",
"topics": []
}
50