5

After last night SubPost.score is now deprecated and its use will be slowly removed from the code. It has been replaced by SubPost.upvotes and SubPost.downvotes. This will allow us to implement more dynamic sorting algorithms in the near future.

Also, the implicit upvote given to a user for each one of their posts is now explicit (saved in SubPostVote).

As a result, everybody running a production instance of throat should re-build the user and post score from the SubPostVote table. I'll upload a script to do so soon.

This change might happen to SubPostComment too, since it would speed up the rendering of each comment.

After last night `SubPost.score` is now deprecated and its use will be slowly removed from the code. It has been replaced by `SubPost.upvotes` and `SubPost.downvotes`. This will allow us to implement more dynamic sorting algorithms in the near future. Also, the *implicit* upvote given to a user for each one of their posts is now explicit (saved in `SubPostVote`). As a result, everybody running a production instance of throat should re-build the user and post score from the `SubPostVote` table. I'll upload a script to do so soon. This change might happen to `SubPostComment` too, since it would speed up the rendering of each comment.

2 comments

[–] ScorpioGlitch 0 points (+0|-0)

So you're saying that every post/comment we make adds to our score.

That means that power-posting will rank you up the levels and allows spamming as an avenue to control more subs more quickly.

I don't think I like this.

[–] Polsaker [OP] 3 points (+3|-0)

So you're saying that every post/comment we make adds to our score.

Only posts, not comments.

That means that power-posting will rank you up the levels and allows spamming as an avenue to control more subs more quickly.

Well, if somebody floods the site they're bound to end up banner or downvoted so I don't think that's a problem. Besides, with the posting rate-limits and the captchas it would take a good while to reach a high level