Building Web Reputation Systems
Read it now on the O’Reilly learning platform with a 10-day free trial.
O’Reilly members get unlimited access to books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
Book description
What do Amazon's product reviews, eBay's feedback score system, Slashdot's Karma System, and Xbox Live's Achievements have in common? They're all examples of successful reputation systems that enable consumer websites to manage and present user contributions most effectively. This book shows you how to design and develop reputation systems for your own sites or web applications, written by experts who have designed web communities for Yahoo! and other prominent sites.
Building Web Reputation Systems helps you ask the hard questions about these underlying mechanisms, and why they're critical for any organization that draws from or depends on user-generated content. It's a must-have for system architects, product managers, community support staff, and UI designers.
- Scale your reputation system to handle an overwhelming inflow of user contributions
- Determine the quality of contributions, and learn why some are more useful than others
- Become familiar with different models that encourage first-class contributions
- Discover tricks of moderation and how to stamp out the worst contributions quickly and efficiently
- Engage contributors and reward them in a way that gets them to return
- Examine a case study based on actual reputation deployments at industry-leading social sites, including Yahoo!, Flickr, and eBay
Show and hide more
Publisher resources
Table of contents Product information
Table of contents
- Preface
- What Is This Book About?
- Why Write a Book About Reputation?
- Who Should Read This Book
- Organization of This Book
- Part I: Reputation Defined and Illustrated
- Part II: Extended Elements and Applied Examples
- Part III: Building Web Reputation Systems
- Role-Based Reading (for Those in a Hurry)
- From Randy
- From Bryce
- 1. Reputation Systems Are Everywhere
- An Opinionated Conversation
- People Have Reputations, but So Do Things
- Reputation Takes Place Within a Context
- We Use Reputation to Make Better Decisions
- The Reputation Statement
- Explicit: Talk the Talk
- Implicit: Walk the Walk
- The Minimum Reputation Statement
- Local Reputation: It Takes a Village
- Global Reputation: Collective Intelligence
- FICO: A Study in Global Reputation and Its Challenges
- Web FICO?
- Attention Doesn’t Scale
- There’s a Whole Lotta Crap Out There
- People Are Good. Basically.
- Know thy user
- Honor creators, synthesizers, and consumers
- Throw the bums out
- The Reputation Statement and Its Components
- Reputation Sources: Who or What Is Making a Claim?
- Reputation Claims: What Is the Target’s Value to the Source? On What Scale?
- Reputation Targets: What (or Who) Is the Focus of a Claim?
- Messages and Processes
- Reputation Model Explained: Vote to Promote
- Building on the Simplest Model
- From Reputation Grammar to…
- 3. Building Blocks and Reputation Tips
- Extending the Grammar: Building Blocks
- The Data: Claim Types
- Qualitative claim types
- Text comments
- Media uploads
- Relevant external objects
- Normalized value
- Rank value
- Scalar value
- Roll-ups: Counters, accumulators, averages, mixers, and ratios
- Simple Counter
- Reversible Counter
- Simple Accumulator
- Reversible Accumulator
- Simple Average
- Reversible Average
- Mixer
- Simple Ratio
- Reversible Ratio
- Simple normalization (and weighted transform)
- Scalar denormalization
- External data transform
- Common decision process patterns
- Simple Terminator
- Simple Evaluator
- Terminating Evaluator
- Message Splitter
- Conjoint Message Delivery
- Typical inputs
- Reputation statements as input
- Periodic inputs
- Return values
- Signals: Breaking out of the reputation framework
- Logging
- The Power and Costs of Normalization
- Liquidity: You Won’t Get Enough Input
- Bias, Freshness, and Decay
- Ratings bias effects
- First-mover effects
- Freshness and decay
- Simple Models
- Favorites and Flags
- Vote to promote
- Favorites
- Report abuse
- Participation karma
- Quality karma
- Robust karma
- User Reviews with Karma
- eBay Seller Feedback Karma
- Flickr Interestingness Scores for Content Quality
- Party Crashers
- Keep Your Barn Door Closed (but Expect Peeking)
- Decay and delay
- Provide a moving target
- 5. Planning Your System’s Design
- Asking the Right Questions
- What Are Your Goals?
- User engagement
- Establishing loyalty
- Coaxing out shy advertisers
- Improving content quality
- Web 1.0: Staff creates, evaluates, and removes
- Bug report: Staff creates and evaluates, users remove
- Reviews: Staff creates and removes, users evaluate
- Surveys: Staff creates, users evaluate and remove
- Submit-publish: Users create, staff evaluates and removes
- Agents: Users create and remove, staff evaluates
- Basic social media: Users create and evaluate, staff removes
- The Full Monty: Users create, evaluate, and remove
- Predictably irrational
- Incentives and reputation
- Altruistic or sharing incentives
- Tit-for-tat and pay-it-forward incentives
- Friendship incentives
- Crusader, opinionated incentives, and know-it-all
- Direct revenue incentives
- Incentives through branding: Professional promotion
- Fulfillment incentives
- Recognition incentives
- Personal or private incentives: The quest for mastery
- What are people there to do?
- Is this a new community? Or an established one?
- The competitive spectrum
- The Objects in Your System
- Architect, Understand Thyself
- So…what does your application do?
- Perform an application audit
- People are interested in it
- The decision investment is high
- The entity has some intrinsic value worth enhancing
- The entity should persist for some length of time
- User Actions Make Good Inputs
- Explicit claims
- Implicit claims
- Emphasize quality, not simple activity
- Rate the thing, not the person
- Reward firsts, but not repetition
- Use the right scale for the job
- Match user expectations
- The ratings life cycle
- The interface design of reputation inputs
- The schizophrenic nature of stars
- Do I like you, or do I “like” like you
- Favorites, forwarding, and adding to a collection
- Favorites
- Forwarding
- Adding to a collection
- Context Is King
- Limit Scope: The Rule of Email
- Applying Scope to Yahoo! EuroSport Message Board Reputation
- The Heart of the Machine: Reputation Does Not Stand Alone
- Common Reputation Generation Mechanisms and Patterns
- Generating personalization reputation
- Generating aggregated community ratings
- Ranking large target sets (preference orders)
- Points as currency
- How to Use a Reputation: Three Questions
- Who Will See a Reputation?
- To Show or Not to Show?
- Personal Reputations: For the Owner’s Eyes Only
- Personal and Public Reputations Combined
- Public Reputations: Widely Visible
- Corporate Reputations Are Internal Use Only: Keep Them Hush-hush
- Reputation Filtering
- Reputation Ranking and Sorting
- Reputation Decisions
- Content Reputation
- Karma
- Karma is complex, built of indirect inputs
- Karma calculations are often opaque
- Display karma sparingly
- Karma caveats
- Normalized Score to Percentage
- Points and Accumulators
- Statistical Evidence
- Levels
- Numbered levels
- Named levels
- Leaderboard ranking
- Top-X ranking
- Leaderboards Considered Harmful
- What do you measure?
- Whatever you do measure will be taken way too seriously
- If it looks like a leaderboard and quacks like a leaderboard…
- Leaderboards are powerful and capricious
- Who benefits?
- Up with the Good
- Rank-Order Items in Lists and Search Results
- Content Showcases
- The human touch
- Configurable Quality Thresholds
- Expressing Dissatisfaction
- Reporting Abuse
- Who watches the watchers?
- Inferred Reputation for Content Submissions
- Just-in-time reputation calculation
- On the User Profile
- My Affiliations
- My History
- My Achievements
- Integrating with Your Application
- Implementing Your Reputation Model
- Rigging Inputs
- Applied Outputs
- Beware Feedback Loops!
- Plan for Change
- Bench Testing Reputation Models
- Environmental (Alpha) Testing Reputation Models
- Predeployment (Beta) Testing Reputation Models
- Performance: Testing scale
- Confidence: Testing computation accuracy
- Application optimization: Measuring use patterns
- Feedback: Evaluating customer’s satisfaction
- Value: Measuring ROI
- Tuning for ROI: Metrics
- Model tuning
- Application tuning
- Emergent effects and emergent defects
- Defending against emergent defects
- What Is Yahoo! Answers?
- A Marketplace for Questions and Yahoo! Answers
- Attack of the Trolls
- Time was a factor
- Location, location, location
- Setting Goals
- Cutting costs
- Cleaning up the neighborhood
- The Objects
- Limiting Scope
- An Evolving Model
- Iteration 1: Abuse reporting
- Inputs
- Mechanism and diagram
- Analysis
- Inputs
- Mechanism and diagram
- Analysis
- Inputs
- Mechanism and diagram
- Analysis
- Inputs
- Mechanism and diagram
- Analysis
- Who Will See the Reputation?
- How Will the Reputation Be Used to Modify Your Site’s Output?
- Is This Reputation for a Content Item or a Person?
- Application Integration
- Testing Is Harder Than You Think
- Lessons in Tuning: Users Protecting Their Power
- Reputation Framework Requirements
- Calculations: Static Versus Dynamic
- Static: Performance, performance, performance
- Dynamic: Reputation within social networks
- Performance at scale
- The Invisible Reputation Framework: Fast, Cheap, and Out of Control
- Requirements
- Implementation details
- Lessons learned
- Yahoo! requirements
- Yahoo! implementation details
- High-level architecture
- Messaging dispatcher
- Model execution engine
- External signaling interface
- Reputation repository
- Reputation query interface
- Recommendations for All Reputation Frameworks
- Further Reading
- Recommender Systems
- Social Incentives
- Patents
Show and hide more
Product information
- Title: Building Web Reputation Systems
- Author(s): Bryce Glass, F. Randall Farmer
- Release date: March 2010
- Publisher(s): O'Reilly Media, Inc.
- ISBN: 9780596159795