Request

Post Reply
Security_Wiz
Posts: 53
Joined: Sat Jun 28, 2008 7:46 pm

Request

Post by Security_Wiz » Wed Oct 01, 2008 3:16 pm

Hi,

I have some suggestions. On the request section in the community page, there's always lots of them, so they tend to stay there for a month or two.

1. Not many people like posting comments. How about instead of taking it off when someone has posted a comment, why not also include ratings? For example, if someone posts a comment, it will be taken off. If some people rate the website five times instead of the comment (or you could do both) then it would be taken off.

2. The top requested website has 15 requests, meaning that it will stay there until 15 people comment on it. How about if one person comments on it, it gets taken down? Or if five people rate it?

I think those ideas would help websites get rated more instead of having 200-1000 website on the request section at a time.

Thanks!

User avatar
Sami
Posts: 3506
Joined: Sat Oct 07, 2006 11:43 am

Re: Requests

Post by Sami » Wed Oct 01, 2008 3:42 pm

You're right, the "request a comment" feature still needs some work.

1. I think the idea was to have a way to request comments, so removing the site from the list if someone rates it doesn't quite achieve the goal. I agree that we'll have to change something to make the list rotate more quickly. Having the same sites there for weeks doesn't really work for anyone.

2. It's removed from the list as soon as someone leaves a comment for the site.

If anyone has more ideas on how you'd like to see this feature work, please post your thoughts.

User avatar
Timo
Posts: 418
Joined: Sun Oct 29, 2006 5:11 pm

Re: Requests

Post by Timo » Thu Oct 02, 2008 6:33 pm

We made changes to the Request a comment -section.
The Request a comment on the scorecard is only available when the last comment is older than 30 days. Those scorecards that where on the request list and had newer comments than 30 days old have been removed from the list.

Security_Wiz
Posts: 53
Joined: Sat Jun 28, 2008 7:46 pm

Request Section

Post by Security_Wiz » Thu Oct 02, 2008 11:23 pm

Good, great ideas!

Also, if the website is currently unrated, could it be moved to the top, no matter how many requests?

User avatar
phantazm
Posts: 2486
Joined: Thu Jan 03, 2008 1:46 pm

Include time as a factor...

Post by phantazm » Fri Oct 03, 2008 12:25 am

Removing a site from the list, as the first comment arrives, is probably the simplest rule. But does it have to be a simple binary response? Surely a site with 20 requests should get more attention, than a site with only a single request..?

How about this:

1. The site moves 1 line up if a requst arrives.
2. The site moves 1 line down if comment arrives.
3. The site moves 1 line down if a day has passed.

Unneccesary requests could be diminished, if people could see how many others have already requested, rating or comment. (Why push a site up, if it's already near the top..?)


User avatar
phantazm
Posts: 2486
Joined: Thu Jan 03, 2008 1:46 pm

Actually, there are two kinds of requests...

Post by phantazm » Fri Oct 03, 2008 12:40 am

Maybe the 'request-section' should be divided in two? There are actually two kinds of requests, and a single list cannot be optimised to both at the same time. Here they are:

1. Request a quick rating consensus:
Brandnew unrated site, but another clone of an old wellknown scam operation, like Canadian Pharmacy (CP). Such scams has very short lives, so it's important to get a warning out fast. Only takes a reviewer 1 second to recognize yet another CP-clone. If others quickly join, sites would soon cross the rating threshold. Speed is important here, not discussion or precision.

2. Request slow but precise comments:
Some sites are not easily defined, borderline cases or unknown entities. Or they may be disputed, by owners or costumers. Debate and investigation may be as longwinded as it needs, as long as a clear conclusion is reached. Here speed matters not, but final precision counts.

Unneccesary requests could be diminished
Right now people requests a comment/rating, assuming there's probably none (because they can't see any). They have no idea if 17 requests already pushed the site near top. But, why not tell them, before they make a request? In some cases they would not need it then...

Post Reply

Who is online

Users browsing this forum: No registered users and 4 guests