7
$\begingroup$

Having seen that often newcomers (included myself when I started here) are too quick in accepting an answer, and having also seen that the reminder to wait at least 24 hours to allow a wider batch of potential answerers goes practically unnoticed, wouldn't it be better to make the capability of accepting an answer within the first 24 hours a privilege one hearns at, let's say, 1000 reputation?

In this way the benefits of waiting would become evident to any poster.

$\endgroup$
4
  • $\begingroup$ Good idea, but it depends on the SE. My experience about the SE is that your chance to reach any change in the code is practically negligible. Maybe you could try it on meta.stackexchange.com . $\endgroup$
    – Gray Sheep
    May 18, 2017 at 5:57
  • 1
    $\begingroup$ Mixing [discussion] and [feature-request] is usually not a good idea. It's better to have a [discussion] first, and if that shows a consensus for a change, then make a [feature-request] and point to the [discussion]. $\endgroup$
    – user
    May 18, 2017 at 8:43
  • 1
    $\begingroup$ I can't help but find it curious that you yourself accepted an answer within six hours of asking this question, and with less than two dozen views. :-) $\endgroup$
    – user
    May 18, 2017 at 11:10
  • $\begingroup$ @MichaelKjörling, I fully got the point of the answer I accepted $\endgroup$
    – L.Dutch Mod
    May 18, 2017 at 11:17

3 Answers 3

6
$\begingroup$

I'll add my opinion to apaul34208's that this doesn't solve any real problem, and particularly not one that justifies such a fairly drastic change. Code change complexity aside, moving a feature that has so far been available to everyone to be available only at a relatively high reputation level is a pretty drastic change, and it would leave newcomers with potentially no way to indicate that they are happy with an answer. (They wouldn't be able to vote up, offer a bounty on or accept an answer. All that would be left would be to leave a comment, but that's not what comments are for.)

It is up to the OP when, whether, and which answer to accept. For a current, somewhat extreme, example, do consider Does WannaCry infect Linux? on the Information Security SE, where the accepted answer is currently at -20 with only four upvotes, but the highest-voted answer is currently at +52 with only one downvote.

We can point out to the OP the consequences of accepting an answer early, including that it reduces the chances of them getting even better answers to their question, but if the OP feels a given answer answers their question to their satisfaction, they have every right to accept an (the) answer.

There have been proposals to make accepted answers float based solely on votes, and perhaps acceptance functioning as a tie-breaker, the way acceptance works with self-answers. Other, similar proposals have been made that are slightly different, but still accomplish the same goal of not putting so much emphasis on acceptance status. Compare e.g. Let's move some negatively scored answers from the top spot on Meta Stack Exchange.

And of course, "in this way the benefits of waiting would become evident to any poster"? You have 10k now, so you can see all the low-quality posts that pose as "answers" which are really just comments, posted as answers because commenting is not available to new users. Not to mention all the people who regularly complain about commenting not being available to new users. I think we can reasonably conclude based on experience that it doesn't work the way you posit that it does.

As much as I still feel that we should be careful about accepting answers early, limiting access to basic features of the site (which are even integral to how the site is supposed to work) is something that should also be done very carefully. Better, then, to simply point out to the OP the benefits of not accepting an answer too soon.

$\endgroup$
3
$\begingroup$

Terrible idea, what you would end up with is a bunch of questions with no accepted answer. You can't coerce the OP into doing things, he/she is here for their own needs and possibly just transient in any case.

$\endgroup$
0
$\begingroup$

Honestly the problem you're trying to solve seems negligible... As in it doesn't happen often enough to warrant a systemic change.

I know it's irritating, but it's not a major problem. People can still modify their accepted answer long after the requested 24 hours, so what problem does this solve? Truly I hate being "that guy", but sometimes I have to be... Accepted answers are fairly meaningless to anyone who's been kicking around on the network for a while, maybe I've lost perspective... Does the the check mark still matter to new-ish users? it's 15 rep, but that's a drop in the bucket toward anything meaningful.

$\endgroup$
4
  • $\begingroup$ I believe only a subset of deep diggers takes time in readying through questions which have an accepted answer. Overall it simply decreases the (potential) quality of most answers. $\endgroup$
    – L.Dutch Mod
    May 18, 2017 at 7:00
  • $\begingroup$ @L.Dutch possibly true, but we do seem to have an awful lot of answers per question here​ regardless. $\endgroup$
    – apaul
    May 18, 2017 at 7:04
  • 3
    $\begingroup$ @L.Dutch On the other hand, if the OP feels their question has been satisfactorily answered, then accepting an answer is their perogative. We can point out the consequences of this, but it's the OP's choice whether, when and what answer to accept. $\endgroup$
    – user
    May 18, 2017 at 8:42
  • $\begingroup$ @MichaelKjörling, you have a point $\endgroup$
    – L.Dutch Mod
    May 18, 2017 at 8:43

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .