<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>Building Web Reputation Systems: The Blog</title>
    <link rel="alternate" type="text/html" href="http://buildingreputation.com/" />
    <link rel="self" type="application/atom+xml" href="http://buildingreputation.com/atom.xml" />
   <id>tag:buildingreputation.com,2010://1</id>
    <link rel="service.post" type="application/atom+xml" href="http://buildingreputation.com/writings-mt/mt-atom.cgi/weblog/blog_id=1" title="Building Web Reputation Systems: The Blog" />
    <updated>2010-07-28T03:28:52Z</updated>
    <subtitle>The companion blog by the authors (Randy Farmer and Bryce Glass) of the upcoming O&apos;Reilly book: Building Web Reputation Systems.</subtitle>
    <generator uri="http://www.sixapart.com/movabletype/">Movable Type 3.2ysb5-20051201</generator>
 
<entry>
    <title>BWRS Peer Critique - Engage!</title>
    <link rel="alternate" type="text/html" href="http://buildingreputation.com/writings/2010/07/bwrs_peer_critique_engage_1.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://buildingreputation.com/writings-mt/mt-atom.cgi/weblog/blog_id=1/entry_id=66" title="BWRS Peer Critique - Engage!" />
    <id>tag:buildingreputation.com,2010://1.66</id>
    
    <published>2010-07-28T17:39:15Z</published>
    <updated>2010-07-28T03:28:52Z</updated>
    
    <summary>Eric Goldman (@ericgoldman) recently posted a detailed and thoughtful review of Building Web Reputation Systems on his blog (and gave us on Amazon). Since his blog doesn&apos;t support comments, we&apos;ve decided to respond here with copious backlinks. If you&apos;re involved...</summary>
    <author>
        <name>randy</name>
        
    </author>
            <category term="Reputation Wednesday" />
    
    <content type="html" xml:lang="en" xml:base="http://buildingreputation.com/">
        <![CDATA[<div class="announce"><a href="http://www.ericgoldman.org">Eric Goldman</a> (<a href="http://twitter.com/ericgoldman">@ericgoldman</a>) recently posted a detailed and thoughtful <a href="http://blog.ericgoldman.org/archives/2010/07/book_review_bui.htm">review</a> of <a href="http://oreilly.com/catalog/9780596159801"><em>Building Web Reputation Systems</em></a> on his blog (and gave us <img alt="4 stars" src="http://g-ecx.images-amazon.com/images/G/01/x-locale/common/customer-reviews/stars-4-0._V192240704_.gif"/> on <a href="http://www.amazon.com/review/R3S97V94QOXLUE/ref=cm_cr_rdp_perm">Amazon</a>). Since his blog doesn't support comments, we've decided to respond here with copious backlinks. If you're involved with creating and managing reputation systems, you'll definitely want to follow Eric's writings.</div>

<p>We've received great and very positive reviews from others as well, but Eric's the first of our peers to take up the challenge of wanting more from our work. First a little about him from his <a href="http://www.ericgoldman.org/biography.html">bio</a>:<blockquote>Eric Goldman is an Associate Professor of Law at Santa Clara University School of Law. He also directs the school's High Tech Law Institute &hellip; [his] research focuses on Internet law, intellectual property, marketing, and the legal and social implications of new communication technologies &hellip;</blockquote> He also has some great presentations online, especially a recent one about <a href="http://www.ericgoldman.org/Speeches/reputationtalkspring2010.pdf">Regulating Reputation Systems</a> <a href="http://amazon.sjsu.edu/slisPod/colloquia/sp10/7goldman/collGoldmanSP10.mp3">[video]</a>. It's great work that has already influenced our thinking and even our recent public presentations. Too bad we didn't even know about Eric or his work before completing the book. This lack of a coherent way to discuss reputation systems was one of the reasons we started this effort. But, we're getting ahead of ourselves&hellip;</p>

<p>Hopefully, if you're still interested in reading this far, you've read Eric's <a	href="http://blog.ericgoldman.org/archives/2010/07/book_review_bui.htm">review</a> . Go ahead, we'll wait&mdash;this response assumes you have, so we don't have to quote a lot of context. Bryce and Randy each have thoughts to share about the issues raised, so we'll call out our responses by name below.</p>

<h2>"&hellip;a debate worth having"</h2>

<p><strong>Randy:</strong> Thank you for taking the time to write such a detailed critique. Before discussing the critical points, I really appreciate the props you give us for being the first ones to put a book together in this area, and your words of support for our experience. Hopefully it was the first of several to be contributed by many authors. As you said: "&hellip;the book provides a good repository of high-value experience-based perspectives that are not readily available elsewhere. Even if the book’s recommendations are debatable, it’s a debate worth having."</p>

<p>We asked for this debate, and you've engaged, so lets go!</p>

<h2>Not Enough Citations</h2>
<strong>Bryce:</strong>Hi Eric&mdash;thank you for the insightful critique. It is exactly this level of dialog that we'd hoped the book would inspire, and many of your points are dead-on. 

<p>In particular, calling us out for a paucity of cited references stings a<br />
bit (tho' deservedly so!) Randy and I made the decision early on that we would consciously avoid writing a 'survey' book&mdash;one focused on cataloging the various market- and academe-based approaches to reputation. </p>

<p>And, you're right, there is a deep, rich vein of prior art to be explored there&mdash;digesting all of it, and putting it into a consumer-friendly format for product and industry folks would indeed be a fantastic resource. It's just not the book we chose to write. (And the Ariely references? Yeah, I kinda feel those stick out like a sore thumb, too&mdash;we'll definitely want to leaven the text with richer references if we get a crack at a second edition. Suggestions are welcome!)</p>

<p><strong>Randy:</strong> It's tough to pick a target market for a book. Our primary experience was with product managers and web designers who were making very basic reputation system design errors. I've tried getting them to read whitepapers on ratings, reviews, reputation&mdash;and honestly it wasn't worth their time (though it should have been!) But the problem of what to cite is worse than that&mdash;the fact we were writing the very first book on the subject is a testament to how difficult it is to actually find good source material. </p>

<p>Much of your critique (and our response) is about terminology and<br />
usage in this new domain&mdash;even just doing searches is non-trivial. Heck, one of the key repositories we cite in the appendix [web.si.umich.edu/reputations/] hadn't been updated in years and now appears to be gone (or moved somewhere I can't find at the moment).</p>

<p>For example, you say "[w]e implemented a very similar system embodying these two points back in 2000-01 at Epinions"&mdash;where is this documented? Links please! (I didn't see them in your post.) If it exists, I either missed it because I didn't know the correct keywords, or it didn't get enough link-love to show up when I tried. It would have been fantastic to be able to point at proof before embarking on the uphill battle to convince Yahoo! product managers to even try allowing the users to moderate the worst-of-the-worst content.</p>

<p>I <em>so</em> look forward to the day that the stuff in our book is common-knowledge&mdash;but it isn't even close. This isn't the first new field of study I've been an early pioneer in: I'm the co-author, with Chip Morningstar, of <a href="http://www.fudco.com/chip/lessons.html"><cite>The Lesson's of Lucasfilm's Habitat</cite></a>&mdash;the first paper on creating and operating avatar virtual worlds, written in 1990 (it too was a practitioner's take on what was, up to then, a largely theory-covered field.) <cite>Lessons</cite> has been cited in over 100 books and yet there are still people building systems with the errors that Chip and I clearly identified more than 20 years ago! It's a long road we're on together.</p>

<p>BTW, Both Bryce and I would really like to own a copy of the book that Eric<br />
thinks our book could/should have been&mdash;does someone want to write it? Or is it really close to what we already have, and you&mdash;kind readers&mdash;just need to send us the links?</p>

<h2>Object Reputation vs. Grading &amp; Filtering</h2>

<p><strong>Bryce:</strong> I do take issue with one of your criticisms&mdash;your dismissal of content reputation as mere "grading and filtering" of content items, and your assertion reputation for content items "does not work." </p>

<p>You're mistaking a useful <em>application</em> of reputation (the ability to sort and promote/demote, which we cover in <a href="http://buildingreputation.com/doku.php?id=chapter_8">Chapter 8</a>) with an attribute of the object being sorted: quality, freshness, popularity, etc. These attributes are determined, of course, by community concensus and&mdash;as it turns out&mdash;there's already a pretty good term for 'a general concensus about something arrived at by a number of sources, some of them<br />
known to you and some of them not': it's reputation. </p>

<p>While it's true that certain types of content are fairly immutable, the <em>contexts</em> in which they're embedded are infinitely variable, and make reputation an invaluable way to think about, and tabulate, these attributes. </p>

<p>Let's take music as an example: an MP3 track is generally fixed and, you're correct, "does not change its character unless subsequently edited." So, perhaps (and I'm actually not willing to concede this point, but more on this later) "reputation" for one particular track may be of limited value. </p>

<p>But how about a <em>song</em>? How about a specific performance of a song? Try telling any of the contributors to <a href="http://www.deadlists.com/default.asp">The DeadLists Project</a> that 'a song is a song is a song.' They've cataloged over 40 years of concert recordings from Grateful Dead shows, and can probably tell you exactly which performances of "Stella Blue" are the superior, must-listen experiences. Different context, different expectations for reputation. </p>

<p>Further, how about a playlist&mdash;one in which songs appear and disappear over time, coming in and out of rotation? The tracks themselves don't change, but <em>collections</em> of content objects most certainly do. Tracking the reputation of a collection gives consumers valuable information to<br />
judge that asset: am I likely to like the types of songs featured here? (Google <a href="http://www.google.com/search?q=Billboard+Payola+Scandal">'Billboard Payola Scandal'</a> and then tell me that influencing content reputation hasn't historically been a very lucrative endeavor.) </p>

<p>Of course, content doesn't merely spring forth like Athena from the forehead of Zeus&mdash;no, <em>people</em> create content. So, many times, content reputation is useful as a kind of "proxy reputation" for a person (its creator). What's the best way to know an artists reputation? Why, look at how their works are received: how many downloads, how many sales, remixes, adds to playlists. These things are generally a much better indicator of an artist's impact than who they're dating or what hotel room they've trashed lately. </p>

<p>It's our contention that people and content reputation are inextricably<br />
intertwined: to even attempt to assess one in the absence of the other, would be&mdash;and for many failed startups, <em>has been</em>&mdash;an exercise in futility. </p>

<p>And, as promised, a return to your initial point: that content doesn't change over time. This is a question that goes back at least as far as Socrates and the Sophists: are the qualities of a thing intrinsic to the thing itself, or imparted instead by the context that we situate it within? I (and, generally,<br />
subsequent history, Aristotle notwithstanding) would argue the latter. </p>

<p>So, Mark Twain's <cite>Huck Finn</cite>, barring some minor edits and censored bits over the years, is indeed the same text that it's always been. But I don't think anyone would seriously argue that its reputation (our shared perception of its value, it's place in our cultural fabric) <em>hasn't</em> changed drastically over the years.</p>

<p>The exact same thing takes place, on smaller scales and with less evident effects, every time someone favorites a video on YouTube, or 'Bans' an artist from their Last.fm personal channel. </p>

<p><strong>Randy:</strong> Interesting that you call out <em>Karma</em> as a confusing term for person-reputation, I see it in a lot of white papers these days. :-) None the less, all terminology should be up for debate at this point. Sorting out entity-reputation from person-reputation is important&mdash;the naming of names is negotiable. Any counter-suggestions?</p>

<h2>Engage!</h2>

<p><strong>Randy:</strong> Again, <em>we're so grateful</em> for Eric to kickstart the debate on these important issues. As I've said to more than one dejected-looking peer "Don't be sad that I'm critical of your ideas&mdash;that<br />
means they are interesting enough to criticize! If I didn't like them, I'd just go do something else and ignore them." I'm now accepting that advice myself. Here's hoping that the issues around reputation systems remain interesting enough to continue criticism, discussion, and refinement.</p>

<p>Bryce &amp; Randy</p>

<p>Please, peers, leave comments here - if there's enough interest we're happy to move the debate to the wiki&hellip;</p>]]>
        
    </content>
</entry>
<entry>
    <title>5 Reputation Missteps [video] @Google 7/1</title>
    <link rel="alternate" type="text/html" href="http://buildingreputation.com/writings/2010/07/5_reputation_missteps_video_go.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://buildingreputation.com/writings-mt/mt-atom.cgi/weblog/blog_id=1/entry_id=60" title="5 Reputation Missteps [video] @Google 7/1" />
    <id>tag:buildingreputation.com,2010://1.60</id>
    
    <published>2010-07-13T23:59:22Z</published>
    <updated>2010-07-14T17:18:59Z</updated>
    
    <summary>I gave a solo version of the 5 Reputation Missteps (and how to avoid them) at Google as a tech-talk, and the video is up: I&apos;m afraid I don&apos;t do anywhere as well with Bryce&apos;s portions as he does, but...</summary>
    <author>
        <name>randy</name>
        
    </author>
            <category term="Best Practices" />
            <category term="Ratings" />
            <category term="Reputation Wednesday" />
            <category term="Speaking" />
            <category term="The Book" />
    
    <content type="html" xml:lang="en" xml:base="http://buildingreputation.com/">
        <![CDATA[<p>I gave a solo version of the  <a href="http://buildingreputation.com/writings/2010/05/5-reputation-missteps.html">5 Reputation Missteps (and how to avoid them)</a> at Google as a tech-talk, and the video is up:</p>

<p><object width="480" height="385"><param name="movie" value="http://www.youtube.com/v/Yn7e0J9m6rE&amp;hl=en_US&amp;fs=1"></param><param name="allowFullScreen" value="true"></param><param name="allowscriptaccess" value="always"></param><embed src="http://www.youtube.com/v/Yn7e0J9m6rE&amp;hl=en_US&amp;fs=1" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="480" height="385"></embed></object></p>

<p>I'm afraid I don't do anywhere as well with Bryce's portions as he does, but this is one of the better solo presentations I've given...</p>

<p>If you'd like Bryce and I to respond to any comments/questions you have, please leave your comments here instead of on the video - we don't get email notifications there...</p>]]>
        
    </content>
</entry>
<entry>
    <title>Bryce tonight at UX Book Club in Columbus</title>
    <link rel="alternate" type="text/html" href="http://buildingreputation.com/writings/2010/07/bryce_tonight_at_ux_book_club.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://buildingreputation.com/writings-mt/mt-atom.cgi/weblog/blog_id=1/entry_id=65" title="Bryce tonight at UX Book Club in Columbus" />
    <id>tag:buildingreputation.com,2010://1.65</id>
    
    <published>2010-07-12T18:42:12Z</published>
    <updated>2010-07-12T18:49:22Z</updated>
    
    <summary>[Original post] Time: July 12, 2010 from 7pm to 8:30pmLocation: Lextant Street: 580 North 4th Street, Suite 610 City/Town: Columbus, OH 43215 Phone: 412-519-7565 Join us in July for our next meeting of UX Book Club. We will be reading...</summary>
    <author>
        <name>randy</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://buildingreputation.com/">
        <![CDATA[<p>[<a href="http://ning.it/apOHE0">Original post]</a></p>

<p><img src="http://api.ning.com:80/files/GaIiq1qOt1zbPLDAU0mOxl3aShIPOSGFQOc6gLkGohH1p6xopbsVLLaWEyb3Cn9AA-bdT7h4E5DYZmFG-OUPIqDKlJJgrTH9/buildingwebreputationsystems.jpg" alt=""></p>

<p>Time: <a href="http://ixdacolumbus.ning.com/events/event/listByDate?date=2010-07-12">July 12, 2010</a> from 7pm to 8:30pm<br><span id="eventLocation">Location: <a href="http://ixdacolumbus.ning.com/events/event/listByLocation?location=Lextant">Lextant</a></span><br>                                            Street: <strong>580 North 4th Street, Suite 610</strong><br>                        City/Town: <strong>Columbus, OH 43215</strong><br>                                                Phone: <strong>412-519-7565</strong><br>                                      </p>

<p>Join us in July for our next meeting of UX Book Club. We will be reading "Building Web Reputation Systems" by Bryce Glass and Randy Farmer. Bryce has been kind enough to agree to join us for the meeting to discuss and answer questions about the book. It should be a great time.</p>

<p>We are moving locations to Lextant so we can support remote/virtual participants if we need to.</p>

<p>There will be free coffee.</p>

<p>We are working with Bryce to get discount codes for both the physical and ebo0k versions. Stay tuned for more details.<br />
</p>]]>
        
    </content>
</entry>
<entry>
    <title>RealID and WoW Forums: Classic Identity Design Mistake</title>
    <link rel="alternate" type="text/html" href="http://buildingreputation.com/writings/2010/07/realid_and_wow_forums_classic.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://buildingreputation.com/writings-mt/mt-atom.cgi/weblog/blog_id=1/entry_id=64" title="RealID and WoW Forums: Classic Identity Design Mistake" />
    <id>tag:buildingreputation.com,2010://1.64</id>
    
    <published>2010-07-07T23:32:51Z</published>
    <updated>2010-07-07T23:46:38Z</updated>
    
    <summary>Over on Habitat Chronicles I&apos;ve posted a rant explaining why Blizzard&apos;s new policy on using users&apos; real names on forum posts is lose-lose. It&apos;s not just a rant, I actually propose a solution. Here&apos;s a short excerpt to whet your...</summary>
    <author>
        <name>randy</name>
        
    </author>
    
    <content type="html" xml:lang="en" xml:base="http://buildingreputation.com/">
        <![CDATA[<p>Over on <a href="http://habitatchronicles.com/2010/07/realid-and-wow-forums-classic-identity-design-mistake/">Habitat Chronicles I've posted a rant</a> explaining why Blizzard's new policy on using users' real names on forum posts is lose-lose. It's not just a rant, I actually propose a solution.</p>

<p>Here's a short excerpt to whet your appetite:<br />
<blockquote><br />
The idea Blizzard has is a common initial misconception - that people will "play nice" if they have to show their real names to each other [...] and the community is responding with the longest threads in WoW history, and blog posts everywhere.<br />
[...]<br />
The Facebook-analogy of Real Identity = Quality Contributions falls apart when applied Gaming. Google + Friends + Foes + Bosses + My Real Name + The fact I have 6 80th Level Characters = Too Much Information.</p>

<p>Facebook does NOT leak this much information, and the US Senate is looking into their privacy practices.<br />
[...]<br />
In short:<br />
<ul><br />
<li>The trolls now get <em>more information to harass</em></li><br />
<li>The best players will <em>leave</em></li><br />
<li>The casual players will <em>panic</em> when they realize that their private-time activity is now public.</li><br />
</ul><br />
</blockquote></p>

<p>Read the <a href="http://habitatchronicles.com/2010/07/realid-and-wow-forums-classic-identity-design-mistake/">full post for my suggested solution</a>.</p>]]>
        
    </content>
</entry>
<entry>
    <title>Going Meta: Web Reputation Building for Building Web Reputation Systems</title>
    <link rel="alternate" type="text/html" href="http://buildingreputation.com/writings/2010/07/going_meta_web_reputation_buil.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://buildingreputation.com/writings-mt/mt-atom.cgi/weblog/blog_id=1/entry_id=63" title="Going Meta: Web Reputation Building for Building Web Reputation Systems" />
    <id>tag:buildingreputation.com,2010://1.63</id>
    
    <published>2010-07-07T18:41:28Z</published>
    <updated>2010-07-07T18:57:27Z</updated>
    
    <summary>Have you read Building Web Reputation Systems, the book, ebook, or wiki versions? If so, we&apos;d really like to read what you think, publicly, in the form of a review on any of Amazon (UK), Borders, O&apos;Reilly, or any other...</summary>
    <author>
        <name>randy</name>
        
    </author>
            <category term="Reputation Wednesday" />
    
    <content type="html" xml:lang="en" xml:base="http://buildingreputation.com/">
        <![CDATA[<p>Have you read <em>Building Web Reputation Systems</em>, the <a href="http://oreilly.com/catalog/9780596159801">book</a>, <a href="http://my.safaribooksonline.com/9781449382193">ebook</a>, or <a href="http://buildingreputation.com/doku.php">wiki </a>versions?</p>

<p>If so, we'd really like to read what you think, publicly, in the form of a review on any of<br />
<a href="http://www.amazon.com/Building-Reputation-Systems-Farmer-Randall/dp/059615979X">Amazon </a> (<a href="http://www.amazon.co.uk/Building-Reputation-Systems-Farmer-Randall/dp/059615979X">UK</a>), <a href="http://www.borders.com/online/store/TitleDetail?sku=059615979X">Borders</a>, <a href="http://oreilly.com/catalog/9780596159801">O'Reilly</a>, or any other place that you like to share feedback...</p>

<p><em>All</em> reviews are welcome, including critical ones - we're looking for more ways to improve the field and the way we communicate its subtleties. Given that the web's average star rating is 4.3, we're still too high with our <a href="http://www.amazon.com/Building-Reputation-Systems-Farmer-Randall/dp/059615979X">low-liquidity 5.0 rating at Amazon.com</a>...</p>

<p>Talk about "eating your own dog food!"</p>

<p>Thanks in advance,<br />
Bryce and Randy</p>]]>
        
    </content>
</entry>
<entry>
    <title>BuildingReputation.com Blog/Wiki excerpts translated to 华语</title>
    <link rel="alternate" type="text/html" href="http://buildingreputation.com/writings/2010/07/buildingreputationcom_blogwiki.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://buildingreputation.com/writings-mt/mt-atom.cgi/weblog/blog_id=1/entry_id=62" title="BuildingReputation.com Blog/Wiki excerpts translated to 华语" />
    <id>tag:buildingreputation.com,2010://1.62</id>
    
    <published>2010-07-02T18:21:23Z</published>
    <updated>2010-07-02T18:30:30Z</updated>
    
    <summary>There are several posts over at http://www.alienbin.com translating excerpts from this blog and the wiki version of Building Web Reputation Systems into Chinese: 来自《Building web reputation system》+ 少数本地化修改和个人见解 现实里的声誉 声誉系统在我们生活里无处不在。我们做决定的时候，如果没有足够多的参考信息（多半时候是没得的），声誉就在帮助我们做尽可能正确的决定。 If you know of any other commentaries/translations, please share them...</summary>
    <author>
        <name>randy</name>
        
    </author>
            <category term="Participation" />
    
    <content type="html" xml:lang="en" xml:base="http://buildingreputation.com/">
        <![CDATA[<p>There are several posts over at <a href="http://www.alienbin.com">http://www.alienbin.com</a> translating excerpts from this blog and the wiki version of <a href="http://oreilly.com/catalog/9780596159801"><em>Building Web Reputation Systems</em></a> into Chinese:</p>

<blockquote>来自《Building web reputation system》+ 少数本地化修改和个人见解

<p>现实里的声誉</p>

<p>声誉系统在我们生活里无处不在。我们做决定的时候，如果没有足够多的参考信息（多半时候是没得的），声誉就在帮助我们做尽可能正确的决定。<br />
</blockquote></p>

<p>If you know of any other commentaries/translations, please share them in the comments. We'd love to give them some reputation in the form of link-love.</p>]]>
        
    </content>
</entry>
<entry>
    <title>July 1 @Google - Randy presents 5 Reputation Missteps</title>
    <link rel="alternate" type="text/html" href="http://buildingreputation.com/writings/2010/06/july_1_google_randy_presents_5.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://buildingreputation.com/writings-mt/mt-atom.cgi/weblog/blog_id=1/entry_id=61" title="July 1 @Google - Randy presents 5 Reputation Missteps" />
    <id>tag:buildingreputation.com,2010://1.61</id>
    
    <published>2010-06-28T21:35:05Z</published>
    <updated>2010-06-28T21:40:15Z</updated>
    
    <summary>[This Thursday, 7/1/2010 at 1pm at Google&apos;s main campus. Please email randy.farmer@pobox.com with your name if you are not a Google employee and plan to attend, so Google security can be alerted] --- Designing a reputation system is hard. Do...</summary>
    <author>
        <name>randy</name>
        
    </author>
            <category term="Speaking" />
    
    <content type="html" xml:lang="en" xml:base="http://buildingreputation.com/">
        <![CDATA[<p>[This Thursday, 7/1/2010 at 1pm at Google's main campus. Please email randy.farmer@pobox.com with your name if you are not a Google employee and plan to attend, so Google security can be alerted]</p>

<p>---</p>

<p>Designing a reputation system is hard. Do it right, and you’re likely to draw from disciplines as disparate as computer science, sociology, user experience design and behavioral economics. Do it wrong, and you could wreak horrible downstream effects on the morale, motivations and mindset of your community.</p>

<p>We often design web reputation systems by drawing from easily-available examples on the Web, but this is an impoverished approach; it often leads the designer to settle on a design solution before they’ve properly understood the context, and framed the design problem. This is cargo-cult design at its worst, and leads to such “common sense” fallacies as…</p>

<p>    * “It’s The People, Dummy!"<br />
    * “One Reputation To Rule Them All”<br />
    * “All I Need is Five Stars"<br />
    * “Competition is Always Good”<br />
    * “Negative Karma Will Out the Bad Guys”</p>

<p>F. Randall "Randy" Farmer, one of the authors of Building Web Reputation Systems (O’Reilly, 2010) will debunk these fallacies, and a couple of others besides, drawing on real-life examples of actual deployed reputation systems from some of our industry’s biggest names: EA, Google, Yahoo! and Ebay. You might be surprised at how pervasive, and persistent, these fallacies have been through the years. But don’t worry—we’ll also tell you how to avoid falling into the same old traps!</p>

<p>---</p>

<p>[This Thursday, 7/1/2010 at 1pm at Google's main campus. Please email randy.farmer@pobox.com with your name if you are not a Google employee and plan to attend, so Google security can be alerted]<br />
</p>]]>
        
    </content>
</entry>
<entry>
    <title>Web2.0 Expo Talk — 5 Reputation Missteps</title>
    <link rel="alternate" type="text/html" href="http://buildingreputation.com/writings/2010/05/5-reputation-missteps.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://buildingreputation.com/writings-mt/mt-atom.cgi/weblog/blog_id=1/entry_id=59" title="Web2.0 Expo Talk — 5 Reputation Missteps" />
    <id>tag:buildingreputation.com,2010://1.59</id>
    
    <published>2010-05-05T14:33:34Z</published>
    <updated>2010-05-05T14:26:25Z</updated>
    
    <summary>The slides from our presentation yesterday at the Web 2.0 Expo in San Francisco. We will soon be adding all speaker&apos;s notes into the full version on Slideshare. 5 Reputation Missteps (And how to avoid them)View more presentations from Bryce...</summary>
    <author>
        <name>randy</name>
        
    </author>
            <category term="Abuse" />
            <category term="Best Practices" />
            <category term="Participation" />
            <category term="Ratings" />
            <category term="Reputation Wednesday" />
            <category term="Speaking" />
            <category term="The Book" />
    
    <content type="html" xml:lang="en" xml:base="http://buildingreputation.com/">
        <![CDATA[The slides from our presentation yesterday at the Web 2.0 Expo in San Francisco. We will soon be adding all speaker's notes into the <a href="http://www.slideshare.net/soldierant/5-reputation-missteps-and-how-to-avoid-them">full version on Slideshare</a>.

<div style="width:425px" id="__ss_3978236"><strong style="display:block;margin:12px 0 4px"><a href="http://www.slideshare.net/soldierant/5-reputation-missteps-and-how-to-avoid-them" title="5 Reputation Missteps (And how to avoid them)">5 Reputation Missteps (And how to avoid them)</a></strong><object id="__sse3978236" width="425" height="355"><param name="movie" value="http://static.slidesharecdn.com/swf/ssplayer2.swf?doc=5reputationmissteps-100505090645-phpapp02&rel=0&stripped_title=5-reputation-missteps-and-how-to-avoid-them" /><param name="allowFullScreen" value="true"/><param name="allowScriptAccess" value="always"/><embed name="__sse3978236" src="http://static.slidesharecdn.com/swf/ssplayer2.swf?doc=5reputationmissteps-100505090645-phpapp02&rel=0&stripped_title=5-reputation-missteps-and-how-to-avoid-them" type="application/x-shockwave-flash" allowscriptaccess="always" allowfullscreen="true" width="425" height="355"></embed></object><div style="padding:5px 0 12px">View more <a href="http://www.slideshare.net/">presentations</a> from <a href="http://www.slideshare.net/soldierant">Bryce Glass</a>.</div></div>]]>
        
    </content>
</entry>
<entry>
    <title>Don&apos;t Display Negative Karma Redux: Unvarnished</title>
    <link rel="alternate" type="text/html" href="http://buildingreputation.com/writings/2010/04/dont_display_negative_karma_re.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://buildingreputation.com/writings-mt/mt-atom.cgi/weblog/blog_id=1/entry_id=58" title="Don't Display Negative Karma Redux: Unvarnished" />
    <id>tag:buildingreputation.com,2010://1.58</id>
    
    <published>2010-04-06T12:56:28Z</published>
    <updated>2010-04-24T18:29:47Z</updated>
    
    <summary>It&apos;s Reputation Wednesday again, and the entire subject area of reputation systems seems to be heating up. For example there&apos;s been a lot of chatter about Unvarnished. Update 4/13/2010: The Register is reporting that an eBayer is being sued in...</summary>
    <author>
        <name>randy</name>
        
    </author>
            <category term="Best Practices" />
            <category term="In the News" />
            <category term="Reputation Wednesday" />
    
    <content type="html" xml:lang="en" xml:base="http://buildingreputation.com/">
        <![CDATA[<div class="announce">It's <a href="/writings/reputation_wednesday/">Reputation Wednesday</a> again, and the entire subject area of reputation systems seems to be heating up. For example there's been a lot of chatter about <cite>Unvarnished</cite>.</div>

<p><em><strong>Update 4/13/2010:</strong> The Register is reporting that an <a href="http://www.theregister.co.uk/2010/04/13/ebay_feedbach/">eBayer is being sued in the amount of $15,000 for leaving negative feedback</a> - more fodder for thought...</em></p>

<p>Unvarnished is a public karma system for real-world identities which will reportedly accept [and protect] negative anonymous comments, presumably from former co-workers.</p>

This has generated a lot of chatter, mostly negative from folks like Evelyn Rusli at TechCrunch:<a href="http://techcrunch.com/2010/03/30/unvarnished-a-clean-well-lighted-place-for-defamation/">Unvarnished: A Clean, Well-Lighted Place For Defamation</a>
<blockquote>
Today, Unvarnished makes its beta debut. It’s essentially Yelp for LinkedIn: any user can create an online profile for a professional and submit anonymous reviews. You can claim your profile, but unlike LinkedIn, you have to accept every post, warts and all. And once the profile is up there’s no taking it down.<br>
<br>
I asked co-founder, Peter Kazanjy, “Will you ever give users the option to take down their profile?” Kazanjy’s reply: “No, because if we did that, everyone would take their profile down” 
</blockquote>
...and... CNet's Molly Wood writes in <a href="http://news.cnet.com/8301-31322_3-20001507-256.html">Unvarnished: Person reviews or trollfest?</a><br>
<blockquote>
Because let's be clear. Though Unvarnished may be billed as a natural extension of trends that started with LinkedIn, Yelp, and even Facebook, MySpace, and message boards, there's nothing about this site that, in my opinion, doesn't lead almost immediately to rank nastiness.<br>
<br>
After a long conversation with co-founder Peter Kazanjy, formerly of VMWare, I'm convinced that the founders (the others come from eBay and LinkedIn) really do think they're creating a site that will maintain a professional veneer, be well moderated by its users, and won't descend into personal attacks. I just don't agree. 
</blockquote>
...and perhaps a bit more positive - Craig Newmark says in <a href="http://www.cnewmark.com/2010/04/trust-and-reputation-systems-redistributing-power-and-influence.html">Trust and reputation systems: redistributing power and influence</a>
<blockquote>
The most prominent experiment in directly measuring trust is Unvarnished, very recently launched in beta form. You rate what trust you have in specific individuals, and they might rate you. Unvarnished is pretty controversial, and is already attracting a lot of legal speculation. They're trying to address all the problems related to the trustworthiness of the information they receive, and if so, might become very successful. 
</blockquote>

<h2>Unvarnished Against the grain</h2>

<p>This service breaks several tenants of online karma (people reputation) as outlined in  <a href="http://oreilly.com/catalog/9780596159801">Building Web 
Reputation Systems</a> <a href="http://buildingreputation.com/doku.php"><small>(wiki)</small></a>:</p>
<ol>
<li><em>Don't Display Negative Karma!</em><a href="http://buildingreputation.com/writings/2009/10/the_dollhouse_mafia_or_why_to.html">(from The Dollhouse Mafia post)</a><br>
We said it there best: "Avoid negative public karma, really."</li>
<li><em>Karma is Complex, Built of Indirect Input</em> <a href="http://buildingreputation.com/doku.php?id=chapter_7#karma_is_complex_built_of_indirect_inputs">(Chapter 7 of our book draft)</a><br>
The reason for using indirect input is to establish a clear context of evaluation - eBay requires you complete a transaction in their system before you rate a seller. There is no way for unvarnished to tie the negative comments to an actual context (co-worker).</li>
<li><em>There is a real problem with the incentives model for all the participants (we spend one half a chapter on <a href="http://buildingreputation.com/doku.php?id=Chapter_5#incentives_for_user_participation_quality_and_moderation">incentives and motivation</a> for user generated content).</em><br>As we warn there, mixing ego-based motivation (i.e. revenge) with commercial incentives (personal brand building) is usually toxic. Unvarnished is especially problematic with the ability to leave anonymous comments. Doesn't anyone remember F*ckedCompany.com? Having been the target of comments like "Sieg Heil, Randy!" I can tell you one possible outcome for Unvarnished: Deadpool.
<li><em>Scanning our <a href="http://buildingreputation.com/writings/2010/02/on_karma.html">post summarizing Karma best practices</a> suggests quite a few places Unvarnished might want to look at closely when creating and displaying their karma.</em></li>
</ol>
<p>A colleague that worked for Wink.com, an identity aggregation site told me that they would get people angry at the fact that a profile had been assembled on their behalf on Wink, even if it was only built by a search engine&mdash;they would often demand it's removal, even though it only contained public data. Identity and privacy are sensitive topics.</p>

<p>The one thing I'm sure of, from my experience building online communities for over 35 years, the founders of Unvarnished will discover that the use-patterns will look nothing like what they've planned for or predicted. They have bitten off something in an area that is fraught with peril, and so far (in the press, at least) haven't shown any understanding how significantly different business reviews are from public user karma, especially when people's livelihoods are at stake.</p>

<p><small>[BTW, I've signed up for the beta at <http://getunvarnished.com>getunvarnished.com</a> - so if you're already a member, push the magic button that requests a review from me. :-)]</small></p>]]>
        
    </content>
</entry>
<entry>
    <title>[MIT] Online Reputation Systems: How to Design One That Does What You Need</title>
    <link rel="alternate" type="text/html" href="http://buildingreputation.com/writings/2010/04/mit_online_reputation_systems.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://buildingreputation.com/writings-mt/mt-atom.cgi/weblog/blog_id=1/entry_id=57" title="[MIT] Online Reputation Systems: How to Design One That Does What You Need" />
    <id>tag:buildingreputation.com,2010://1.57</id>
    
    <published>2010-04-02T23:57:13Z</published>
    <updated>2010-04-03T00:14:14Z</updated>
    
    <summary>There is a top-notch post on creating reputation systems over at the MIT Sloan Management Review: Online Reputation Systems: How to Design One That Does What You Need by Chrysanthos Dellarocas, an associate professor of management at Boston University School...</summary>
    <author>
        <name>randy</name>
        
    </author>
            <category term="Best Practices" />
    
    <content type="html" xml:lang="en" xml:base="http://buildingreputation.com/">
        <![CDATA[<p>There is a top-notch post on creating reputation systems over at the MIT Sloan Management Review: <a href="http://sloanreview.mit.edu/the-magazine/articles/2010/spring/51308/online-reputation-systems-how-to-design-one-that-does-what-you-need/"><em>Online Reputation Systems: How to Design One That Does What You Need</em></a> by Chrysanthos Dellarocas, an associate professor of management at Boston University School of Management and an affiliated researcher at <span class="caps">MIT'</span>s <a href="http://cci.mit.edu/">Center for Collective Intelligence</a></p>

<p>It's fairly lengthy, and aligns very closely with what we cover in greater detail in our book. Here I've excerpted <em>only</em> the section headers to peak your interest. Go <a href="http://sloanreview.mit.edu/the-magazine/articles/2010/spring/51308/online-reputation-systems-how-to-design-one-that-does-what-you-need/">read it</a>, bookmark it, and if you have an MIT Sloan account, please leave a comment. BTW, if anyone has the author's address, we'd love to send professor Dellarocas a free copy...

<blockquote>
<p>How can a website attract the contributors it needs?</p>
<ul>
<li>Key Decision #1: What are the key business objectives of your reputation system?</li>
<ul>
<li>Build Trust</li>
<li>Promote Quality</li>
<li>Facilitate Member Matching</li>
<li>Sustain Loyalty</li>
</ul>
<li>Key decision #2: What information should be included in your user’s reputation profile?</li>
<ul>
<li>Which actions are most relevant to the reputation system’s users? </li>
<li>Which user behaviors are desirable? </li>
<li>For which behaviors is it possible to obtain reliable information?</li>
</ul>
<li>Key Decision #3: How should reputation information be aggregated and displayed?<br>
Reputation mechanisms employ a variety of methods for displaying outputs. These fall into three large categories:</li>
<ul>
<li>Raw activity statistics. Examples: number of reviews posted, number of transactions completed.</li>
<li>Scores and distinctions. Examples: star ratings (such as Amazon reviews), numerical scores (eBay’s feedback score, TopCoder’s user rating), numbered levels or named member tiers (World of Warcraft’s player levels, Slashdot’s “moderator” and “meta-moderator” tiers) or achievement badges (eBay power seller, Amazon Top Reviewer).</li>
<li>Leaderboards and other methods of displaying relative user rankings. Examples: the list of top Amazon reviewers; Epinions’ author popularity ranking.</li>
</ul>
</ul>
</blockquote>]]>
        
    </content>
</entry>
<entry>
    <title>Guest Post over on CommunityGuy.com: There’s a Whole Lotta Crap Out There</title>
    <link rel="alternate" type="text/html" href="http://buildingreputation.com/writings/2010/04/guest_post_over_on_communitygu.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://buildingreputation.com/writings-mt/mt-atom.cgi/weblog/blog_id=1/entry_id=56" title="Guest Post over on CommunityGuy.com: There’s a Whole Lotta Crap Out There" />
    <id>tag:buildingreputation.com,2010://1.56</id>
    
    <published>2010-04-01T18:15:02Z</published>
    <updated>2010-04-01T18:23:34Z</updated>
    
    <summary>We&apos;ve guest posted over at CommunityGuy.com outlining a content-quality scale. Content at the higher end of the scale should be rewarded, trumpeted, and showcased. Stuff on the lower registers will either be ignored, hidden or reported to the authorities. Read...</summary>
    <author>
        <name>randy</name>
        
    </author>
            <category term="Best Practices" />
            <category term="The Book" />
    
    <content type="html" xml:lang="en" xml:base="http://buildingreputation.com/">
        <![CDATA[<p>We've guest posted over at <a href="http://www.communityguy.com/7319/guest-post-theres-a-whole-lotta-crap-out-there">CommunityGuy.com</a> outlining a content-quality scale.</p>

<center><a href="http://www.communityguy.com/7319/guest-post-theres-a-whole-lotta-crap-out-there"><img src="http://buildingreputation.com/lib/exe/fetch.php?media=Figure_1-2.png"></a>
<small><br><em>Content at the higher end of the scale should be rewarded, trumpeted, and showcased.<br>
Stuff on the lower registers will either be ignored, hidden or reported to the authorities.</em></small>
</center>

<p>Read the post <a href="http://www.communityguy.com/7319/guest-post-theres-a-whole-lotta-crap-out-there">CommunityGuy.com</a></p>
]]>
        
    </content>
</entry>
<entry>
    <title>Incentives and Behavior: Consider the Mayor</title>
    <link rel="alternate" type="text/html" href="http://buildingreputation.com/writings/2010/03/incentives_and_behavior_consid.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://buildingreputation.com/writings-mt/mt-atom.cgi/weblog/blog_id=1/entry_id=55" title="Incentives and Behavior: Consider the Mayor" />
    <id>tag:buildingreputation.com,2010://1.55</id>
    
    <published>2010-03-31T11:38:46Z</published>
    <updated>2010-03-31T14:46:21Z</updated>
    
    <summary>Are you considering an incentive system for your online community or application? There&apos;s been an overwhelming amount of attention paid lately to the ways that providing incentives—points, badges or trophies—to users can influence their behaviors and contributions. If you&apos;re already...</summary>
    <author>
        <name>Bryce Glass</name>
        <uri>http://soldierant.net</uri>
    </author>
            <category term="In the News" />
            <category term="Reputation Wednesday" />
    
    <content type="html" xml:lang="en" xml:base="http://buildingreputation.com/">
        <![CDATA[<p>Are you considering an incentive system for your online community or application? There's been an overwhelming amount of attention paid lately to the ways that providing incentives—points, badges or trophies—to users can influence their behaviors and contributions. If you're already sold, then pay careful attention to NY Mayor Michael Bloomberg's efforts to <a href="http://www.nytimes.com/2010/03/31/nyregion/31cash.html?hp">incentivize positive behaviors amongst the city's poorest residents</a>:<blockquote>An unusual and much-heralded program that gave poor families cash to encourage good behavior and self-sufficiency has so far had only modest effects on their lives and economic situation, according to an analysis the Bloomberg administration released on Tuesday.</blockquote> In the book, we caution against intermixing market and social norms (or providing external incentives in lieu of leveraging people's already-present intrinsic motivations) and it would be easy to point to NYC's experience as supporting that stance. Easy, but&mdash;perhaps&mdash;not entirely fair. As the <cite>Times</cite> article points out, the program has at least been partially succesful at lifting some citizens out of poverty. </p>

<p>It's interesting to note that one of the program's earliest failings, however, was its <em>complexity.</em> There were also problems of <em>trust</em>, <em>comprehension</em> and <em>user education</em>: <blockquote>&ldquo;I think people were confused, and there was some amount of distrust,&rdquo; Ms. Brandenburg said. &ldquo;For some people it sounded too good to be true. It took a while to explain to people what the offer was.&rdquo;</p>

<p>Ms. Gibbs said many families had been perplexed by the guidelines that were laid out for them. Cash payments were eventually eliminated for actions like getting a library card and follow-up visits with a doctor.</p>

<p>&ldquo;Too many things, too many details, more to manage in the lives of burdened, busy households,&rdquo; Ms. Gibbs said, standing next to the mayor on Tuesday. &ldquo;Big lesson for the future? Got to make it a lot more simple.&rdquo;</blockquote> These are all classic user experience problems that you, too, will wrestle with should you decide to provide incentives to influence behavior. (Hat-tip to <a href="http://twitter.com/sladner/status/11363360433">Sam Ladner</a> for the article-pointer.)</p>]]>
        
    </content>
</entry>
<entry>
    <title>Thursday 3/25 ship date for BWRS from Amazon</title>
    <link rel="alternate" type="text/html" href="http://buildingreputation.com/writings/2010/03/thursday_325_ship_date_for_bwr.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://buildingreputation.com/writings-mt/mt-atom.cgi/weblog/blog_id=1/entry_id=53" title="Thursday 3/25 ship date for BWRS from Amazon" />
    <id>tag:buildingreputation.com,2010://1.53</id>
    
    <published>2010-03-20T17:56:49Z</published>
    <updated>2010-03-29T14:35:43Z</updated>
    
    <summary>A few of our friends have shared that Amazon.com is shipping Building Web Reputation Systems this week, on Thursday 3/25/10. Bryce and I received our author&apos;s copies yesterday......</summary>
    <author>
        <name>randy</name>
        
    </author>
            <category term="The Book" />
    
    <content type="html" xml:lang="en" xml:base="http://buildingreputation.com/">
        <![CDATA[<img width="200px" src="http://farm5.static.flickr.com/4060/4448392097_d219aa85b1.jpg" align="right">A few of our friends have shared that <a href="http://www.amazon.com/Building-Reputation-Systems-Randy-Farmer/dp/059615979X/ref=pd_rhf_p_t_1">Amazon.com is shipping Building Web Reputation Systems this week</a>, on Thursday 3/25/10.

Bryce and I received our author's copies yesterday... 
]]>
        
    </content>
</entry>
<entry>
    <title>[Updated 3/31] We&apos;re presenting at Web2.0 Expo on May 4th</title>
    <link rel="alternate" type="text/html" href="http://buildingreputation.com/writings/2010/03/were_presenting_at_web20_expo.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://buildingreputation.com/writings-mt/mt-atom.cgi/weblog/blog_id=1/entry_id=52" title="[Updated 3/31] We're presenting at Web2.0 Expo on May 4th" />
    <id>tag:buildingreputation.com,2010://1.52</id>
    
    <published>2010-03-19T00:34:02Z</published>
    <updated>2010-03-31T23:40:27Z</updated>
    
    <summary>Designing Reputation Systems F. Randall Farmer (MSB Associates), Bryce Glass (Manta Media, Inc.) 2:35pm Tuesday, 05/04/2010 Location: Room 2001 Designing a reputation system is hard. Do it right, and you’re likely to draw from disciplines as disparate as computer science,...</summary>
    <author>
        <name>randy</name>
        
    </author>
            <category term="The Book" />
    
    <content type="html" xml:lang="en" xml:base="http://buildingreputation.com/">
        <![CDATA[<h1 class="summary"><a href="http://www.web2expo.com/webexsf2010/public/schedule/detail/11579">Designing Reputation Systems</a></h1>
<table><tr><td>
	<div id="schedule_detail">
		<div class="en_session_speakers">	
		<a href="http://www.web2expo.com/webexsf2010/public/schedule/speaker/73869">F. Randall Farmer</a> (MSB Associates), 
		<a href="http://www.web2expo.com/webexsf2010/public/schedule/speaker/72145">Bryce Glass</a> (Manta Media, Inc.)
</div>
<div class="session_time">2:35pm Tuesday, 05/04/2010</div>
<div class="en_session_roominfo">
<span class="en_session_room">Location: <span class="location">Room 2001</span></span>
	<span class="uf_timing">
		 <abbr class="dtstart dtstamp" title="20100504T1435"></abbr>
		 <abbr class="dtend" title="20100504T1525"></abbr>
	</span>
</div>
</td><td><img src="http://assets.en.oreilly.com/1/event/37/webexsf2010_logo.gif"></td>
</tr></table>
 <p>Designing a reputation system is hard. Do it right, and you’re likely to draw from disciplines as disparate as computer science, sociology, user experience design and behavioral economics. Do it wrong, and you could wreak horrible downstream effects on the morale, motivations and mindset of your community.</p>

	<p>We often design web reputation systems by drawing from easily-available examples on the Web, but this is an impoverished approach; it often leads the designer to settle on a design solution before they’ve properly understood the context, and framed the design <em>problem</em>. This is cargo-cult design at its worst, and leads to such “common sense” fallacies as…</p>
	<ul>
	<li>“It’s The People, Dummy!”</li>
	</ul>
	<p>When you think of reputation on the Web, do you just assume that it applies chiefly to <em>people</em>? This is only partially true. Reputation applies to <em>things</em> as well, and—in fact—it’s almost impossible to know a person’s reputation <em>without</em> evaluating the reputation of things.</p>
	<ul>
	<li>“One Reputation To Rule Them All”</li>
	</ul>
	<p>Do you think that someone’s Ebay Seller Reputation should follow them onto Facebook? Should Slashdot karma matter over on Reddit? Some very smart people have fallen victim to this fallacy: the belief that one reputation is enough to accurately convey “the measure of a man.”</p>
	<ul>
	<li>“All I Need is Five Stars”</li>
	</ul>
	<p>Ratings input mechanisms fall into, and out of, vogue. Once it was 5-Stars, then it was Digg-style upvoting, now Facebook’s ‘Like’ holds the crown. If you’re tempted to <em>start</em> with a ratings scheme in mind, and then back-design a system to justify it, proceed with caution. (Includes a bonus fallacy: “Of course I need a down-vote!”)</p>
	<ul>
	<li>“Competition is Always Good”</li>
	</ul>
	<p>Feeling inspired by game-like elements? Levels, points and leaderboards? Just make sure that they influence the <em>right</em> kind of behavior, and don’t assume a level of community competition that may, or may not, be appropriate.</p>
	<ul>
	<li>“Negative Karma Will Out the Bad Guys”</li>
	</ul>
	<p>What’s the best way to identify the bad actors in your community? Why, label them, of course! Wrong—you should employ negative karma sparingly, and <em>display</em> it almost never.</p>

	<p>The authors of Building Web Reputation Systems (O’Reilly, 2010) will debunk these fallacies, and a couple of others besides, drawing on real-life examples of actual deployed reputation systems from some of our industry’s biggest names: EA, Google, Yahoo! and Ebay. You might be surprised at how pervasive, and persistent, these fallacies have been through the years. But don’t worry—we’ll also tell you how to avoid falling into the same old traps!</p>]]>
        
    </content>
</entry>
<entry>
    <title>The first copies spotted at SWSX</title>
    <link rel="alternate" type="text/html" href="http://buildingreputation.com/writings/2010/03/the_first_copies_spotted_at_sw.html" />
    <link rel="service.edit" type="application/atom+xml" href="http://buildingreputation.com/writings-mt/mt-atom.cgi/weblog/blog_id=1/entry_id=51" title="The first copies spotted at SWSX" />
    <id>tag:buildingreputation.com,2010://1.51</id>
    
    <published>2010-03-14T22:00:16Z</published>
    <updated>2010-03-14T22:03:47Z</updated>
    
    <summary> RT @freshelectrons Building Web Reputation Systems prerelease copy driving buzz @OReillyMedia booth #yahoopress #sxsw...</summary>
    <author>
        <name>randy</name>
        
    </author>
            <category term="The Book" />
    
    <content type="html" xml:lang="en" xml:base="http://buildingreputation.com/">
        <![CDATA[<a href="http://twitter.com/freshelectrons/status/10478184916"><img src="http://farm3.static.flickr.com/2699/4432073503_78d851f1f5_m.jpg"><br>
RT @freshelectrons Building Web Reputation Systems prerelease copy driving buzz @OReillyMedia booth #yahoopress  #sxsw</a>
]]>
        
    </content>
</entry>

</feed> 

