Check out Smess, our featured variant for February, 2025.

Enter Your Reply

The Comment You're Replying To
H. G. Muller wrote on Fri, Oct 20, 2023 12:12 PM UTC in reply to Bn Em from 10:42 AM:

I thought about this too, and also came to the conclusion that inverse linear is not ideal. Furthermore, I would like to avoid fractional scores. A possibility that occurred to me was this: everyone has a 'budget' for favoring variants, and can choose to favor a variant multiple times. To favorite a variant N times would take N squared out of his budget, though. This should be enough to discourage excessively favoring a single variant.

E.g. if we set the budget to 128 (which is enough to accomodate the situation described in a posting lower down in this topic thread), people that would want to favor only a single variant could favor it 11 times; more typical people that favor 8 variants could assign each of those 4 times (giving the 'all on one' attempt not even 3 times as much weight), and less critical people who want to favor 127 would have to do with a single favor for each of those.

This would need enhancement of the interface to also allow users to favor variants multiple times, and 'unfavor' those they favored before, in order to make room for more favored variants. If we feel it is unnecessary for a user to distinguish between variants he favors, the current interface would suffice. But in reporting the score the votes of each user would be weighted by multiplying those with a number N, which is the largest integer that, squared and multiplied by the number of variants favored by the user would not exceed 128.

To implement the latter it would only be necessary to modify the script that prepares the overview page. I don't think we would need a new 'awards program' for that. We can even have this page show both numbers: the weighted sums, (on which the variants are then sorted), as well as the number of users that contributed to this total (as it does now).

The weighted totals could be calculated in two iterations: the first one would discard all self-voting. After that it would be calculated how many weighted votes each user received, and how many self-votes this would earn him. In the second iteration the self-votes of users that did not go 'over budget' in self-voting would be counted in the weighted total.


Edit Form

Comment on the page Favorite Games

Conduct Guidelines
This is a Chess variants website, not a general forum.
Please limit your comments to Chess variants or the operation of this site.
Keep this website a safe space for Chess variant hobbyists of all stripes.
Because we want people to feel comfortable here no matter what their political or religious beliefs might be, we ask you to avoid discussing politics, religion, or other controversial subjects here. No matter how passionately you feel about any of these subjects, just take it someplace else.
Avoid Inflammatory Comments
If you are feeling anger, keep it to yourself until you calm down. Avoid insulting, blaming, or attacking someone you are angry with. Focus criticisms on ideas rather than people, and understand that criticisms of your ideas are not personal attacks and do not justify an inflammatory response.
Quick Markdown Guide

By default, new comments may be entered as Markdown, simple markup syntax designed to be readable and not look like markup. Comments stored as Markdown will be converted to HTML by Parsedown before displaying them. This follows the Github Flavored Markdown Spec with support for Markdown Extra. For a good overview of Markdown in general, check out the Markdown Guide. Here is a quick comparison of some commonly used Markdown with the rendered result:

Top level header: <H1>

Block quote

Second paragraph in block quote

First Paragraph of response. Italics, bold, and bold italics.

Second Paragraph after blank line. Here is some HTML code mixed in with the Markdown, and here is the same <U>HTML code</U> enclosed by backticks.

Secondary Header: <H2>

  • Unordered list item
  • Second unordered list item
  • New unordered list
    • Nested list item

Third Level header <H3>

  1. An ordered list item.
  2. A second ordered list item with the same number.
  3. A third ordered list item.
Here is some preformatted text.
  This line begins with some indentation.
    This begins with even more indentation.
And this line has no indentation.

Alt text for a graphic image

A definition list
A list of terms, each with one or more definitions following it.
An HTML construct using the tags <DL>, <DT> and <DD>.
A term
Its definition after a colon.
A second definition.
A third definition.
Another term following a blank line
The definition of that term.