-116

Update May 6th, 2025

After reviewing the feedback on the comment changes, specifically regarding the plan to disable the "No longer needed" (NLN) flag during this experiment, we discussed internally and decided to follow the suggestion from TylerH & Starship. Instead of removing the flag, we will rename it to "Not needed" for the duration of the experiment. We may also slightly revise the descriptive subtext to better align with both existing use cases and the experiment's goals.

Additionally, we are exploring adding an optional text field when this flag is used during the experiment. This would allow users to provide brief context for their flag, which could offer valuable feedback for the experiment and offer more context for moderators on those types of comment flags. We will provide further details as the experiment launch approaches.


TL;DR: Soon we will be launching an experiment on Stack Overflow to enhance the quality and usefulness of comments. Our goal is to make them more suitable for follow-up questions and conversations surrounding specific content, and shifting away from the notion that they are strictly temporary or suggesting post improvements. Based on learnings and feedback, we will test features such as threaded replies and code formatting, and introduce an updated UI. This is a temporary test to gather data and feedback before deciding on permanent changes. Should this experiment be successful, these changes will be released network-wide.

We're launching a new set of experiments on Stack Exchange, beginning with Stack Overflow, focused on evolving the way comments function. This experiment represents a significant shift from the long-standing philosophy that comments are ephemeral and intended solely for post improvement or clarification. We recognize that this change may be unpopular to some and welcomed by others. To be very clear, the primary purpose of this experiment is to discover ways to increase meaningful engagement across the entire network.

We aim to develop an experience that welcomes comments that are on- topic, professional, and beneficial to users. Since commenting on the internet is a well-understood feature, we’re also exploring how improvements to our commenting UI, similar to how commenting is commonly experienced on the internet, will affect engagement on Stack Overflow.

Why This Change? Learnings from Past Experiments

These experiments stem directly from what we learned in our recent experiments focused on comments and the 'Discussions' feature.

Need for Follow-Up Questions

A key takeaway from our previous experiment was that users want to ask specific, technical follow-up questions related to existing questions and answers. Our analysis showed common needs such as asking direct follow-ups, clarifying answers, sharing variations, or explaining why an answer didn't work for them (and why). These attempts often included code blocks or images, which current comments do not support.

Visibility Challenges

While we experimented with directing users to Discussions for follow-ups, we found it wasn't the ideal solution for these specific, contextual questions. This was partly due to lower visibility compared to the original Q&A page. Users also expressed confusion about the distinct purposes of comments, Discussions, and Q&A.

Current Limitations

The existing comment experience with its character limits and formatting restrictions creates friction for users who need help. It either requires users to create multiple comments or to demonstrate their own code in awkward spaces. Rather than trying to find a way to fit Discussions into this need, we are shifting our primary focus to better facilitate follow-up questions directly within the context of the Q&A posts as comments, where many users already try to engage in follow-up questions.

The Proposed Experiment on Stack Overflow

We plan to run a series of rapid tests that build on each other on Stack Overflow to explore ways to make comments more suitable for these types of exchanges. Much of this will be UI updates, such as:

  • A general update to the look and feel of comments, with an updated user card
  • Comment threading for easier to follow conversations
  • A full editor for commenting that supports images and code blocks
  • Some improved commenting moderator tools. We expect that we will begin work on this towards the end of our experiments, once we have a better idea of what requirements the experiments have surfaced.

To inform our strategy, we conducted interviews with developers who are regular users of Stack Overflow. These interviews affirmed the findings in our previous commenting experiment that users are encountering situations where they need to ask follow-up questions or need to clarify what is in an existing answer. Those individuals felt that our approach to enhancing the commenting experience could provide better context and encourage the back and forth needed to fully solve problems.

Please be aware that the screenshot below is a preliminary view and the final version may differ. The comments are expanded here just for demonstration purposes. Default would be to have them collapsed.

We intend to act fast, potentially testing variations on a weekly basis, while gathering your feedback and iterating solutions. We will provide updates to this post to communicate test start and end dates as soon as possible.

Screenshot of a web page layout of a new commenting experience on Stack Overflow. The main content area displays an answer block, followed by a section with five comments, some of which are replies nested under others. Below the comments is a rich text editor labeled 'Your Answer'. Placeholder 'Lorem ipsum' text is used throughout the content areas. Sidebars show navigation and related links.

Measuring Success

Our primary metric will be an increase in constructive engagement within comments. We will also closely monitor comment flags and deletion rates to understand the impact on content quality and moderation load.

What are the new acceptable commenting rules?

To better support an environment where discussions can take place on Q&A pairs, we are experimenting with these updated commenting guidelines on Stack Overflow for the duration of the experiment:

  • Asking specific follow-up questions about the post.
  • Seeking clarification on how an answer works or why it might not work for you.
  • Sharing variations or related experiences pertinent to the Q&A.
  • Engaging in constructive, technical discussion sparked by a question or answer, even if it explores associated concepts.

These guidelines will allow for more interaction than the traditional methodology of only using comments to improve a post or request a clarification of its intent. We want to build a space for technical exchanges. Comments should still adhere to our Code of Conduct, remain polite and professional, and stay generally focused on the topic at hand. Comments should not be a substitute for answers, social chit-chat, or expressions of thanks.

Additionally, we will modify the flagging modal to disable the “no longer needed” flag type for the duration of the experiment. If users attempt to use it, they will be directed to the help center article on commenting, which will have an updated copy for the duration of the experiment.

Changing the rep to comment

After rolling out and evaluating the initial feature changes, we plan to experiment with lowering the reputation requirements for commenting, potentially down to two reputation points. Reputation limits on most features have shown that having rep of two or more prevents most spam. The fifty-rep limit is an arbitrary threshold that was not firmly based on beliefs or backed by data. We are aware that some spam will still get through; however, we need to start stress-testing this part of the system to identify where the reputation threshold breaks down. To be transparent, we would like to explore making it so any user can comment regardless of reputation, but we would first like to test out what we have outlined above before embarking on that experiment. Lowering rep further will require considerably more anti-spam work on our end to make that a viable possibility.

Looking Ahead

These updates are strictly an experiment. Once the testing phases are complete, we will evaluate the results and provided feedback to decide whether to keep any changes, disable them for further work, or revert them entirely.

We recognize that fostering longer discussions in comments might lead to threads that eventually warrant being turned into their own canonical Q&A pair. We see this as a potential follow-up initiative to explore if this core commenting experiment proves successful.

Should these changes prove favorable and effective, we will begin to undertake additional work to enhance visibility into comment moderation and implement general improvements to moderation tools in that area. Thanks to a post by Mithical, which has some good suggestions, we have some strong ideas that we are exploring, and we plan to have a more active discussion with moderators to better understand the needs here.

Ultimately, the goal is to make Stack Overflow and the entire Stack Exchange network more helpful, particularly for those seeking clarification or have related questions on existing answers. We believe that enabling these direct interactions on the relevant post is a crucial step in growing user engagement across the network.

We Need Your Feedback

These experiments are a significant change, and we know there will be strongly held opinions. We would like to hear from you on any of the following:

  • The commenting UI we have previewed
  • Any of the changes related to threading or the expanded editor
  • Changing the commenting policy
  • Lowering the reputation limit

We'll be monitoring this post for feedback until May 12th, 2025.

29
  • 95
    This experiment seems to suffer from the same issue as a lot of other failed experiments in the past several years. Namely: it tries to do too much at once. You should be changing the layout, or the functionality, or the policy on what comments are allowed. Not two or all three at once. Commented Apr 28 at 17:08
  • 28
    Related Make it clearer that comments are temporary Commented Apr 28 at 18:07
  • 15
    Am I confused or something? The first three bullet points in your expanded purpose of comments are part of the existing scope of comments. Commented Apr 28 at 20:45
  • 3
    @Catija We were using the help center article and expanding on the "When should I comment" section when we laid out those points. Which I do feel are quite a bit different. Commented Apr 28 at 20:51
  • 4
    Request clarification covers the first two points. Relevant but minor information is the third point. If you want to have more detailed descriptions, fine... but they're already (generally) allowed. Commented Apr 28 at 21:08
  • 5
    "Evolving" comments? Sounds more like devolution to me. Maybe change the SO logo to the Devo hat while you're at it. Commented Apr 29 at 11:57
  • 2
    @NoDataDumpNoContribution Nope. We are still working on Discussions and are in the process of trying another experiment there. Commented Apr 29 at 13:19
  • 34
    Personally, I think the concept is sound, just not.... not there. Why not take inspiration from the likes of Wikipedia, and just completely separate "Discussions" from the core Q&A, to maintain that cleanliness of "ask questions, get answers, no distractions"? Commented Apr 29 at 14:30
  • 3
    @Robotnik "Why not take inspiration from the likes of Wikipedia, and just completely separate "Discussions" from the core Q&A..." Maybe it's the mentioned visibility challenges ("we experimented with directing users to Discussions for follow-ups, we found it wasn't the ideal solution for these specific, contextual questions. This was partly due to lower visibility compared to the original Q&A page"). Commented Apr 29 at 15:52
  • 20
    @Robotnik I assume you are referring to the Talk pages on a Wiki article? We have discussed that, and I wouldn't rule that out as a potential experiment in the future. Commented Apr 29 at 17:16
  • 4
    @Hoid re: your latest comment and Robotnik's idea, I suggested a very similar thing a long time ago. You can see a demo of it on this deleted Sandbox answer (it was previously a JSFiddle but since the migration away from Imgur for images, the hotlinking on JSFiddle broke). That's a clear example of a 'middle ground' between easily-viewable comments and a separate page/tab for them. Replace traditional comments on the other tab with this more in-depth 'threaded' view, et. viola! Commented Apr 30 at 18:50
  • 3
    Will the length of comments be increased as part of this experiment? Or will code blocks count differently re: the character length? Commented Apr 30 at 19:33
  • 4
    The experiment seems to be live now on SO. Those that think that SO got preferential treatment all those years, just think about how it has to suffer from getting experimented on too. ;) Commented May 13 at 5:14
  • 3
    Alright, it's been a while. Can you now please revert these layout changes? Having comments be displayed at the same font size as answers only makes them distracting. It's harder to spot the next answer, and that is everything this change is doing. StackOverflow already is a very sophisticated platform. There's little room for improvement, so I'd suggest not wasting time on questionable experiments. In particular, I don't think obscuring the UI in this way will change the way people interact with this platform. This does not just take some "getting used to", the new layout is simply worse. Commented Jun 19 at 11:29
  • 4
    The last update was beginning of May, more than two months ago and the experiment was still running then. Is there a word for the pattern when you repeatedly start things in public but then cease to communicate about them, maybe even crease to work on them? Commented Jul 13 at 23:00

47 Answers 47

137

Changing the commenting policy

The new comment policies look like you want to encourage tangential noise on posts. As a post author, I generally have little interest in helpdesk'ing for individuals (policy 2), hearing arbitrary stories (policy 3) or even an entirely new discussion (policy 4).

Given the desired increase of comments that have little to do with the original author, do post authors get an option to opt-out of comment notifications?

3
  • 10
    Or opt out of secondary question discussions entirely? How will users feel if the respondent, having their own busy life, is unable to respond to a lengthening comment chain of variations on a theme? I remember the days of Stack Overflow where if you asked a question and didn't sit there hovering over your keyboard waiting for comments you'd be blasted by the community. Now we're going to do that to respondents, too. Commented Apr 29 at 4:15
  • 9
    Will post viewers be able to opt out as well? As a reader looking to solve a problem, I have zero interest in any of those things and the only outcome is an increased likelihood that I will bounce from excessive noise. Commented Apr 29 at 15:17
  • 7
    As I said on the related MSO question meta.stackoverflow.com/a/433665/4014959 "I'm concerned about encouraging follow-up questions. I don't mind clarifying some detail in my answer, and of course we all should repair any errors when they're pointed out. However, writing an answer should not be an open-ended task". Commented Apr 30 at 13:55
119

What will happen to the content once the experiment is over?

11
  • 52
    Oh, wow. That's an absolutely fantastic question. We'll have a bunch of comments that may well have a bunch of code block formatting in them. If they were to go back to normal comment design, that'd be lost/look janky. What happens to them is a great question. Commented Apr 28 at 18:00
  • 53
    There'll also (I'm not even going to say 'probably' here, I'm that sure) be a whole backlog of stuff that would've been flagged but wasn't because NLN flagging was disabled. What's the plan for cleaning up those broken windows as fast as possible? Commented Apr 28 at 18:32
  • 15
    Or is the plan to just not, and this isn't really an experiment at all? Commented Apr 29 at 15:07
  • 30
    And indeed, what happens to threaded comments? I can't see threading being lost, and nor can I see the coding effort for threading being wasted either. This is not an experiment. Commented Apr 29 at 16:12
  • 18
    Their primary metric for success is increased engagement with comments. Lowering the rep limit to comment and making comments more prominent is all-but-guarenteed to increase engagement, therefore the experiment is successful and we can keep the changes... Commented Apr 30 at 19:58
  • 2
    That we still do not have a response to this after a (work-)week is severely disappointing. As there was no reason given for the absence of a response either, I currently interpret this to mean that SE either entirely failed to think about this very obvious issue and have been scrambling since monday to find a solution to this huge hole in their plan, or do not want to answer this for whatever reason (e.g. maybe they never intended this as an "experiment" to begin with but as a permanent addition disguised as one). Neither option is inspiring any confidence in the SE development process. Commented May 2 at 13:14
  • 2
    @l4mpi Or they just didn't get to it/didn't consider it sufficiently important/whatever - it's by far not the first time things like that stay unanswered for a while. That doesn't automatically mean they have an issue with answering that question specifically. If you look at other answers here, this is not the only one without a staff response. Commented May 2 at 14:20
  • 1
    @dan1st my point is that by not answering this question about an issue which has the potential to leave the site littered with broken content, SE are increasing my doubts about this feature request, which were already substantial before that. The specific reason for not answering does not really matter; if the reason is that they do not consider this to be important enough, that doesn't inspire any more confidence in their development process either. Commented May 5 at 8:01
  • 2
    I think "it's too hard to undo this" will end up being a significant deciding factor, irrespective of whether or not there any 'improvement' in 'engagement'. Commented May 5 at 11:19
  • 1
    This will depend on how the experiment goes. If things go very well then we wouldn't take any action to remove any content. But if things don't go so well or things go very poorly, we would look at removing content. We will be sampling the comments to see what ends up being left though. Commented May 12 at 17:13
  • 6
    @Hoid "we would look at removing content" - so your plan to deal with nested comments if the experiment fails is to delete all of them? That sounds like nobody considered this question important enough to create a solid plan to deal with it before announcing the experiment, which is just as bad as I expected. OTOH I expect the experiment to be declared a success regardless of the actual impact of the change, so the question is probably irrelevant anyways... Commented May 13 at 11:42
99

At first glance this looks a bit like you want to turn a Q&A site into a forum (or Reddit). Which is kinda the opposite of the original idea for Stack Overflow. Doesn't mean this is automatically a bad idea, but I'd cautiously evaluate the effects this might have on how people might use the site.

To me Q&A isn't necessarily the only option, but it is the most valuable one for creating and curating content for later visitors. So even if we don't start with a Q&A pair directly and a longer discussion arises, I think in the end the result should be a question and an answer, to ensure a high signal to noise ratio.

I see a danger here that the better the discussion features are, the less likely people will be to post actual answers. I think one idea worth experimenting with would be a "promote comment to answer" action, to push people towards distilling comment threads into real answers. This is much more viable in your experiment as comments have actual formatting options.

It might even be worth it to experiment with allowing other users to promote comments to answers even if they didn't write them themselves. This adds a lot of potential problems so it would need much more care, but I'm imagining something more like an automatic Community wiki answer with a non-removable attribution to the comment it was created from. But this is a bit more of a crazy idea, not sure how people would react to this.

9
  • 26
    "Doesn't mean this is automatically a bad idea" why not? The forum/Reddit market is saturated. Turning a Q&A into either of those seems like making the problem worse, at least on first glance, for me. Commented Apr 29 at 7:24
  • 15
    It really looks a lot like Reddit. Commented Apr 29 at 7:24
  • 4
    Or maybe they want to turn meta into a useful place where discussions can actually be had, in place of the current "everyone posts a monologue of their own" model which is horrible. We have a room of some 20 people all holding their own monologue instead of a room with 20 people where everyone who has something to add can do so in turn, in an organized manner. Commented Apr 29 at 13:36
  • 6
    "this looks a bit like you want to turn a Q&A site into a forum (or Reddit)" Rather it looks like they are finally going to fix the last place on the whole Internet that doesn't have threaded comments. It's long overdue and there are no sensible arguments against it. Try to read a popular comment field after some 50+ comments. It's impossible, everyone are having their own monologues there. It soon turns into a complete mess and the moderators have no option but to give up and nuke the whole thing. Kind of like weeding ones garden using a flamethrower. Commented Apr 29 at 13:40
  • 4
    @Mast "The forum/Reddit market is saturated"– sure, but those aren't integrated with high-quality Q&A, either. Integration is a valuable asset, if they avoid damaging existing Q&A. Commented Apr 29 at 16:16
  • 4
    attaching a forum might not be horrible, but comments are very much not a suitable place for that. Comments are great getting clarification and help improve questions/answers. Allowing off-topic is bad. If people want reddit, they can go to reddit. Commented Apr 30 at 12:09
  • 1
    @Lundin I don't think Mad Scientist's (or anyone else's) arguments here are against threading in general, just this specific implementation/design proposed above. There's a lot of room between the current unthreaded layout and... Reddit's comment design. Commented May 1 at 15:51
  • 1
    "promote comment to answer" - I suggested something similar myself: "copy this comment to an answer" Commented May 4 at 20:16
  • @Lundin - the argument against it is the purpose of comments here is supposed to be limited and they are supposed to be secondary to the question both in intent and visually (reflecting that intent). They exist to help flesh out the question, not become their own discussion (thread). There simply should not be 50+ comments and if there are then that is an indication a) the question is very bad and needs lots of resolving and/or b) the users have lost the plot, ie they are not trying to improve the question and are on some other agenda. Commented Jul 25 at 17:34
84

question about what appears to be a massive regression in functionality, tantamount to introducing a breaking bug:

Additionally, we will modify the flagging modal to disable the “no longer needed” flag type for the duration of the experiment. If users attempt to use it, they will be directed to the help center article on commenting, which will have an updated copy for the duration of the experiment.

Why? How are we supposed to flag comments that are no longer needed, then? This experiment will in no way eliminate the phenomenon of comments not being needed any longer. I say this as someone who has cast nearly 30,000 helpful NLN flags on Stack Overflow alone.

8
  • 9
    Flag them as "Something else" with user text of "This comment is no longer needed" /s but also not. 🤢 Commented Apr 28 at 23:40
  • 5
    @DanIsFiddlingByFirelight Doesn't that turn a 90,000-click-history into a 90,000-click + 960,000 keystroke history? That's an unreasonable workaround. Even reducing your text to "nln" adds 90,000 keystrokes to an already lengthy history. Commented Apr 29 at 4:11
  • 4
    @JBH Dan's comment is most likely based on this one Commented Apr 29 at 5:18
  • 3
    @VLAZ Yeah, I saw it, but its repetition here was irritating. I believe I also saw a fine response, something like, "why have any other option since 'something else' covers everything?" What I haven't seen is an actual explanation for why it'll be disabled. It's as if our SE Overlords want all the chit chat no matter how banal. Besides, TylerH's history made the issue so very visceral. Commented Apr 29 at 5:38
  • 1
    @JBH while I suspect the most prolific flaggers would copy/paste or macro it reducing it to at most a few extra key strokes; the extra effort was part of why I was semi-sarcastic. Commented Apr 30 at 3:51
  • @DanIsFiddlingByFirelight I didn't (and still don't) see the sarcasm, but I apologize for any mistreatment. Commented Apr 30 at 14:42
  • 1
    @JBH /s (after the quoted text) is a standard internet sarcasm marker. Commented Apr 30 at 21:08
  • 1
    @DanIsFiddlingByFirelight I'm 60 years old and don't use internet-related abbreviations. Never assume your audience knows your shortcuts. TylerH, I apologize that we've hijacked your comment chain. I won't comment again. Commented Apr 30 at 22:44
60

we found it wasn't the ideal solution for these specific, contextual questions. This was partly due to lower visibility compared to the original Q&A page

I'm not a fan of the idea of making comments more visible than they already are. Giving them more visibility is going to distract from the Q&A. The example you showed takes up a huge amount of space and I find it very distracting. Even if the default is apparently to have them collapsed, I assume you won't be changing that a handful of highly-scored comments remain inline automatically, and the new form factor is much bigger than it is currently. Stack Exchange is supposed to be a place people can get answers to questions without the noise that is common in other places on the internet.

we will modify the flagging modal to disable the “no longer needed” flag type for the duration of the experiment [...]

I don't see why disabling NLN flags is necessary. Why would you do this? Unless your rule updates remove existing reasons not to comment (do they?). Please, don't do this. How are we going to flag the vast amounts of NLN comments that are created every day during this experiment?

Our primary metric will be an increase in constructive engagement within comments. We will also closely monitor comment flags and deletion rates to understand the impact on content quality and moderation load.

What about increase in unconstructive engagement? You seem to have a filter on your glasses to only look for success. Especially given that you're removing the NLN flag for the experiment.

4
  • 1
    Yes, it could work if the comments are collapsed or mostly-collapsed by default (like currently where only the most upvoted N comments are shown if there are >N), but it sounds like they're planning to show all comments by default, and make them bigger? There's already a problem with people exploiting comments to sticky low-quality pseudo-answers or opinions to the top of the page. Many visitors from search will see reams of irrelevant chatter and close the tab before they scroll past to the actual quality answers. Commented Apr 30 at 15:41
  • 1
    (oh, apparently they're going to be collapsed by default? It's kinda worrying they're so unclear on such an important detail) Commented May 2 at 10:47
  • 1
    I'd agree with the problem of unconstructive engagement. Experience shows us that comment sections often become places where people who cannot accept a close vote or downvotes or criticism seek to argue at length to try and force people to accept their point of view. We don't need to encourage this and we need a way for mods to shut these things down. Commented May 7 at 20:47
  • Yes, besides all else, please make sure this does not take up too much vertical space, distracting fromt he real Q&A! The huge Vote button surely can find another place! Commented May 23 at 9:13
57

Users also expressed confusion about the distinct purposes of comments, Discussions, and Q&A.

After reading the motivation for your upcoming experiment, count me in. Now I'm also confused. To me it reads like you want to have everything in one page and everything can be everything. Code in comments, discussions in comments, follow-up questions in comments. What can possibly go wrong? And will the confusion be reduced or reach new heights? The experiment will hopefully show.

But let me emphasize one more aspect.

Mockup from question with annotations showing how even more space is cluttered with noise instead of informatiom

At the very least, show all the extended, discussionary, code containing comments collapsed initially. From a perspective of knowledge consumer, already now the pages are unfortunately low concentration of knowledge (much space in between question and answers) and I can imagine this becoming even much worse, next to unusable.

12
  • 16
    Plenty of users right now don't read past the first answer. And some even confuse comments for answers (and complain why they don't answer the question). I don't have stats but from what I've seen either post, the latter group seems smaller than the former. And yes - both are composed of predominantly first-time users. At any rate, how would both of these categories of users take to the even-more-answer-looking comments? Seems like a good way to confuse both of them. Commented Apr 29 at 11:29
  • 13
    The comments are expanded here just for demonstration purposes. Default would be to have them collapsed. This image was shared just to show the desired end state. Our first experiment will be just the UI changes: Bigger comments, different buttons and the updated user card. When the experiment starts, there will be a separate post on MSO for those users to offer feedback, and all the details of what the expected behavior should be. Threading and the full editor will come as a second and third experiment. Commented Apr 29 at 14:00
  • 3
    @Hoid Thanks for the reply. That would probably be better, but I hope you saw the point. With bigger comments and threading and the full editor, more and more space will be needed and the most important content, which would be the answers I think, will move further and further below on the page, reducing the value for visitors just wanting to read the answers. It surely depends on how the UI is done exactly. The idea seems to be to cram everything on a single page, and I just wanted to point out where disadvantages of that approach could be. Commented Apr 29 at 14:21
  • 17
    @Hoid PLEASE edit the initial post with an image of the question with the comments collapsed. This is 90% of my hesitation with the proposal, and if the comments start collapsed I think that's a good start. Commented Apr 29 at 17:31
  • @Kaia Another user did so since your comment, and I just edited that bit to be very large/clear, for future readers. Commented Apr 30 at 19:04
  • I don't believe what you describe is an actual issue. These days we have mice with spinning wheels, touchpads, touchscreens – all that makes scrolling easy. Compare this with reddit design, where many answers are initially collapsed, and you need to make many mouseclicks to read the whole discussion. Present SE design is annoying too. You read comments, they make no sense, and only then you realize that they are answers to some collapsed comments, you need to click, and read again. Waste of time. Commented May 3 at 13:46
  • @user1079505 I believe it is. Of course scrolling is available, and Reddit is a fine site, but I don't use it for information retrieval. It's entertainment. We should make an experiment. One cluttered SO site like the one shown above and one cleaned up as much as possible and make a test, which site visitors prefer. The data will show us how much of an issue it is. Commented May 3 at 13:58
  • 1
    @user1079505 I don't know why you're trying to show that "being able to scroll fast" was the issue. It never was - you could middle-click on the page, or use page up/down, or home/end for ages, before spinning wheels. The issue has never been the ability to scroll, it was the necessity to scroll in order to read the whole thing with potentially irrelevant content in between what you're actually here for - the questions and answers. Reddit does have the same problem - it's not build to expose content, it's to allow users to have infinite discussions spinning off it. Commented May 3 at 15:45
  • @VLAZ maybe that's a matter of a preference and opinion, but to me hitting page down a couple of times is much easier than making multiple clicks to find the right thing. I'm here and not on reddit for a reason. Commented May 3 at 16:23
  • 1
    @user1079505 I'm saying that the mode by which you scroll hasn't been the issue. Having to scroll to keep all the relevant content in view is. Commented May 3 at 17:36
  • 1
    The screenshot in the op does not even have any answer. Maybe that's the goal, remove answers and replace with comments on the original post. Very much like reddit. Commented May 5 at 6:38
  • 2
    @Hoid "Default would be to have them collapsed." Is this true? People seem to report that by default nothing is collapsed. Maybe something has gone wrong. Commented May 19 at 12:29
49

Our primary metric will be an increase in constructive engagement within comments.

That seems positive, but ... engagement is not the intended purpose of comments. They're primarily a collaborative way to help improve questions / answers. I.e. if I post as a comment (for example) "What version of python are you using?" the asker can either reply in another comment or edit the answer into their question. The former is higher engagement but the latter is what we actually want them to do.

Comments are deliberately less fully-featured than questions/answers. Not because nobody bothered to add proper markdown and threading support, but rather to encourage people to use questions and answers instead.

It seems pretty obvious to me that making comments more visible and fully-featured and making it easier to comment will result in more engagement with comments. It's less obvious that this is an improvement for the site as a whole. It's probably worth thinking about it you can find any way to measure that, e.g. if less askers are editing their questions that's a bad thing.

4
  • 6
    You're absolutely right, but I think the idea being experimented with here is to change the longstanding "intended purpose of comments", in order to facilitate more engagement, all while hopefully avoiding sacrificing the high-quality Q&A format. Whether that's possible remains to be seen. Commented Apr 29 at 15:54
  • 1
    @zcoop98 what makes that confusing is how their wording changes to the existing comment rules/guidance seems not really to be that different from what is already in place. Commented Apr 29 at 19:04
  • 1
    @zcoop98 that may be what they're implicitly trying to do, but they didn't articulate that and don't seem to be looking at any metrics that would indicate whether they are successful at changing the purpose of comments without sacrificing high-quality Q&A. Commented Apr 29 at 23:49
  • 7
    The negative impact on Answers should be measured. If a comment can replace an answer because it can have code, answers may degrade in quantity. Commented Apr 30 at 5:09
46

You got my attention; this is an interesting set of ideas. However, in light of very real problems we've seen with our current system, I must ask: How does a new user tell the difference between Question Response Input Box #1 and Question Response Input Box #2?

One of these allows pretty much any content you can write with no consequences, but posting the wrong thing in the other one leads to negative comments, negative votes, and sometimes it can even lead to the semi-automatic suspension of one or more Responding-to-Questions privileges. Of course, if you're familiar enough with SE (and this new design) to know that #1 is properly called a "comment" and #2 is an "answer", you can probably avoid such a travesty (and maybe even exploit it a little on purpose—leaving all your potentially controversial responses as comments). But how does a new user manage? Alternatively, how can we, the people who moderate the site, deal with this in a way that doesn't suck for everyone involved? We have an answer-to-comment mod tool, but it's always seemed quite lacking to me given that it's only available to mods.

In the same way, as a reader looking for an answer, my eye is drawn to the answer above "Your answer". But this isn't an answer at all but a comment. Comments are just so more visible in this mock up that I wouldn't be able to find the answers proper.

This doesn't even touch the fact that there's yet another Input Box: Questions. There's an undeniable appeal to using comments as a substitute (no downvotes plus you can notify an expert directly), but questions really should be asked as questions. Do we let a question-in-comments run its course and then wait for someone to repost it properly? This has its own cost in that information that's germane to the original question gets more buried and hard to find.

4
  • 5
    You raise really good points and its obviously a bit of a ticky problem. Some things we are thinking about to resolve this is to first add more user settings for things like always keeping comments defaulted to collapsed and more notification settings. We believe there is a path that can be created to convert comments into Q&A pairs. But we first wanted to start with making these UI & functionality changes to see if the existing users comment more and enjoy the more permissive commenting experience. It might be that it changes nothing without users who currently have the privilege. Commented Apr 28 at 21:19
  • 4
    We do plan to discuss directly with all mods later this week on what their thoughts are from the moderation angle so that we can address those potential issues more directly. Commented Apr 28 at 21:22
  • 6
    @Hoid users will most probably comment more and enjoy the more permissive commenting experience. However, this will come at the expense of cluttering the content and diluting the Q&A format. Users will post answers, questions, and unrelated discussions in comments. It will be harder to find what you are looking for among all the clutter, good content will not float to the top, bad content will not be downvoted, closed as duplicate, put in a review queue, etc. This will make Stack Overflow and other SE sites much less useful for future visitors, which will bring site visits and engagement down. Commented Apr 29 at 7:04
  • Yeah I can see this being a classic "new coke" product testing error: "People respond really positively in the short term to all this extra sugar! Let's launch it! ...wait, why in the long term do fewer and fewer keep coming back?" Commented Apr 30 at 15:45
39

Measuring success. Our primary metric will be an increase in constructive engagement within comments. We will also closely monitor comment flags and deletion rates to understand the impact on content quality and moderation load.

This feels like a nice Italian restaurant saying “We’re trialling some fast food items. Our metrics will be the sales of beer, burgers, and chips; we’ll also monitor customer feedback on those.” You need to also monitor how it affects sales of other dishes — do existing customers switch to the new cheaper items, or get put off entirely by the change of vibe? Or does the fast food bring in new customers, who then trade up to the upscale menu? Does the change support your existing core strength, or undermine it?

A more flexible comment section might be great, but not if it draws attention away from the main Q&A. (That was the stated goal of keeping comments minimal in the first place.) Please monitor the effect on overall site quality, not just on comments themselves!

5
  • 3
    Happy to take requests back to the team for specific measurements you would like to know more about. I don't want to guess at what you're asking for, but something like Q&A declining against commenting at large increasing? Commented Apr 29 at 13:30
  • 6
    @Hold its the kind of thing that's difficult to state objectively, especially since there is a presumption that the company will try to justify the changes after the fact. A lot of this is long term effects. Commented Apr 29 at 15:02
  • 9
    @Hoid the motto of SE is "ask questions, get answers, no distractions". If a useful comment is surrounded by not-useful comments then the other comments are a distraction, which is bad. So that can be your metric: count the average ratio per question of useful to not-useful comments, either automatically through comment upvotes and/or flags, or by manually annotating a sample. Note that this metric is inversely proportional to comment rate: less comments overall means (most probably) a higher ratio of useful to distracting comments. Commented Apr 30 at 6:01
  • 1
    I’m not at all sure, but just spitballing, some ideas could be looking at how comments on a question/answer correlate with edits/votes/views on the question answer, and other answers on a question. E.g. if a top answer gets many comments, do votes/views on lower answers decline afterwards? If a question gets many comments, is it more/less likely to get answers afterwards? Commented Apr 30 at 9:24
  • 1
    @Marijn The rate of useful comments might indeed be favoring less but more comments than now. The metric could be a trade off between rate and absolute number, something like number of useful comments^alpha /number of comments for alpha > 1. Commented Apr 30 at 19:55
33

I see the upside of what you're trying to embrace, but I also see the downside and wonder if it's really worth it

I'm concerned that this attempt to become something more like Reddit will undermine the intrinsic value of the service. The Tour tells us,

The guidance on all our Q&A sites explicitly disallows meta-discussion, to reduce clutter and noise. There's no chit-chat; just questions and answers.

...

This site is all about getting answers. It's not a discussion forum. There's no chit-chat.1

And yet your prototype presentation appears to step more than halfway to dispensing with those expectations. Why not, then, simply do away with the Q&A format altogether and shift to a fully discussion-based solution as is used on Reddit? Because that's what it appears we're becoming. (Assuming that AI-generated searches don't make SE obsolete anyway. But we'll set that aside.)

What Stack Exchange has been in the past is a place where a specific and reasonably objective question can be asked with a best-practice or most-acceptable answer rising to the top. Secondary questions were asked anew with a link pointing to the answer that spawned it, preserving the basic integrity of the service and its information structure.

That will no longer be true.

And while the honest at heart will find it easier to explore clarifications and variations, too many people (IMO) will use it for disagreement, tangents, even misinformation — which can only be minimized through an increased moderator burden, unless you allow users to down-vote comments that the community believes are unhelpful, unrelated or misinformed.

Finally, I believe this will eventually create a powerfully negative experience for future users who can no longer find tightly focused questions and solutions relating to their problem but must now navigate pages of comment chains just to determine if a variation exists that's closer to the exact problem the future user is trying to solve. It's already difficult to convince users to edit their questions and answers with clarifications rather than leaving them in comments where they're difficult to find or easily overlooked. You're about to motivate them, possibly even reward them, for doing exactly that.


1If you do go through with this, I hope you take the time to update the Tour and Help Center to reflect the changes. Your track record in that regard has been poor and that causes its own problems as people refer to outdated material in support of actions no longer considered appropriate.

6
  • 12
    "Assuming that AI-generated searches don't make SE obsolete anyway. But we'll set that aside." Ironically, it’s high-noise, chit-chat "information sources" that make me use AI search. Any tech that primarily relies on discourse, reddit, or similar is prime fodder for AI search - let’s see if I have to add SO to that list in the future. Commented Apr 29 at 7:10
  • 10
    @MisterMiyagi: Hand in hand with that, the unreliability of AI search results these days (and AI slop polluting other search results) makes me appreciate the focused quality content of sites like SO/SE more than ever. Commented Apr 29 at 11:10
  • 7
    "this will eventually create a powerfully negative experience for future users who can no longer find tightly focused questions and solutions relating to their problem but must now navigate pages of comment chains" -- This is my main concern. Not having to read through discussions to distill the answer is IMO the main benefit of SO over forums. Commented Apr 29 at 15:46
  • I think this is a real danger, if they don't separate concerns properly. If they figure out how to both enable broader commentary & discussion and also keep Q&A as the clean, focused information source that it is today, I think we get the best of both worlds (with some bonus "engagement" numbers sprinkled in for the Company as a treat). Commented Apr 29 at 15:51
  • 1
    @zcoop98 I would hope for that too, but I don't believe it's possible. SE is manifesting a user interface. How does one teach a computer to seperate concerns? How do you stop someone from asking for help for a related problem that's just a little too much for comments? I believe in miracles, but not magic. What you're suggesting feels like magic. Commented Apr 30 at 1:59
  • 3
    @JBH There's currently a retreat from the AI is our future model, so we're keeping the humans for now at least. Commented Apr 30 at 2:05
33

UPDATE: Stack Exchange has decided to not remove the "No Longer Needed" flag and instead rename it to "Not Needed" (which might be a good idea to keep as the name even outside this experiment). My original answer is preserved below.

Please don't remove the "No Longer Needed" flag. Plenty of comments will still have no place in the comment section, even with this experiment. "Thank you so much" is still NLN. As is a comment asking for a change to a post which has now been made.

2
  • 5
    I still haven't wrapped my head around what removing this exceptionally useful flag accomplishes. Commented May 1 at 10:34
  • @ouflak Same here Commented May 1 at 10:34
30

I like this, but I personally feel it is highly situational, that is, it's only particularly useful on certain Stack Exchange network sites which include topics that are inherently a bit looser and more conversational in nature.

I'd strongly suggest viewing this as a feature you:

  1. Only turn on for specific Stack Exchange sites where that commenting format is a better fit.

  2. Have strict configurable limits on the feature (say, only ONE level of comment reply nesting, there's a few other limits I can think of that'd make sense.) Let the site's moderators and the site's meta community decide how best to use the feature on THEIR site.

4
  • 1
    This is my favorite answer so far: I'd ask for MMSE (and maybe others) to continue not allowing new questions to be asked in comments (every question goes in a new post, which can contain a link to related questions), and to keep the reputation requirement for commenting, or even to increase it. Commented May 3 at 14:44
  • @user1271772 I think empowering the site's moderators and the site's community (via meta) is almost always the best answer. We are doing a specific flavor of Q&A here, and we can't (and shouldn't ever) lose sight of that, but some sites are inherently less data/science/fact oriented. Commented May 4 at 2:28
  • 1
    "say, only ONE level of comment reply nesting" - Good idea. For comparison, I love Reddit, but its endless branching threads can be impossible to read if they get deep and tangled. Commented May 4 at 19:38
  • 1
    If the experiment is deemed successful, I recommend letting each stack discuss it in Meta and then vote on whether to adopt it or remain with the current style. Commented May 5 at 15:09
28

The experiment is focused on the interaction needs of askers, not on the needs of readers coming to this site half a year later with a similar problem.

The key value proposition of SO is that when I have a technical problem, I can find an existing question about it with multiple answers that are maintained over time, with updates and so on. If instead I get my problem in 4 different comment threads that are unmaintained, this site becomes much less useful in solving the problem for me that other people already had. Follow-up questions are still questions and deserve to be treated as questions, not comments. Follow-up questions need to be visible to all as unanswered, need to be tagged, need a title, linked questions...

So this experiment ought to measure new flags on comments like "this should be a top-level question/answer".

2
  • 1
    keeping in mind that what is seen from helpful flags will always be underrepresentative of all the things that should be flagged for each reason, at least for large-scale sites like SO. Commented Apr 30 at 6:25
  • Are follow-up questions questions or comments or sometime in between? I also wonder about that. Commented Apr 30 at 21:22
27

for the UI/Design

I don't see a flag icon in the example layout image above, so I can only assume it is hidden behind the ellipsis. Please don't add extra clicks for the number 1 (or maybe number 2) most used action on a comment. There is plenty of space as shown below for a flag icon:

screenshot of the proposed comment layout/design with red circles around empty area currently available for displaying a flag icon

Unless clicking the ellipsis directly/immediately expands to show the current flag options (including the textbox for custom/mod flags), this seems like a clear (and completely unnecessary) regression in UI/UX.

5
  • 5
    I don't have it mentioned in the post, cause I didn't want to get to into the weeds on something that might/probably will change. But we have them show up on hover instead of a dedicated button. Not set in stone though. Commented Apr 28 at 17:01
  • 8
    FWIW, it's similar to the Discussion design where some actions are hidden behind the three dots button. And yes, that has lead to multiple queries like "how do I delete my post" or "how do I edit my post". Commented Apr 28 at 17:03
  • 10
    @Hoid This is an announcement requesting feedback on an initial idea for an experiment, is it not? Doesn't "something that might/probably will change" apply to everything in the question? Commented Apr 28 at 17:12
  • 1
    I'm fine with the ellipse... if it was given the same prominence as the reply button in the same location as the reply button. Currently it's not where you would expect to see it. Commented Apr 28 at 17:14
  • 6
    @Hoid Hover is useless on touchscreen devices. A lot of people access the sites from phones (or tablets) these days. Commented Apr 30 at 13:50
24

There's a lot of things wrong with this proposal, as detailled by many of the other answers, but I'll focus on one part which was already a problem with various past experiments:

Our primary metric will be an increase in constructive engagement within comments

That sounds highly problematic. You do not define "constructive" engagement, which means this is open to interpretation, and of course as SE is the one proposing this experiment, SE will be biased towards seeing it succeed. Given past experiences, I can already see you counting all non-flagged comments as "constructive" even if they might be utter garbage and nobody got around to flagging it, and/or interpreting an increase in overall comments as a good thing even though that might just represent an increase in noise.

One thing I am certain of is that SE will not commit the manpower to manually inspect all comments or even a significant percentage of comments created during the experiment, which means it will be impossible for you to analyse the results in-depth to see if they actually represent positive, valuable engagement, or if they are noise, useless, or harmful (and you might be thinking of using AI to perform a classification, which would make this worse because now you're adding a BS generator into the mix). There are not many SE employees who are active SO contributers either, so your internal feedback from people who are directly affected by the change will be limited as well. All of which means that my trust in your analysis is effectively zero.

Of course, given the volume of comments, it's not realistic to expect you to be able to analyze all of them in-depth. But that doesn't make it better to use statistics that will at best be flawed to decide the success of the experiment. Instead, why not run the experiment, and at the end of it share as much data about it as possible and gather another round of feedback from the community to gauge which parts of the experiment are well received and which parts are problematic, and make permanent changes (or can them) based on that feedback? That would be a significantly broader evaluation of the changes and their impact, give the community a meaningful way to participate, and reduce animosity against unilateral decisions by SE.

23

So – this feels a little like trying to shoehorn aspects of discussions into comments. Some of these feel like old feature requests – threading and formatting might actually be useful.

On the other hand – The UI at present feels a little too much like a forum, especially with the comments uncollapsed. I wonder if some visual/site distinction would be useful. I also feel like practically this would be more useful in the process of refining a question, than an answer.

This experiment represents a significant shift from the long-standing philosophy that comments are ephemeral and intended solely for post improvement or clarification. We recognize that this change may be unpopular to some and welcomed by others.

Which leads to a very important question – one of the goals of SE's design was to lower noise. The core information should be in a question or answer. I'm not entirely sure how changing the ephemerality of comments helps with creating a clear, referable knowledge base. I get the purpose and friendliness of a more forum like metaphor. I'm not sure it plays to our strengths.

Need for Follow-Up Questions

A key takeaway from our previous experiment was that users want to ask specific, technical follow-up questions related to existing questions and answers. Our analysis showed common needs such as asking direct follow-ups, clarifying answers, sharing variations, or explaining why an answer didn't work for them (and why). These attempts often included code blocks or images, which current comments do not support.

I think its worth distinguishing these follow ups in terms of 'immediacy' – I'm quite happy to work with another poster on an answer I'm writing on now. If you asked me about some obscure answer I posted 15 years ago… I'm not going to remember. A useful goal would be to optimise for people working through the answer, but not delayed/unrelated follow ups.

Additionally, we will modify the flagging modal to disable the “no longer needed” flag type for the duration of the experiment. If users attempt to use it, they will be directed to the help center article on commenting, which will have an updated copy for the duration of the experiment.

So, I'm not sure about SO, but I have a handful of folks who flag very old comments we have missed as NLN – they are NLN and best gone. SO might handle things differently but would this be for 'new' test posts or all posts.

And on that note how are pre-test comments handled, and how would test period comments be handled should the old behaviour be reverted?

1
  • 8
    I fully agree with your core part. SO is useful because I can read a visually well-formatted question with a visually well-formatted answer(s) below it. All comments can be discarded at first, only to be read if one is interested. Much like footnotes in books/articles. Giving comments such a prominent visual place makes it (much?) more difficult for a quick reader to distinguish between relevant (Q and A) content and chatty follow-up clarification/question/addition/thanks/I-lost-my-keys. Commented Apr 29 at 6:51
17

Do you have a plan yet for the situation where a comment is deleted that has replies?

Currently in discussions... this results in orphaned replies. I think in the case of threaded comments there's no reason not to just take the extra step and also automatically hide/delete all of the replies to the deleted comment.

2
  • Similar concern: how to show only top-k highest votes comments, and drill down into single threads? The single screenshot is not good enough as specification or for validation or review. It can only serve as a first impression. Commented Apr 29 at 21:25
  • 1
    Also being able to understand which parent a child comment belongs to becomes very hard. Reddit has many obvious lessons learned from any example with 100s of comments instead of just 5. Commented Apr 29 at 21:32
17

The first thing that kinda looks odd to me is the upvote button. Sure, comments today have upvotes, but in this larger, more spacious format it almost looks out of place, or lacking a clear opposite action.

I'm not suggesting we should have downvotes for comments, rather, maybe we should use an icon that more accurately fits what upvotes on comments are, since upvoting on answers and questions are expressively different from upvoting comments.

1
  • But "expressively different" would no longer be true, correct? The new chain-discussion comment allows for variants of a theme to be discussed. Those variants may be more valuable to a future user than the answer itself, which means the comments are now of equal value to the answers. Should the community have no way to suggest that a discussion has gone too far off target or that a commenter has started from a incomplete or false premise? Commented Apr 29 at 4:06
17

Allow users to access their deleted comments, even more so since in your proposal, comments can be even more substantial.

4
  • 6
    I concur and here's why: On one occasion I've posted comments that were followed by a user getting very upset about it and the whole thread was deleted. If we have access to comments then what I did (pestering the local mod to tell me if I did anything wrong) wouldn't be necessary as I could have decided for myself if the user was justified in losing their temper at what I said (or didn't). Seeing deleted comments facilitates self-auditing for future interactions. Commented Apr 28 at 17:37
  • 4
    While this is a reasonable thing to consider, I'd want to approach it with great caution. Comments are sometimes deleted to quietly end or de-escalate a contentious interaction; giving users an easy way to find (and potentially re-post) such comments might lead to users re-escalating a situation. Commented Apr 28 at 22:29
  • 6
    @RyanM repost = ban (could be automated). Nowadays, since I can't access my deleted comments, I sometimes don't know if I'm reposting. Commented Apr 28 at 23:26
  • 1
    I have more than once reposted a comment that I thought failed to post for technical reasons, or that I thought I forgot to press Add after writing, but that I think, in fact, were deleted by bots. If I could see them, I might not repost or I might improve them. I don't know! I have no way of knowing, ever, how many of my comments were deleted by moderators or bots and why. It would be great they could tag deletions that their authors could see. Commented Oct 16 at 3:09
17

My prediction is that this change will increase "engagement", just not from people you'd necessarily wish to engage with. Eventually the advertisers will wisen up to this.

The whole point, the entire differentiator of the Stack Exchange network is to offer on-topic Q&A content. Adding what amounts to a Reddit or Slashdot thread to every question and answer seems to be counter-productive.

Follow-up questions should be asked separately, as their own question. That's the case everywhere on Stack Exchange. This experiment attempts to change it - maybe? You're not clear on that. Does "follow-up" mean questions by the original questioner, or questions related to the question that ask for clarification? This is a technical discussion of a feature, so unambiguous language does matter!

On SE, an "ideal" question and answer should have zero comments. The purpose of the comments is, in essence, to point out various shortcomings of the content being commented on. Those shortcomings may be related to clarity, on-topic-ness, correctness of answers, etc. The ideal lifetime of these comments should tend to zero.

Since this cardinal premise will be broken, What will be the differentiator between an answer and a comment, or between a comment and a separate question? Do we need "me too" comments, "thanks", and such? What comments do you really wish to see? "Engaging comments" is meaningless in this context. That's a wish, not a solution, and you seem to offer a solution for evaluation - where, seemingly, there is not much to evaluate.

I would expect, at minimum, not to see "Lorem Ipsum" in your comment examples. You should give several examples of desired, "real life" comment chains that you'd like to see under questions and under answers. Cover as many use cases as you have.

The use of "Lorem Ipsum" tells me that you have no use cases, and the whole idea is vacuous.

2
  • 12
    I don't think it's fair to levy the use of "lorem ipsum" text against them here. The screenshot is just to demonstrate the proposed design. Would it really have changed your mind if a real discussion was showcased in the screenshot? Commented Apr 29 at 15:11
  • 3
    @Spevacus actually I think the comment about "Lorem Ipsum" was spot on! I zoomed in to read the "use case" that they had in mind, only to find that they chose not to put the effort into making one that they'd feel comfortable to present. Commented May 3 at 14:54
17

Gavin's answer raises a great point:

Comments are deliberately less fully-featured than questions/answers. Not because nobody bothered to add proper markdown and threading support, but rather to encourage people to use questions and answers instead.

as well as this ensuing comment reply by tkruse:

The negative impact on Answers should be measured. If a comment can replace an answer because it can have code, answers may degrade in quantity. – tkruse Commented 2025-04-30 05:09:30Z

If you are adding code block and other formatting support to comments... you probably need to consider giving moderators the ability to convert comments into answers, and/or give certain users the ability to (auto) 'flag' or vote for a comment to be converted into an answer1, at least for the duration of the experiment.

Currently moderators can convert answers into comments, but not vice versa. Yet, we have a real problem (and have for many years) of people answering in comments (something they shouldn't be doing and something comments are not meant to do). If users can now give all the same formatting capabilities to their comments as they can to their answers, it stands to reason that they're going to be posting answers as comments more often, not less.

The consequence of this is that, while you may see more comments with this experiment/new feature set, you'll likely also be shooting yourself in the foot regarding the answer rate on the network, which has been declining for several years, if I recall correctly.

I'm not sure whether it would make sense to have this restricted to just comments under an answer. Any such conversion would also necessarily raise a notification to the comment/answer author.


1: Similarly to how a certain number of No Longer Needed flags from users will automatically delete a comment, if a comment gets a "this looks like an attempt to answer" flags, it should be handled by a moderator. Alternatively, if some number of such flags are raised on a comment (say, 5), then it should automatically convert to an answer, and all child comment replies under it should be converted to comments under the answer.

   To avoid abuse, this flag could be restricted to the first 90 days (or 365 days or whatever) after a comment is posted, just like how we can't flag/vote to migrate a question after 60 days). You can restrict it further if desired by exposing the flag only to users with a certain reputation threshold (say, >=1,000).

13
  • 2
    I think this makes a lot of logical sense, but I also worry about the ramifications of conversions "forcing" a user to post an answer (and thus take on the "responsibility" of having that answer). "Abuse vector" isn't really the right word, but I worry about the adverse impact on contributors along the lines of getting downvotes on/ penalized for an answer they did not post. This isn't a problem with existing tooling converting in the other direction because there is essentially no penalty for "bad" (CoC-compliant) comments. Commented Apr 30 at 20:26
  • 2
    @zcoop98 in the case that it was done by non-mod, it could send the post into a state where the commenter needs to decide if they want to delete the comment, mod flag to dispute, or approve conversion to answer. Commented Apr 30 at 20:43
  • @zcoop98 I thought about that, but felt it was best to avoid going into even further detail about risks or subfeatures. Beyond just a notification that it was converted, the author would be able to unilaterally delete the answer just like they can unilaterally delete their own answers today. But it's stuck as an answer, then. I suppose you could make it a more rich experience a la what starball suggested above, but I think that complexity is unnecessary. I don't think the risk for abuse/shoehorning is too high, given appropriate restrictions on the ability of users to flag/vote for conversion. Commented Apr 30 at 20:57
  • 4
    If five different users of sufficient rep see a comment and say "hey, this should've been an answer", I think that's a good thing if it forces OP to provide an Answer if they want to... provide an answer. It would mitigate any FGITW tendencies to provide partial 'drive by' help, as well as efforts to post a true, full solution as a comment to avoid potential downvotes. I think both of those effects help achieve Stack Overflow's long-time goal of trending toward a "slow lane" (to use recent company language) of a high-quality programming Q&A repository. Commented Apr 30 at 20:59
  • @zcoop98 If people answer in comments it's most probably because they think it's not a good answer yet. If others think it is, they could provide an answer, copy the content and mark the original comment as no longer needed. I wouldn't like to have a comment force converted to an answer (or question why not) unless it's made community wiki then. Commented Apr 30 at 21:30
  • 2
    @NoDataDumpNoContribution It's a horrible workflow to have someone provide an answer in a comment, then have someone else come in and just copy that comment into an answer they have to post. That this is done at all (I have to do it often) means there's a big problem/inefficiency in what the system permits. At the end of the day, the commenter provided a response to a question, and whether the system displays it as something called a "comment" rather than something called an "answer" is largely irrelevant in terms of attribution. A response is a response. (1/2) Commented Apr 30 at 21:37
  • 1
    @NoDataDumpNoContribution The idea to allow community conversion is driven by two motivating factors, the first of which is to properly preserve authorship/attribution in converting that response from one displayed format (comment) to the other (answer). The second factor is providing a somewhat indirect form of feedback to such users that they ought to think about stopping such behavior, now that users can more directly do something about it (2/2) Commented Apr 30 at 21:38
  • 4
    That being said, I'm not opposed to the idea that such converted answers should be made Community Wiki automatically. That would only further drive home to the original author that they should consider posting their responses as proper answers in the first place if they care at all about attribution or credit/rewards such as reputation or badges. Commented Apr 30 at 21:42
  • 1
    @TylerH I did repost comments as answers in the past even from staff and it was less work than you might think. I didn't flag as NLN though. The problem I have is that posting an answer means taking responsibility for it. People who comment don't want that. You cannot force them. That will end in negative feelings. Their name would stand below an answer they never wanted to post. If the community thinks this should be an answer, the community should take the responsibility for it. Commented May 1 at 7:39
  • Often enough these comments would need some cleaning up or adding additional material to be really good anyway. If you can answer a question completely and satisfiable within the limited space and functions of a comment, something might be wrong anyway. Or what if two comments together would be needed to form one complete answer. And why not adding that comment to an existing answer if it would fit there? Often enough that would be the case. Commented May 1 at 7:43
  • What we could do already now would be: take all comments with a high score, look if they already included in answers, flag those that are as NLN, then look if the others could be included in answers, include where possible (problem: edit doesn't give (much) rep, may be rolled back), or if not possible ask comment author to consider posting their own answer and if they don't, either post own answer including it and adding stuff or create community wiki if no stuff is added, then flag for NLN. Those that are left and you aren't sure they answer the question fully, leave them be. Commented May 1 at 7:49
  • @NoDataDumpNoContribution If people don't want responsibility for a response they shouldn't post a response. Users can already delete their own answers, any time. So even without implementing something new for it, such users would already have the ability to avoid responsibility if they really wanted to. But I don't have much patience for the argument of "I don't want to be responsible for an answer, but I did want to post a response to OP that answers the question, so I decided to circumvent/misuse the system and posted a comment, instead". Commented May 1 at 15:56
  • 1
    @NoDataDumpNoContribution Regarding "What we could do already now would be: [...]" yes, I already do this, a lot. But that's not really a solution to the problem, just a way to address a symptom, and only in some cases. It may also no longer be an option if staff decides to stick with the idea that the NLN flag isn't needed. Commented May 1 at 15:59
17

It's problematic that the "Add a comment" box is at the very top, above the other comment threads (pictured below). This is encouraging people to talk without reading what has already been said, which dramatically increases the number of duplicate comments and the amount of noise.

To write this answer, I scrolled down all the way to the bottom of the page, checking all the other answers (but not their associated comments!) on the way, and then hit "OK" on a button reminding me that with >30 answers already posted here, I should make sure that I read them before adding mine. If you want to encourage follow-up questions in comments (which my other answer, in addition to several other answers here argue is not a good idea), then they should be held to the same basic standard as other posts (both questions and answers): listen to what other people have said before you speak.

This concern also applies to the "Reply" button, though an improved UI there is somewhat harder to conceive.

screenshot of the example UI from the question, showing "Add a comment" button above other comments in a thread

I understand how ironic it would be if some other answer here already mentions this, considering how obvious a flaw it is, but I doubt that such an answer could have escaped my notice.

16

Additionally, we will modify the flagging modal to disable the “no longer needed” flag type for the duration of the experiment.

Then for the duration of the experiment, I will be raising "Unfriendly or Unkind" flags on any comment that should be removed like begging for acceptance/votes, discussing votes, "thanks" comments, "I have this problem too" comments, gibberish, anything that was already addressed as an edit to the post, etc.

I can only hope I will not be flag banned for this behaviour.

13
  • 1
    Is there a reason why the Something Else option isn't sufficient for these cases? Commented Apr 28 at 17:49
  • 14
    @Hoid rhetorical: is there a reason why we don't use "something else" for everything? (Ex. the UX of people handling flags, discoverability of common flag reasons) Commented Apr 28 at 17:55
  • 12
    @Hoid yes - it requires me to type in something which is extra friction on top of the already increased extra click you want me to do to flag a comment. Even the current two clicks is a bit much for me, hence why I made myself a userscript to reduce it to 1. You want to add an extra layer, probably break my userscript in the process, and expect me to write some filler just to flag stuff that is 1. routinely cleaned up 2. clearly not fit as a comment. If you insist on making me jump through hoops, I'll instead reconsider flagging. Commented Apr 28 at 17:55
  • 1
    I mean if I got into the weeds it seems like NLN isn't an appropriate flag for, "begging for acceptance/votes, discussing votes, "thanks" comments, "I have this problem too" comments, gibberish" since they were never needed to begin with. This sounds to me like we need a different no-friction, flag reason to capture that stuff to begin with, which I can request if that resolves this particular problem. Commented Apr 28 at 18:05
  • 12
    @Hoid How about just "Not Needed" Commented Apr 28 at 18:06
  • 22
    @Hoid "since they were never needed to begin with." The flag description already captures that: "This comment is outdated, conversational, or not relevant to this post." Only "outdated" strictly falls under "no longer needed". Being conversational or irrelevant does describe the thanks, voting discussions, etc. But they are still not needed - not before and not now as well. Commented Apr 28 at 18:08
  • 12
    @Hoid We need a flag for when the thing/clarification/uncertainty the comment was made for has been fixed/applied to the answer... you know, the primary reason comments even exist... The whole point is improving the post, not sharing/creating new information. I get that you want followup questions to create new long-term information... but that doesn't eliminate the original purpose comments exist nor the need for deleting them. Commented Apr 28 at 20:03
  • 20
    @Hoid Can we please not turn this into a sematic discussion... yes, the NLN flag text has always been a problem and it's gone through many different titles but removing it without something else is a problem - please focus on that. Look at the huge volume of flags on SO - mod attention flags take much longer for mods to handle and can only be handled by mods. NLN flags can auto-delete the comment if it gets enough flags, no mod involved... and take less time for users to raise. Commented Apr 28 at 20:06
  • 30
    @Hoid We can fix that problem by simply renaming "no longer needed" with "not needed" instead of removing the flag altogether. I see you have raised zero flags across the network in your short time here. Starship, VLAZ, and I have together raised over 50,000 helpful flags, on Stack Overflow alone, over the last 10+ years; please, please listen to us (and others) when we say this flag is still needed. Commented Apr 28 at 20:13
  • 9
    This ^^ comment cannot be upvoted enough. @Hoid Please listen to people who have a decade-plus experience actually using the site's features. They're not just trying to be contrarian: they care deeply about the project and its aims, and have seen--from varied vantages--multiple trips around this merry-go-round. Commented Apr 28 at 23:13
  • 2
    Yes, regardless of the debate about how and when to flag fluff, there's a very clear need for a fast, low friction way to remove comments like "Please add details of your XYZ to your question", or "After 1.2.3 was released the solution in your answer needs XYZ", after XYZ was added. These are usually highly upvoted from when they were needed, and become highly distracting after they're not needed. There's already a lot going on in this experiment: please keep "No longer needed" and give any debate about its ideal scope and wording its own space. Commented Apr 30 at 16:15
  • 2
    Just wanted to circle back that we are discussing the feedback on this and will update the post when we come to a conclusion. We are probably gonna betweaking the flag options for the duration of the experiment. Commented Apr 30 at 21:07
  • 2
    Yeah... please don't... we definitely don't need flood of unfriendly/unkind comment flags for NLN comments. Commented May 13 at 12:47
16

Ironic Note: I had to leave this answer (feedback) for a few hours, and come back to finish it. Rather than posting a comment on someone else's answer and exploring how my ideas are a little different I've done what we're supposed to do; write my own answer. Not a duplicate answer, but one bearing some similarities to a few others.

I disagree with this part of the announcement, it lists rules to create more noise on our completed work, long finished and forgotten. It invites "me too" comments with a provisio that entitles them to pollute your comment free post that has long satisfied almost everyone for a long time, except them, now.

"What are the new acceptable commenting rules?"

"To better support an environment where discussions can take place on Q&A pairs, we are experimenting with these updated commenting guidelines on Stack Overflow for the duration of the experiment:

  • Asking specific follow-up questions about the post.
  • Seeking clarification on how an answer works or why it might not work for you.
  • Sharing variations or related experiences pertinent to the Q&A.
  • Engaging in constructive, technical discussion sparked by a question or answer, even if it explores associated concepts.

These guidelines will allow for more interaction than the traditional methodology of only using comments to improve a post or request a clarification of its intent. We want to build a space for technical exchanges.".

They should ask a new question, they can provide an attribution link to the original, and quote the specific point(s) they want help with; I'd be willing to have a setting to disable notifications when that occurs; leaving my post followup free, and excessive notification reduced.

The above reason: "Sharing variations or related experiences pertinent to the Q&A." could be OK (even useful to many) if the person simply said: "There is a similar and not duplicate question here: [provides link]".

Benefits of not making our answers (and unanswered questions) a discussion forum:

  • More Q&As, which many sites need; instead of a comment hidden away somewhere.
  • Rep for the asker, instead of being a commenter and earning nothing for a valid point.
  • Maybe a bit of pension rep for the OP, instead of a series of pings as a discussion opens up.
  • A tab for the "Newest Comments" (à la the "Newest" question tab) would be needed (and extremely active, unusable) if everyone is to be aware of the new comment; otherwise if the OP simply ignores it and then it likely gets forgotten and remains undiscovered (not replied to by others).

People on Stack Overflow might like this idea, and appreciate the opportunity to engage in this experience (I don't go there enough to speak for that site), but I don't know anywhere else that would like this; except possibly our Photography site, where after the discussion (sometimes very lengthy) everyone comes back and deletes their own comments (leaving a polished post without a lot of comments between every valuable answer).

16

Lowering the reputation limit

You mentioned that this will lead to more spam and I think this will also increase the amount of other comments that should be removed for whatever reason. How are you considering the moderation aspect of that? Are there plans to add comment mods (which got 204 upvotes and 6 downvotes), show flagged comments to 10k users (+73/-2) or something similar?

Please at least think about ways to handle the increase of unnecessary comments (including the gap left by disabling NLN but there are already sufficiently many answers on that) and tell us what you are doing.

7
  • 2
    The comment mods is on the table to be discussed. But step one after the experiment would be to determine where the dam breaks on comment spam with reputation. Then, to think about better support for moderating the possible influx of comments. Commented Apr 28 at 20:30
  • 3
    Is there an option to re-enable NLN without cancelling the experiment if it becomes necessary/it gets out of hand (not just spam)? Commented Apr 28 at 20:51
  • 7
    Yes. We are discussing alternatives internally as I write this comment. Commented Apr 28 at 20:53
  • 3
    @Hoid what does "dam breaks" mean? Commented Apr 28 at 22:23
  • 1
    @starball Presumably where/ how low the reputation gate can be set before "too much" spam comes through the proverbial dam. Figuring out where the rep-to-spam-to-participation tradeoff makes the most sense, basically. Commented Apr 29 at 15:45
  • 1
    @zcoop98 I'm trying to get at what ratio of spam to non spam comments the company's threshold of tolerance is at, and the rationale for why they would need/want to see it happen to know it's the threshold. Commented Apr 29 at 19:02
  • 3
    @starball We don't have. I would say first order of business is to determine where it departs in a meaningful way from the current reality. For example, I doubt there is to much difference in comment spam between 40 and 50, maybe the needle doesn't start to move till we hit around 15. We don't know, and even independent of everything else, we want to experiment with, knowing this is beneficial. Commented Apr 30 at 21:01
14

Should there be an explicit message to posters and commenters that the platform is still intended to be a Q&A -- not a Q&A&C?

Since I assume curators won't be able to edit other users' comment threads (only flagging), then there should be explicit guidance that ideally the commentary should be used to improve the original post (question or answer) AND the comments should be deleted by the commenters themselves after the post has been improved.

We want all of the "signal" in one coherent place with an absolute minimum of "noise". Scrolling through and expanding rambling threads is not the goal of Stack Overflow.


Tangentially, I would like it if "comments that are on-topic, professional, and beneficial to users" were used to shield curators from -1 rep penalties when downvoting posts. I would be doing a lot more vote-based curating if I wasn't penalized for it. Currently I just comment saying how the answer doesn't attempt to answer the question or provide an online demo of how the answer is provably wrong for the asked question, but don't bother to downvote because the post from 2013 already has a score of +43. Food for thought.

13

This should include improving the notifications, the follow feature, and the global inbox.

Below is a non-exhaustive list of options

  • Ignore all comment notifications, but keep edit notifications and on your own questions about getting new answers.
  • Ignore comments notifications on your specific question / answer.
  • Ignore comments notifications on a specific question
  • Ignore comments notifications on a specific answer
  • Ignore comments notifications from new users
  • Ignore comments notifications from a specific user

If, in the early stages of this experiment, notifications are not part of the heavy work, consider including at least an option to receive all or none of the notifications triggered by the new content types.

Related answers about notifications

4
  • 4
    I would love that last bullet, "Ignore comments notifications from a specific user" Commented Apr 28 at 17:05
  • 1
    If I have to choose only one, I certainly will choose that option. Commented Apr 28 at 17:05
  • 4
    We have had a few internal discussions about notification settings, and they are on our radar. However, we wanted to see if this experiment was successful in any way before discussing the settings that people might like. Commented Apr 28 at 17:18
  • 4
    @Hoid thanks for your quick reply. Please at least consider to have an "opt in" / "opt out" for getting all/none notifications from this experiment. Commented Apr 28 at 17:25
12

for the UI/Design

Please add some kind of border or styling to the comment "vote"/"reaction" and Reply buttons. It's difficult to tell now which one the button is replying to, even with the Reddit-style indentation lines. In fact it looks like this comment design is basically just pulled from the modern Reddit design, which is a very bad thing:

Screenshot of Reddit's modern comment layout

Reddit's old comment styles were much cleaner, and far better:

Screenshot of Reddit's old comment layout

GitHub's design is also much better than the sample that is shown in the announcement above, and somewhere in the middle (a happy medium, one might say) between the sample above/Reddit's modern layout and SO's current comments/Reddit's old layout:

screenshot of a GitHub comment showing reactions/votes within a comment border

While GitHub's comments aren't threaded, there is a border around the entire comment and any reactions are shown within that border. SE comments being threaded here shouldn't impact that design much/at all.


Please also make the reaction/reply buttons smaller. Why are they equal to the height of two comment lines? They should be the height of one line of text or maybe a bit more.

1
  • Also interesting to see how many indents it takes until the space for content is used up. And mobile UX. Commented Apr 29 at 21:14
12

Another answer makes an important schematic of how much unimportant information spreads across the webpage and hides the other direct answers to the original question.

I wish to add that if there were indeed important information in the now-encouraged follow-up questions in the comments, that would be just as bad. I land at Stack Exchange pages when searching Google for information. If the answer to my Google'd question were in the comments, I would not find it, since I would not dig through those conversations. That's why I never open Reddit links that show up on Google searches.

If our goal here is to build a library of information that is helpful not just to the person who asked it, but to people of the future, then this change is counterproductive. The present policy of encouraging users to go ask a new question is still the best way to go.

11

I think this experiment would be useful; but I think it should be a separate kind of thing (e.g. associated discussion – or, as Rubén points out, chat). Comments are still needed for their original purpose, as temporary post-it notes.

Removing the "no longer needed" flag suggests you're trying to introduce a radical new thing, which is fine, but beware Chesterton's fence.

3
  • 4
    We are discussing the feedback on tthe NLN flag removal will update the post once that is completed. Commented Apr 28 at 21:38
  • 1
    @Hoid since when did it become "remove" instead of "disable" as stated in the question post? Commented Apr 30 at 0:02
  • 2
    @starball In my answer (since I don't distinguish between disabling and removal); so until clarification, don't read too much into the word choice. Commented Apr 30 at 11:15

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.