You are viewing a single comment's thread from:
RE: [Steem Rep] Update - September 2024 | AI-Comments | Tags | Trendings Scores
To prevent the curve from rising too quickly with smaller vote numbers, I have now used log10. We'll see how the values develop.
When debugging the new function, I noticed that there is a bug in the caching wrapper that makes the caching unusable (https://github.com/steemit/hivemind/issues/338).
I would fix that now :-)
This is fascinating. First, I was able to knock a post with low numbers of votes off of your trending page just by voting for it with a small value, so that's an interesting dynamic. It actually gives an advantage to people who want to reduce a post's visibility (with low numbers of votes), and this has ramifications that I hadn't considered for alt-accounts. Not sure if that's a problem - or how big of a problem. Definitely something to be aware of, though.
Second, and more importantly, does this mean that if 10 web sites all run condenser and hivemind, they can use 10 different customized trending algorithms in order to distinguish themselves? That's a competitive dynamic that I was not aware of.
Yes, I've already done that to see how the score changes after a second (small) vote :-)
However, the influence is only apparent and only due to the fact that I recently changed the trending score calculation and that the recalculation only happens when the post or its votes have been changed.
The goal we wanted to achieve with the last change, to weaken the median with fewer votes, is thus achieved. Unfortunately, we won't be able to see for a few days whether it is really effective in comparison with other posts.
Basically yes.
Hivemind provides the trending score for the Steemit condenser. If other frontends also use the Hivemind data, they receive the same score.
There is also a calculation directly in BC Code in
tags_api).Frontend/Backend developers could also use other algorithms. For example, Steemchiller has its own trendings: