Originally created at #83

Hope that you can prioritize this so that I can start fine tuning the incentives!

I think that Wouldn't solve scenarios requiring keys or credentials would be 8 not 7 because "Wouldn't = Would not" which is what the current regex would do but that's adjustable.

We also need the ability to ignore words inside of specific tags. For example, <code>

Is it safe to assume that a html element with a score of 0 would not have its content counting for the word total count? And if the html looks like

<code>
  <p>some content</p>
</code>

then the </p> wouldn't be counted for the final word count?

Yes as I recall in the old implementation if it came across an "ignored" tag then it would count the total amount of words inside and then subtract from the net score.

In normal front-end code I would express this logic as follows:

const codes = document.querySelectorAll(`code`);
let excludedWordCount = 0;
for (const code of codes){
  excludedWordCount += getWordCount(code);
}

// ...

const netWordScore = totalWordCount - excludedWordCount;
return netWordScore;

function getWordCount(element) {
  return element.textContent.split(" ").length;
}

But ultimately it appears that we will scrap this word counting logic all together pretty soon. The more robust way to credit for productive contributions is via semantic understanding of the corpus. This will be handled by embeddings most likely.

However I do want to retain the tag/element counter because there is definitely a high correlation with high quality comments and sample images, links, and code.

So definitely need to emphasize counting tags as per the original design. The word counting is an afterthought and will be removed when we figure out a good strategy with embeddings.

@0x4007 I think what is missing from your exemple is the handling of the list of regexes, so the result should actually look like

{
  "id": 2014495969,
  "content": "Wouldn't solve scenarios requiring keys or credentials",
  "url": "https://github.com/ubiquity/cloudflare-deploy-action/issues/6#issuecomment-2014495969",
  "type": "ISSUE_ASSIGNEE",
  "score": {
    "formatting": {
      "content": {
        "p": {
          "regex": {
            "\\b\\w+\\b": {
              "wordCount": 8,
              "wordValue": 0.1
            }
          },
          "score": 1,
          "elementCount": 1
        }
      },
      "multiplier": 1
    },
    "reward": 0.54,
    "relevance": 0.3
  }
}

and the result would be:
((wordCount * wordValue) + (score * elementCount) * multiplier) * relevance
((8 * 0.1) + (1 * 1) * 1) * 0.3 = 0.54
would that be correct? Or would you apply the relevance only to the wordCount * wordValue?

Relevance should only apply to word count.

Tag count should remain unaffected. For example every image should guarantee $5

@0x4007 Here is a first shot at it, let me know if that is what you expected: Meniole#14 (comment)

If that's ok, I'll fix the tests and put the PR ready for review.

It's really hard to say from those results. It's always been difficult to understand the results based on the results table unfortunately

The applied formula is

So for the aforementioned example you described, the following happened:

So relevance is only applied to the words, and the elements have a fixed value not altered by the relevance.

So relevance is only applied to the words, and the elements have a fixed value not altered by the relevance.

Sounds good to me!