4 edited body
source | link

Accepting an answer is a nice way to close the loop in site interaction but its much less important than you might think.

  This is an understandable thing to be confused about, so allow me to explain. 

Our engine registers a question as answered when an answer receives upvotes...not when the original poster clicks the “accept” button. Accepting an answer is just a social convention.

The number of accepted answers has very little influence on how well a site is developing. It provides a sense of completion for the one thread you're dealing with, but its really a form of etiquette. I don’t recommend placing too much emphasis on it. :)

Accepting an answer is a nice way to close the loop in site interaction but its much less important than you might think.

  This is an understandable thing to be confused about, so allow me to explain. Our engine registers a question as answered when an answer receives upvotes...not when the original poster clicks the “accept” button. Accepting an answer is just a social convention.

The number of accepted answers has very little influence on how well a site is developing. It provides a sense of completion for the one thread you're dealing with, but its really a form of etiquette. I don’t recommend placing too much emphasis on it. :)

Accepting an answer is a nice way to close the loop in site interaction but its much less important than you might think. This is an understandable thing to be confused about, so allow me to explain. 

Our engine registers a question as answered when an answer receives upvotes...not when the original poster clicks the “accept” button. Accepting an answer is just a social convention.

The number of accepted answers has very little influence on how well a site is developing. It provides a sense of completion for the one thread you're dealing with, but its really a form of etiquette. I don’t recommend placing too much emphasis on it. :)

3 added 3 characters in body
source | link

Accepting an answer is a nice way to close the loop in site interaction but its much less important than you might think.

This is an understandable thing to be confused about, so allow me to explain. Our engine registers a question as answered when an answer receives upvotes...not when the original poster clicks the “accept” button. Accepting an answer is just a social convention.

The number of accepted answers has very little influence on how well a site is developing. It provides a sense of completion for the one thread you're dealing with, but its really a form of etiquette. I don’t recommend placing too much emphasis on it. :)

Accepting an answer is a nice way to close the loop in site interaction but its much less important than you might think.

This is an understandable thing to be confused about, so allow me to explain. Our engine registers a question as answered when an answer receives upvotes...not when the original poster clicks the “accept” button. Accepting an answer is just a social convention.

The number of accepted answers has very little influence on how well a site is developing. It provides a sense of completion for the one thread you're dealing with, but its really a form etiquette. I don’t recommend placing too much emphasis on it. :)

Accepting an answer is a nice way to close the loop in site interaction but its much less important than you might think.

This is an understandable thing to be confused about, so allow me to explain. Our engine registers a question as answered when an answer receives upvotes...not when the original poster clicks the “accept” button. Accepting an answer is just a social convention.

The number of accepted answers has very little influence on how well a site is developing. It provides a sense of completion for the one thread you're dealing with, but its really a form of etiquette. I don’t recommend placing too much emphasis on it. :)

2 added 83 characters in body
source | link

Accepting an answer is a nice way to close the loop in site interaction but its much less important than you might think.

This is an understandable thing to be confused about, so allow me to explain. Our engine registers a question as answered when an answer receives upvotes...not when the original poster clicks the “accept” button. Accepting an answer is just a social convention.

The number of accepted answers has very little influence on how well a sites performancesite is developing. It provides a sense of completion for the one thread you're dealing with, but that's itits really a form etiquette. I don’t recommend placing too much emphasis on it. :)

Accepting an answer is a nice way to close the loop in site interaction but its much less important than you might think.

This is an understandable thing to be confused about, so allow me to explain. Our engine registers a question as answered when an answer receives upvotes...not when the original poster clicks the “accept” button. Accepting an answer is just a social convention.

The number of accepted answers has very little influence on a sites performance. It provides a sense of completion, but that's it. I don’t recommend placing too much emphasis on it.

Accepting an answer is a nice way to close the loop in site interaction but its much less important than you might think.

This is an understandable thing to be confused about, so allow me to explain. Our engine registers a question as answered when an answer receives upvotes...not when the original poster clicks the “accept” button. Accepting an answer is just a social convention.

The number of accepted answers has very little influence on how well a site is developing. It provides a sense of completion for the one thread you're dealing with, but its really a form etiquette. I don’t recommend placing too much emphasis on it. :)

1
source | link