Thanks for the detailed explanation. :-)
Now I can understand it better.
I'd be tempted to approach this as incremental changes rather than trying to find the silver bullet straight out of the gates.
I don't know if step-by-step is appropriate here. I don't want to find the ideal solution straight away, but I would like to compare how the different approaches rank.
The trending algorithm is calculated continuously (with every vote) and not just when the trending posts are requested. In this respect, changes to the trending page do not occur immediately when the code is changed. So you have to wait a few days until you see other posts on the trending page.
I had therefore considered creating a separate table in which the trending scores of the various calculations are saved so that a direct comparison could be made. For the display, however, we would then have the problem that there would also need to be a selection option for the respective trending algorithm in the Condenser. Hm, that would be more work than necessary.
When I recapitulate these thoughts now, I am inclined to simply try it with an algorithm and then see what changes in the trendings. We can then at least make a live comparison with the Steemit variant.
Could you please send me your bot list via Discord so that I can use it?
!DUBby 18%
Done and done. I do like the idea of running lots of algorithms and storing additional columns of data (which would allow a relatively quick switch (in the code) to see different attempts). Overall, this might be quicker than waiting a week at a time to implement different possible approaches.
I don't know how easy it is to add an additional database column with associated ranking algorithm though. It's one thing to think that it sounds straightforward enough but very different to implement it on Steemit's codebase 😆
Downvoting a post can decrease pending rewards and make it less visible. Common reasons:
Submit