-
Notifications
You must be signed in to change notification settings - Fork 2.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reviews and voting #14
Comments
A more useful default sort might be the number of upvotes, that way a customer sees the most "valuable" opinions most prominently. Perhaps using recency as a secondary sort for the situation where none of the reviews have votes yet. |
Good idea. We should make that an additional option as well as sorting by score and recency. |
Are we going to handle spamminess in any other way than moderation? On high volume sites this will be a royal pain in the arse. |
Building on top of that - an even more useful sort would be a replication of the reddit one, as in - take time into account. A review from 3 years ago should not be as useful as one from last week. It's simple enough to do with a variable water-down constant and a bit of log. |
@djm's idea is a good one. Once the basic reviews are done, we should write that one up as an enhancement ticket. @kura - Spamminess is not something we've had to contend to date. One option would be Akismet or something like that but that it's paid-for for commercial apps. But I think it's too soon for this kind of feature. Maybe in a few months... |
https://gist.github.com/4645a5f6591253bd9ed1 If you wanted to use it, I've already recreated it and that works brilliantly. The brilliance about the reddit algo is that it is not resource-intensive as the "score" of a certain object is only recalculated and saved on the object when a vote takes place. That way the ordering of the result set is simply by number. |
Does this: http://blog.linkibol.com/resource/reddit.PNG |
Thanks everyone for your inputs. Although reddit's algorithm takes the recency of a vote into account it has not considered spamming as an issue (which we have to face sooner or later). I was trying to find something that takes care of spams algorithmically and found this interesting review paper: http://portal.acm.org/citation.cfm?id=1216307 I also personally prefer to show a diverse set of items which are not just popular items. That in turn reduces the risk of over/under rating an item by spammers or otherwise. Such algorithms are also available. Here is a review of few of them |
I think we're trying to run before we can walk. We're not going to have 1000s of reviews for a while so I suggest we just get the basics of reviewing and voting implemented now. We can worry about spam and clever sorting algorithms later on, YAGNI principle and all that. For now, just go with sorting by date and number of votes. |
We have had reviews for a while now. Closing as outdated. |
Create a new
oscar.reviews
app which provides reviews and voting functionality.OSCAR_ALLOW_ANON_REVIEWS
is set to true - it should default to false.OSCAR_MODERATE_REVIEWS
is set to false, then they don't need moderation.
It might be possible to use the Django comments framework for this.
The text was updated successfully, but these errors were encountered: