Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Codidact Meta!

Codidact Meta is the meta-discussion site for the Codidact community network and the Codidact software. Whether you have bug reports or feature requests, support questions or rule discussions that touch the whole network – this is the site for you.

Post History

71%
+8 −2
Q&A Should we start displaying the score of a post instead of the raw votes?

I agree that on a list of questions, one clear indicator of fitness is most helpful. On a post's own page, it might make more sense to also show the up- and down-vote counts. Given that the "score,...

posted 4y ago by Isaac Moses‭  ·  edited 4y ago by Isaac Moses‭

Answer
#5: Post edited by user avatar Isaac Moses‭ · 2020-07-14T19:47:57Z (over 4 years ago)
replaced image
  • I agree that on a list of questions, one clear indicator of fitness is most helpful. On a post's own page, it might make more sense to also show the up- and down-vote counts.
  • Given that the "score," here, does not directly represent anything anyone can count, but rather is the result of plugging the up- and down-votes into a not-fully-intuitive continuous function, I think that showing the literal number that comes out of that function would be more confusing than helpful. Instead, I suggest representing it with a [Likert scale](https://en.wikipedia.org/wiki/Likert_scale), with a Help topic that provides both the formula and broad qualitative interpretations of the various scores. For example:
  • - **↓↓** (Wilson score 0 - 20%): The community has expressed a clear consensus that this **is not** a helpful post.
  • - **↓** (Wilson score 20% - 40%): There is some indication from the community that this **is not** a helpful post.
  • - **↕** (Wilson score 40% - 60%): The community hasn't expressed a clear consensus regarding how helpful this post is.
  • - **↑** (Wilson score 60% - 80%): There is some indication from the community that this **is** a helpful post.
  • - **↑↑** (Wilson score 80 - 100%): The community has expressed a clear consensus that this **is** a helpful post.
  • In place of the ASCII arrow glyphs in this example, some variation of a traditional five-level signal-strength symbol could be used, such as:
  • ![Four-level signal-strength symbol](https://meta.codidact.com/uploads/C7ARAdLMwG8rdvfDXZ1aJuCV)
  • <sup><a href="https://commons.wikimedia.org/wiki/File:WIFI_icon.svg" title="via Wikimedia Commons">Canopus49</a> / <a href="https://creativecommons.org/licenses/by-sa/3.0">CC BY-SA</a></sup>
  • I agree that on a list of questions, one clear indicator of fitness is most helpful. On a post's own page, it might make more sense to also show the up- and down-vote counts.
  • Given that the "score," here, does not directly represent anything anyone can count, but rather is the result of plugging the up- and down-votes into a not-fully-intuitive continuous function, I think that showing the literal number that comes out of that function would be more confusing than helpful. Instead, I suggest representing it with a [Likert scale](https://en.wikipedia.org/wiki/Likert_scale), with a Help topic that provides both the formula and broad qualitative interpretations of the various scores. For example:
  • - **↓↓** (Wilson score 0 - 20%): The community has expressed a clear consensus that this **is not** a helpful post.
  • - **↓** (Wilson score 20% - 40%): There is some indication from the community that this **is not** a helpful post.
  • - **↕** (Wilson score 40% - 60%): The community hasn't expressed a clear consensus regarding how helpful this post is.
  • - **↑** (Wilson score 60% - 80%): There is some indication from the community that this **is** a helpful post.
  • - **↑↑** (Wilson score 80 - 100%): The community has expressed a clear consensus that this **is** a helpful post.
  • In place of the ASCII arrow glyphs in this example, some variation of a traditional five-level signal-strength symbol could be used, such as:
  • ![Five-level signal-strength symbol](https://meta.codidact.com/uploads/i3vUsw5gpWPhhzVE8soZE6pW)
  • <sup><a href="https://freesvg.org/wi-fi-signal-silhouette">OpenClipart, Public Domain</a></sup>
#4: Post edited by user avatar Isaac Moses‭ · 2020-07-14T19:39:15Z (over 4 years ago)
  • I agree that on a list of questions, one clear indicator of fitness is most helpful. On a post's own page, it might make more sense to also show the up- and down-vote counts.
  • Given that the "score," here, does not directly represent anything anyone can count, but rather is the result of plugging the up- and down-votes into a not-fully-intuitive continuous function, I think that showing the literal number that comes out of that function would be more confusing than helpful. Instead, I suggest representing it with a [Likert scale](https://en.wikipedia.org/wiki/Likert_scale), with a Help topic that provides both the formula and broad qualitative interpretations of the various scores. For example:
  • - **↓↓** (Wilson score 0 - 20%): The community has expressed a clear consensus that this **is not** a helpful post.
  • - **↓** (Wilson score 20% - 40%): There is some indication from the community that this **is not** a helpful post.
  • - **↕** (Wilson score 40% - 60%): The community hasn't expressed a clear consensus regarding how helpful this post is.
  • - **↑** (Wilson score 60% - 80%): There is some indication from the community that this **is** a helpful post.
  • - **↑↑** (Wilson score 80 - 100%): The community has expressed a clear consensus that this **is** a helpful post.
  • In place of the ASCII arrow glyphs in this example, some variation of a traditional five-level signal-strength symbol could be used, e.g.:
  • ![Five-level signal-strength symbol](https://meta.codidact.com/uploads/C7ARAdLMwG8rdvfDXZ1aJuCV)
  • <sup><a href="https://commons.wikimedia.org/wiki/File:WIFI_icon.svg" title="via Wikimedia Commons">Canopus49</a> / <a href="https://creativecommons.org/licenses/by-sa/3.0">CC BY-SA</a></sup>
  • I agree that on a list of questions, one clear indicator of fitness is most helpful. On a post's own page, it might make more sense to also show the up- and down-vote counts.
  • Given that the "score," here, does not directly represent anything anyone can count, but rather is the result of plugging the up- and down-votes into a not-fully-intuitive continuous function, I think that showing the literal number that comes out of that function would be more confusing than helpful. Instead, I suggest representing it with a [Likert scale](https://en.wikipedia.org/wiki/Likert_scale), with a Help topic that provides both the formula and broad qualitative interpretations of the various scores. For example:
  • - **↓↓** (Wilson score 0 - 20%): The community has expressed a clear consensus that this **is not** a helpful post.
  • - **↓** (Wilson score 20% - 40%): There is some indication from the community that this **is not** a helpful post.
  • - **↕** (Wilson score 40% - 60%): The community hasn't expressed a clear consensus regarding how helpful this post is.
  • - **↑** (Wilson score 60% - 80%): There is some indication from the community that this **is** a helpful post.
  • - **↑↑** (Wilson score 80 - 100%): The community has expressed a clear consensus that this **is** a helpful post.
  • In place of the ASCII arrow glyphs in this example, some variation of a traditional five-level signal-strength symbol could be used, such as:
  • ![Four-level signal-strength symbol](https://meta.codidact.com/uploads/C7ARAdLMwG8rdvfDXZ1aJuCV)
  • <sup><a href="https://commons.wikimedia.org/wiki/File:WIFI_icon.svg" title="via Wikimedia Commons">Canopus49</a> / <a href="https://creativecommons.org/licenses/by-sa/3.0">CC BY-SA</a></sup>
#3: Post edited by user avatar Isaac Moses‭ · 2020-07-14T19:31:10Z (over 4 years ago)
  • I agree that on a list of questions, one clear indicator of fitness is most helpful. On a post's own page, it might make more sense to also show the up- and down-vote counts.
  • Given that the "score," here, does not directly represent anything anyone can count, but rather is the result of plugging the up- and down-votes into a not-fully-intuitive continuous function, I think that showing the literal number that comes out of that function would be more confusing than helpful. Instead, I suggest representing it with a [Likert scale](https://en.wikipedia.org/wiki/Likert_scale), with a Help topic that provides both the formula and broad qualitative interpretations of the various scores. For example:
  • - **↓↓** (Wilson score 0 - 20%): The community has expressed a clear consensus that this **is not** a helpful post.
  • - **↓** (Wilson score 20% - 40%): There is some indication from the community that this **is not** a helpful post.
  • - **↕** (Wilson score 40% - 60%): The community hasn't expressed a clear consensus regarding how helpful this post is.
  • - **↑** (Wilson score 60% - 80%): There is some indication from the community that this **is** a helpful post.
  • - **↑↑** (Wilson score 80 - 100%): The community has expressed a clear consensus that this **is** a helpful post.
  • I agree that on a list of questions, one clear indicator of fitness is most helpful. On a post's own page, it might make more sense to also show the up- and down-vote counts.
  • Given that the "score," here, does not directly represent anything anyone can count, but rather is the result of plugging the up- and down-votes into a not-fully-intuitive continuous function, I think that showing the literal number that comes out of that function would be more confusing than helpful. Instead, I suggest representing it with a [Likert scale](https://en.wikipedia.org/wiki/Likert_scale), with a Help topic that provides both the formula and broad qualitative interpretations of the various scores. For example:
  • - **↓↓** (Wilson score 0 - 20%): The community has expressed a clear consensus that this **is not** a helpful post.
  • - **↓** (Wilson score 20% - 40%): There is some indication from the community that this **is not** a helpful post.
  • - **↕** (Wilson score 40% - 60%): The community hasn't expressed a clear consensus regarding how helpful this post is.
  • - **↑** (Wilson score 60% - 80%): There is some indication from the community that this **is** a helpful post.
  • - **↑↑** (Wilson score 80 - 100%): The community has expressed a clear consensus that this **is** a helpful post.
  • In place of the ASCII arrow glyphs in this example, some variation of a traditional five-level signal-strength symbol could be used, e.g.:
  • ![Five-level signal-strength symbol](https://meta.codidact.com/uploads/C7ARAdLMwG8rdvfDXZ1aJuCV)
  • <sup><a href="https://commons.wikimedia.org/wiki/File:WIFI_icon.svg" title="via Wikimedia Commons">Canopus49</a> / <a href="https://creativecommons.org/licenses/by-sa/3.0">CC BY-SA</a></sup>
#2: Post edited by user avatar Isaac Moses‭ · 2020-07-14T19:22:51Z (over 4 years ago)
  • I agree that on a list of questions, one clear indicator of fitness is most helpful. On a post's own page, it might make more sense to also show the up- and down-vote counts.
  • Given that the "score," here, does not directly represent anything anyone can count, but rather is the result of plugging the up- and down-votes into a not-fully-intuitive continuous function, I think that showing the literal number that comes out of that function would be more confusing than helpful. Instead, I suggest representing it with a [Likert scale](https://en.wikipedia.org/wiki/Likert_scale), with a Help topic that provides both the calculation and broad qualitative interpretations of the various scores. For example:
  • - **↓↓** (Wilson score 0 - 20%): The community has expressed a clear consensus that this **is not** a helpful post.
  • - **↓** (Wilson score 20% - 40%): There is some indication from the community that this **is not** a helpful post.
  • - **↕** (Wilson score 40% - 60%): The community hasn't expressed a clear consensus regarding how helpful this post is.
  • - **↑** (Wilson score 60% - 80%): There is some indication from the community that this **is** a helpful post.
  • - **↑↑** (Wilson score 80 - 100%): The community has expressed a clear consensus that this **is** a helpful post.
  • I agree that on a list of questions, one clear indicator of fitness is most helpful. On a post's own page, it might make more sense to also show the up- and down-vote counts.
  • Given that the "score," here, does not directly represent anything anyone can count, but rather is the result of plugging the up- and down-votes into a not-fully-intuitive continuous function, I think that showing the literal number that comes out of that function would be more confusing than helpful. Instead, I suggest representing it with a [Likert scale](https://en.wikipedia.org/wiki/Likert_scale), with a Help topic that provides both the formula and broad qualitative interpretations of the various scores. For example:
  • - **↓↓** (Wilson score 0 - 20%): The community has expressed a clear consensus that this **is not** a helpful post.
  • - **↓** (Wilson score 20% - 40%): There is some indication from the community that this **is not** a helpful post.
  • - **↕** (Wilson score 40% - 60%): The community hasn't expressed a clear consensus regarding how helpful this post is.
  • - **↑** (Wilson score 60% - 80%): There is some indication from the community that this **is** a helpful post.
  • - **↑↑** (Wilson score 80 - 100%): The community has expressed a clear consensus that this **is** a helpful post.
#1: Initial revision by user avatar Isaac Moses‭ · 2020-07-14T19:21:52Z (over 4 years ago)
I agree that on a list of questions, one clear indicator of fitness is most helpful. On a post's own page, it might make more sense to also show the up- and down-vote counts.

Given that the "score," here, does not directly represent anything anyone can count, but rather is the result of plugging the up- and down-votes into a not-fully-intuitive continuous function, I think that showing the literal number that comes out of that function would be more confusing than helpful. Instead, I suggest representing it with a [Likert scale](https://en.wikipedia.org/wiki/Likert_scale), with a Help topic that provides both the calculation and broad qualitative interpretations of the various scores. For example:

- **↓↓** (Wilson score 0 - 20%): The community has expressed a clear consensus that this **is not** a helpful post.

- **↓** (Wilson score 20% - 40%): There is some indication from the community that this **is not** a helpful post.

- **↕** (Wilson score 40% - 60%): The community hasn't expressed a clear consensus regarding how helpful this post is.

- **↑** (Wilson score 60% - 80%): There is some indication from the community that this **is** a helpful post.

- **↑↑** (Wilson score 80 - 100%): The community has expressed a clear consensus that this **is** a helpful post.