FP algorithms
-
I'm another user who would like to know how saves get to FP, with exact numbers, not approximate values.
My save, which I worked on for a whole week, got to FP with 3 upvotes, then got 2 downvotes (judging by how quickly I got this downvotes, these were haters, and I even know who they were) and left FP, after which it could not get there even with a rating +5 (and with the same 2 downvotes). Usually, saves with a +5 rating remain on FP. Does the number of downvotes or the ratio of upvotes/downvotes interfere with this, and does this mean that two or three haters can simply prevent the save from getting to FP?
-
From memory, the front page formula is simply:
log(votes) / (log(time) - 3)
Which is total votes, divided by time in thousands of seconds. If you use the json api to get the upload time, you can even calculate the exact weights of every save to see why it ranks things like it does. It doesn't take upvotes and downvotes into account separately, merely the total. For time, it uses the original upload date, not the publish date or bump date.
Saves must be less than a week old to be on front page, and also more than 17 minutes old so that the - 3 on the log doesn't make the weight negative.
Saves that are promoted are put on top via a separate process, and saves with 0 or less votes are always discarded (unless the save is featured, which also overrides the week time limit)Edited once by jacob1. Last: 24th Dec 2021 -
Are there plans to revise the algorithm?
-
Are there more interesting things you can tell us about the FP?
