I'm starting out on developing my first social web app, and the question of trust and credibility keeps coming up in my mind. My web app would be worthless without allowing users to input content into the system, but giving users unrestricted ability to input content would quickly fill the site with noise. I need to have a good way to identify not only spammers and users who might try to game the system, but users who may inadvertently put in noise/bad data. Likewise, I also want both the system and other users to be able to implicitly and explicitly recognize those users that should be trusted, based on the value of the content they have submitted.
I have seen the following approaches:
- voting system (e.g. Digg, HackerNews), wherein the trust is at the content item level, and the can be influenced by positive or negative voting - once the net voting passes a certain positive threshold, the content is made more visible to the community.
- feedback system (e.g. eBay), wherein the trust is at the user level and can be influenced by other users
- feature unlocking (e.g. StackOverflow, HackerNews), wherein users need to meet certain usage goals in the system in order to have access to features that are deemed to require higher trust
- human review, wherein content is submitted for approval and reviewed by an admin/maintainer user. This approach certainly doesn't scale, but may be useful in initially "seeding the system".
My post is short on details, but I'd like to keep the discussion open as possible within the ___domain of trust in a social app.
I'm looking for suggest readings, anecdotes, experiences, etc. What has worked in your app? What exactly was the problem of "trust" in your social application, and how did you solve it?
I give this presentation pretty often and am happy to get into the details with you depending on your needs.
EDIT: Jesus, I didn't realize the notes didn't make it to SlideShare. The point is that it's best to gather all the data you can, then tweak how you do it. The more obscure your public-facing metric, the more flexibility you have to adapt it as time changes.
Here's a great intro guide from Yahoo: http://developer.yahoo.com/ypatterns/parent.php?pattern=repu...