<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" 
      xmlns:thr="http://purl.org/syndication/thread/1.0">
  <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/rethinking_recommendation_engines.php" />
  <link rel="self" type="application/atom+xml" href="http://www.readwriteweb.com/atom.xml" />
  <id>tag:,2008:/1/tag:www.readwriteweb.com,2008://1.5734-</id>
  <updated>2008-05-09T18:05:20Z</updated>
  <title>Comments for Rethinking Recommendation Engines</title>
  
  <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.1</generator>
  <entry>
    <id>tag:www.readwriteweb.com,2008://1.5734</id>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/rethinking_recommendation_engines.php" />
    <link rel="service.edit" type="application/atom+xml" href="http://www.readwriteweb.com/cgi-bin/mt/mt-atom.cgi/weblog/blog_id=1/entry_id=5734" title="Rethinking Recommendation Engines" />
    <published>2008-02-25T09:37:46Z</published>
    <updated>2008-02-25T19:28:44Z</updated>
    <title>Rethinking Recommendation Engines</title>
    <summary></summary>
    <author>
      <name>Alex Iskold</name>
      <uri>http://www.adaptiveblue.com</uri>
    </author>
    
    <category term="Trends" />
    
    <content type="html" xml:lang="en" xml:base="http://www.readwriteweb.com/">
      <![CDATA[<p><img src="http://www.readwriteweb.com/images/netflix_recommendations_feb08.jpg" />Over two years ago, Netflix announced a <a href="http://www.netflixprize.com/">Recommendation Engine contest</a> - anyone who invents an algorithm that does 10% better than
their current recommendation system will win $1 Million dollars. Many research teams raced to attack the problem, excited by
the unprecedented amount of data available. Initially quite a lot of progress was made, but then slowly
the progress stalled and now teams are stuck at around the 8.5% improvement mark.</p>]]>
      <![CDATA[<p>In this post we argue that the improvement in recommendation engines is not an algorithmic
problem, but rather a <strong>presentation issue</strong>. Respinning recommendations as <b>filters</b> and delivering them without
setting high expectations is more likely to yield progress than crunching more data faster.</p>  
<p>Building a recommendation engine is a complex endeavor, which we
<a href="http://www.readwriteweb.com/archives/recommendation_engines.php">discussed here</a> a year ago.
But in addition to being a technical challenge, there are also fundamental psychological questions: do people
want recommendations and if so, then when are they open to them? Perhaps an even bigger question is:
what happens when the user receives one or more <em>bad</em> recommendations? How tolerant will they be?</p>

<h2>Genetics of Recommendation Engines</h2>
<p>All recommendation engines are trying to solve the following problem: given a set of ratings for a particular user,
along with those of the whole user base, come up with new items that this user will like. There are many algorithms that can be
applied to the problem, but all of them focus on three elements: <strong>personal, social and fundamental</strong>:
<ul>
<li><strong>Personalized recommendation</strong> - recommend things based on the individual's past behavior</li>
<li><strong>Social recommendation</strong> - recommend things based on the past behavior of similar users</li>
<li><strong>Item recommendation</strong> - recommend things based on the item itself</li>
<li>A <strong>combination</strong> of the three approaches above</li>
</ul>
<p><img src="http://www.readwriteweb.com/images/rethink_recommendation1.jpg" align="right"> A social recommendation is also known as <strong>collaborative filtering</strong> - people who liked X also like Y. For example, people who liked
<em>Lord of The Rings</em> are likely to enjoy <em>Eragon</em> and <em>The Chronicles of Narnia</em>. The problem
 with this approach is that peoples tastes do not in reality fall into simple categories. If two people share
the same taste in fantasy movies, it does not mean that they will also both like dramas or mysteries. A good way
to think about this problem comes from genetics. Many times we meet people who have features that we recognize
and have seen in others. For example, eyes might look familiar, or lips, but it is a totally different person.</p>
<p>The other kind of recommendation is an <strong>item-based recommendation</strong>. The best example of this system is the Pandora music
recommendation service. It works by ranking each musical piece by more than 400 different characteristic - musical genes.
It then automatically matches the pieces based on these characteristics. There are challenges with tuning the algorithm to
work well, but it is also challenging to apply it to other verticals. For movies, for example, you'd need to come up
with ranking each movie along many scales, starting from director, cast, plot; and then obscure things like
musical score, locations, light, camera work, etc. It certainly can be done, but this is complicated.</p>    
<h2>The Guy In The Garage</h2>
<p><img src="http://www.readwriteweb.com/images/rethink_recommendation2.jpg" align="left">The complexity of the recommendation problem is due to its vast space of possibilities. Much like
it's hard to figure out which exact gene is responsible for a particular human trait, it is hard to figure out
which bits of the movie or music make us rate it as 5 stars. Reverse engineering human thinking is hard.
Which is exactly why one of the contestants highlighted in the Wired article is relying on a very different trick
to make his algorithm work.</p>
<p>Nicknamed <em>Guy In The Garage</em>, Gavin Potter from London is relying on human inertia. Apparently, the rating
of the movie depends on the ratings of previous movies that we just saw. For example, if you watch three movies
in a row and rate them with 4 stars, and then watch the next one which is slightly better, you will rate it 5.
Conversely, if you rate three movies in a row with 1 star, then the same movie that you would otherwise rate as 5 would
only get 4 stars from you.</p>
<p>Just when you think that this is not true, you will discover that this algorithm now sits in the 5th place and still
is making progress, while other algorithms are spinning. Enhancing formulas with a bit of human psychology is a really good idea
and this is where we turn next.</p>
<h2>Replacing Recommendations with Filters</h2>
<p><img src="http://www.readwriteweb.com/images/rethink_recommendation3.jpg" align="right">How many times has this happened to you: a friend recommended you a movie or
a restaurant, so you went there all excited - but ended up disappointed? A lot!
It is obvious that hype sets the bar high, increasing the chances of a miss.
In math speak, this kind of miss is known as a <em>false positive</em>. Consider now what would happen
if instead of recommending a movie, a friend tells that you are <em>not</em> going to like certain movie,
so do not bother renting it.</p>
<p>What bad can come of that? Not much, because likely you are not going to watch it. But even if you do
and you like it, you are not going to be experience negative feelings. This example demonstrates the difference between our
reaction to a <em>false negative</em> and a <em>false positive</em>. False positives upset us, but false negatives do not.
The idea of respinning recommendations as filters is about leveraging this phenomenon.</p>
<p>When Netflix makes recommendations, it sets itself up for a sure failure. Sooner rather than later it is going
to miss and recommend you a movie that you are not going to like. What if instead of doing that, it would show you new releases
and have a button: filter the ones I am not going to like. The algorithm is the same, but perception is different.</p>
<h2>Filters in Real-Time Culture</h2>
<p>And this idea becomes increasingly important and powerful in the age of real-time news. We are increasingly oriented
towards continuously filtering new information. We do this with our RSS Readers everyday. We think of the world in terms
of streams of news, where things of the past are not relevant. We do not need recommendations, because we are already over subscribed.
We need noise filters. An algorithm that says: 'hey, you are definitely not going to like that' and hide it.</p>
<p>If the machines can do the work of aggressively throwing information <em><strong>out</strong></em> for us, then we can deal with the rest on our own.
Borrowing from the spam box in emails, if all the tools around us had a button that said 'filter this for me', and maybe even
had a mode where such a filter is on by default, we'd all to get more things done.</p>
<h2>Conclusion</h2>
<p>Building a perfect recommendation engine is a very complex task. Regardless of the method, collaborative filtering
or inherent properties of things - recommendations are an unforgiving business, where false positives quickly turn users off.
Perhaps applying psychology to the problem can make people appreciate what these complex algorithms are doing. If instead of
recommending things, machines would filter things we definitely won't like, we might be more forgiving and understanding.</p>
<p>Now tell us please about your experiences with recommendation engines. Were there ones that worked really well?
Would you be open to filtering instead of recommendation? Besides movies and news, where would you like to have these filters?</p>    
 <p>See also our follow-up post <a href="http://www.readwriteweb.com/archives/10_recommendation_engines.php">10 Recommended Recommendation Engines</a>.</p>]]>
    </content>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2008://1.5734-comment:47604</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2008://1.5734" type="text/html" href="http://www.readwriteweb.com/archives/rethinking_recommendation_engines.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/rethinking_recommendation_engines.php#c47604" />
    <title>Comment from Dirk Olbertz on 2008-02-25</title>
    <author>
        <name>Dirk Olbertz</name>
        <uri>http://olbertz.de</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://olbertz.de">
        <![CDATA[<p>Filtering is a nice idea, because it makes more transparent what is happening. But I see recommendations as a kind of "display only a small portion of the reality".</p>

<p>If I'm looking for some movies by genre and there are a coupld of hundreds in it and I should us a filter on those, that process is not very usable.</p>

<p>But in addition to your thoughs: what about showing the recommendations, but also a link with "there are 74 movies here, that you might not like" and then show them. When we then display the reason for the negative recommendation ("your friends did not like it", or "you did not like other movies from that director", makes it perfectly transparent and helps me in choosing the right movie for me - something that I obviously will not find out, until I watched the movie, but I know that when doing the choice :-)</p>]]>
    </content>
    <published>2008-02-25T10:42:33Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2008://1.5734-comment:47605</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2008://1.5734" type="text/html" href="http://www.readwriteweb.com/archives/rethinking_recommendation_engines.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/rethinking_recommendation_engines.php#c47605" />
    <title>Comment from Data Mining and Knowledge Discovery Search Engine on 2008-02-25</title>
    <author>
        <name>Data Mining and Knowledge Discovery Search Engine</name>
        <uri>http://www.google.com/coop/cse?cx=006422944775554126616%3Aixcd3tdxkke</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.google.com/coop/cse?cx=006422944775554126616%3Aixcd3tdxkke">
        <![CDATA[<p>Data Mining and Knowledge Discovery Search Engine</p>

<p>This is a search engine all about Data Mining and Knowledge Discovery, including related International Conferences, Journals, Companies, Blogs, People, Research Institutes, softwares, products, courses, tutorials, papers, codes and etc..</p>

<p><br />
<a href="http://www.google.com/coop/cse?cx=006422944775554126616%3Aixcd3tdxkke" rel="nofollow">http://www.google.com/coop/cse?cx=006422944775554126616%3Aixcd3tdxkke</a></p>]]>
    </content>
    <published>2008-02-25T11:10:13Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2008://1.5734-comment:47606</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2008://1.5734" type="text/html" href="http://www.readwriteweb.com/archives/rethinking_recommendation_engines.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/rethinking_recommendation_engines.php#c47606" />
    <title>Comment from TS on 2008-02-25</title>
    <author>
        <name>TS</name>
        <uri>http://funkykaraoke.blogspot.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://funkykaraoke.blogspot.com">
        <![CDATA[<p>Filtering sounds like a good idea at first glance but it made me think. I feel it is potentially dangerous in term of filtering out alternative content. </p>

<p>Imagine you are a really strange subject who likes things a very little percent of other users like. A filtering engine would say ..."hah, since almost nobody likes this, most probably you won't like it too"... and you would never even see that content listed (even if it might be of interest to you).</p>

<p>Just a thought :)</p>]]>
    </content>
    <published>2008-02-25T11:13:41Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2008://1.5734-comment:47611</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2008://1.5734" type="text/html" href="http://www.readwriteweb.com/archives/rethinking_recommendation_engines.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/rethinking_recommendation_engines.php#c47611" />
    <title>Comment from Amit on 2008-02-25</title>
    <author>
        <name>Amit</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>The theory that "False positives upset us, but false negatives do not"<br />
maybe true for films, but it is not true in the general case. Imagine I'm investing in Apple stocks, than I'm willing to tolerate some news that are irrelevant about the company. But I wouldn't want to miss any story that may imply a dip in the stock price. <br />
The psychological value of false positives and false negatives is determined by the relative price (time/money/effort) one have to pay for each.   </p>]]>
    </content>
    <published>2008-02-25T11:58:29Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2008://1.5734-comment:47614</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2008://1.5734" type="text/html" href="http://www.readwriteweb.com/archives/rethinking_recommendation_engines.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/rethinking_recommendation_engines.php#c47614" />
    <title>Comment from IdeaTagger on 2008-02-25</title>
    <author>
        <name>IdeaTagger</name>
        <uri>http://www.ideatagging.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.ideatagging.com">
        <![CDATA[<p>The issue with automatic filtering is one of trust. What I have found when I use fee filters like FeedHub etc is that I keep going back to my original feeds to make sure the filters haven't missed out anything interesting - talk about addiction. Sad I know, but probably true for a lot of people. Oh and each time I do find something that the filters missed, it degrades my trust in the filters and makes me more likely to check again.</p>

<p>BTW, I think social recommendation of the "people who liked this also liked" variety is good. On the other hand, I think the "your friends liked this so you might too" kind overestimates the significance of friends. However, "your friend Joe thinks you might like this" is probably quite interesting, especially if I can set whose recommendations I am interested in and what number of such recommendations should trigger a notification to me. So on Facebook or something you would ask users "which of your friends would like this book/movie?" and use that as a basis.</p>]]>
    </content>
    <published>2008-02-25T12:40:19Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2008://1.5734-comment:47620</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2008://1.5734" type="text/html" href="http://www.readwriteweb.com/archives/rethinking_recommendation_engines.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/rethinking_recommendation_engines.php#c47620" />
    <title>Comment from preetam mukherjee on 2008-02-25</title>
    <author>
        <name>preetam mukherjee</name>
        <uri>http://weareindia.blogspot.com/</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://weareindia.blogspot.com/">
        <![CDATA[<p>Alex, </p>

<p>Thank you for highlighting an important aspect of the evolving Internet. </p>

<p>Recommendation engines typically work off a given social (+/-) contextual construct. </p>

<p>However, the dynamics of Internet hasn't scaled in the last few years. They've evolved. There have been disruptions. So while Amazon, Netflix, et al were commendable in achieving their objectives in a yester-year, we now DO need to think about recommendation engine in a very different light. </p>

<p>Three things to think about are content(nature, niche, information), audience(individuals/groups/masses, preferences, tastes, habits), and context(who, when, where..and hopefully why). </p>

<p>We're a startup out of Berkeley working on a recommendation engine for video that we've been testing out extensively. It's based on the above model, and we're focusing our efforts on personalization across the video domain.</p>

<p>"Bad recommendations" always exist. You can't have a perfect recommendation engine. What one can do is introduce learning mechanisms to understand <i>why</i> a recommendation was bad, and what a user chose in lieu of. You won't develop serious wisdom from just one observation on alternate choice, but over time/aggregated use, you'd be surprised how few those "bad recommendation" numbers become!! </p>

<p>Also, part of the problem with rec. engines is that they're mostly active-interaction based(ratings, purchases, et al). But there's a lot you could learn from passive transactions(user flow, navigation, alternate selections, de-selections...) which can be used to provide a complementary inferencing basis for your recommendations.</p>

<p>Still in stealth mode, so can't go into more detail, but hope all that helps. Let me know if I can clarify something further.</p>

<p>-p</p>]]>
    </content>
    <published>2008-02-25T13:37:45Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2008://1.5734-comment:47623</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2008://1.5734" type="text/html" href="http://www.readwriteweb.com/archives/rethinking_recommendation_engines.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/rethinking_recommendation_engines.php#c47623" />
    <title>Comment from Scott on 2008-02-25</title>
    <author>
        <name>Scott</name>
        <uri>http://www.chiefmartec.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.chiefmartec.com">
        <![CDATA[<p>Great post. This reminded me that in computer science and math proofs, one of the most successful techniques is to solve the *inverse* of the problem you're working on -- which is sometimes significantly easier -- and then exploit that result. It's a counterintuitive approach, but often very effective.</p>

<p>It's also a technique that could be used more in business brainstorming, particularly for start-ups and disruptive innovations.</p>]]>
    </content>
    <published>2008-02-25T15:35:05Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2008://1.5734-comment:47628</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2008://1.5734" type="text/html" href="http://www.readwriteweb.com/archives/rethinking_recommendation_engines.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/rethinking_recommendation_engines.php#c47628" />
    <title>Comment from p-air on 2008-02-25</title>
    <author>
        <name>p-air</name>
        <uri>http://direwolff.wordpress.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://direwolff.wordpress.com">
        <![CDATA[<p>Thanks for bringing these methods into a common context.  While I'm far fm an authority, you may have mischaractized social recommendations (or collaborative filtering) in your description if it.  Specically:</p>

<p>"For example, people who liked Lord of The Rings are likely to enjoy Eragon and The Chronicles of Narnia. The problem with this approach is that peoples tastes do not in reality fall into simple categories."</p>

<p>The collaborative filtering services that I'm familiar with are looking at this statistically.  In other words, people who liked Lord of The Rings are likely to enjoy Eragon and The Chronicles of Narnia, because others who liked Lord of The Rings also bought or rented or watched the other two movies.  It has nothing to do w/tastes.  By the same token, one could make such recommendations across categories because this is a clustering exercise that says that people who bought A, B & C also bought D, therefore if you bought A, B & C then you might also be interested in D.  When these systems don't have enough data on a specific item, they might move up a level of abstraction to a topic or interest level but that's only when the item level data isn't there.  It doesn't take long to have enough item level data to increase the precision of recommendations.</p>

<p>Not that this was the point of your write-up, but it seemed like a point worth clarifying.</p>]]>
    </content>
    <published>2008-02-25T17:14:29Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2008://1.5734-comment:47640</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2008://1.5734" type="text/html" href="http://www.readwriteweb.com/archives/rethinking_recommendation_engines.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/rethinking_recommendation_engines.php#c47640" />
    <title>Comment from preetam mukherjee on 2008-02-25</title>
    <author>
        <name>preetam mukherjee</name>
        <uri>http://weareindia.blogspot.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://weareindia.blogspot.com">
        <![CDATA[<p>good point, p-air.</p>

<p>however, "social recommendations" can be(and is) used loosely. </p>

<p>It could refer to: "your friends liked...". <br />
Or it could refer to the collaborative filtering scenario which you've outlined accurately. </p>

<p>note that collaborative systems examine tastes based on item-level data(implicit + explicit metadata), as well as using aggregate information(that's where the 'collaborative' part comes in)</p>]]>
    </content>
    <published>2008-02-25T19:46:51Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2008://1.5734-comment:47644</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2008://1.5734" type="text/html" href="http://www.readwriteweb.com/archives/rethinking_recommendation_engines.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/rethinking_recommendation_engines.php#c47644" />
    <title>Comment from Arnie on 2008-02-25</title>
    <author>
        <name>Arnie</name>
        <uri>http://www.verticalmeasures.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.verticalmeasures.com">
        <![CDATA[<p>We actually have a patented recommendation system that no one really knows about. We tried to get it out before the bubble burst but haven't done anything with it in a few years.</p>

<p>It is a ground floor patent that is basically the opposite of collaborative filtering. It correlates the items rather than the people and is incredibly accurate.  In fact, more accurate than the Netflix system - BTW... no one will win their contest either, unless they get very, very lucky. </p>

<p>If anyone reading this post is interested in acquiring or licensing our patent, contact arnie [at] cox.net.<br />
</p>]]>
    </content>
    <published>2008-02-25T20:11:23Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2008://1.5734-comment:47650</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2008://1.5734" type="text/html" href="http://www.readwriteweb.com/archives/rethinking_recommendation_engines.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/rethinking_recommendation_engines.php#c47650" />
    <title>Comment from Matt Gillooly on 2008-02-25</title>
    <author>
        <name>Matt Gillooly</name>
        <uri>http://mattgillooly.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://mattgillooly.com">
        <![CDATA[<p>To extend on Amit's point, I think a preference for false positives versus false negatives comes down to the abundance of acceptable results, and the cruciality of any individual item.</p>

<p>In the case of movies, there are many more good-enough picks than most of us will ever watch, and few of them are particularly crucial to watch.  There is little cost associated with missing one particular sure-thing, but a noticeable cost associated with letting any poor choices through.  I think most consumer entertainment/food/product recommendation problems fall into this category.</p>

<p>In the case of financial or medical info, however, there are individual items that are crucial enough to merit wading through a larger set which may contain false positives.</p>

<p>Even within a given vertical, this idea has applications to social recommendation systems.  Results from my inner circle of trusted friends could be considered more crucial than people I trust less.</p>]]>
    </content>
    <published>2008-02-25T22:03:13Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2008://1.5734-comment:47666</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2008://1.5734" type="text/html" href="http://www.readwriteweb.com/archives/rethinking_recommendation_engines.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/rethinking_recommendation_engines.php#c47666" />
    <title>Comment from Fabio De Bernardi on 2008-02-25</title>
    <author>
        <name>Fabio De Bernardi</name>
        <uri>http://www.veedow.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.veedow.com">
        <![CDATA[<p>Getting it right with recommendations is a tough job. Especially if your focus is multiple and not only movies, or book, music, etc.<br />
While applying these theories in my startup we thought about using reverse-recommendations (or false negatives) to enhance the information set delivered.<br />
It's tricky though to get it right and to let people understand that there's real information in things you shouldn't - in theory - like.<br />
Especially in social networks the aggregation of users around things they didn't like could be pretty powerful to exploit their similar traits. If then you add their interests on top of it you could come up with some pretty nice association. Of course it can't be the only aspect to consider but it could enhance the understanding of people/products/music/etc connections.</p>]]>
    </content>
    <published>2008-02-26T00:12:22Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2008://1.5734-comment:47698</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2008://1.5734" type="text/html" href="http://www.readwriteweb.com/archives/rethinking_recommendation_engines.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/rethinking_recommendation_engines.php#c47698" />
    <title>Comment from Daniel Barnett on 2008-02-25</title>
    <author>
        <name>Daniel Barnett</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>Nice idea to look at the opposite. I thought that the competition was scored on accurately predicting user ratings instead of only providing recommendations. </p>

<p>I think it would be better not to favour either recomending or filtering but simply to give the user their 'expected rating' for each movie as well as a indication of the confidence of the expected rating. Then they could do what they wanted with that information. For example</p>

<p>Movie : Jaws<br />
Average Rating : 4.2<br />
Your Expected Rating : 2.9 - 3.7 (80%)</p>

<p>Something like that.<br />
</p>]]>
    </content>
    <published>2008-02-26T07:03:49Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2008://1.5734-comment:47908</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2008://1.5734" type="text/html" href="http://www.readwriteweb.com/archives/rethinking_recommendation_engines.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/rethinking_recommendation_engines.php#c47908" />
    <title>Comment from Joe McCarthy on 2008-02-27</title>
    <author>
        <name>Joe McCarthy</name>
        <uri>http://gumption.typepad.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://gumption.typepad.com">
        <![CDATA[<p>I've tried twice to leave a trackback here from a blog post I wrote in response to this one, but did not succeed.</p>

<p>A brief summary of my post, <a href="http://gumption.typepad.com/blog/2008/02/re-rethinking-r.html" rel="nofollow">Re-rethinking Recommendation Engines: Psychology and the Influence of False Negatives</a>, is that I like the article, especially its characterization of different kinds of recommendations and its emphasis on the importance of psychological factors in technology design, but have concerns about its promotion of the acceptability of false negatives, which could reduce serendipitous discoveries and lead to more harmful consequences from overly aggressive filtering.</p>]]>
    </content>
    <published>2008-02-27T20:59:30Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2008://1.5734-comment:47934</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2008://1.5734" type="text/html" href="http://www.readwriteweb.com/archives/rethinking_recommendation_engines.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/rethinking_recommendation_engines.php#c47934" />
    <title>Comment from Yuri Syuganov on 2008-02-27</title>
    <author>
        <name>Yuri Syuganov</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>It looks for me netflix's (and few other sites, like flixster) approach is: movies are entertainment. Yes, it is for the majority of people. And they are OK with filtering out "not worth your 2 hours/10 backs" list for what currently is in movie theatres.</p>

<p>There are also less big but more demanding audience of people around for whom movies are a form of art. (And the mix of those, of course.)</p>

<p>I think recommendations those two audiences would appreciate should be based on different set of criterias. The "art lovers" don't care much about "blockbusters" lovers recommendations no matter if those are their friends or not.</p>

<p>I agree with the idea that presentation is the huge part of recommendations perception.</p>

<p>...My expectation is: the next generation recommendation system will first run an adaptive test creating user's profile and then showing not only recommended movie titles but give a clue why those were suggested (not as another link but inside the list).</p>

<p>Another thought: it's important to distinguish between "I think you'll love it" and "based on your choice it worth seeing that movie from the same director which is even better than this his latest one".</p>

<p>So adaptive test should show movie titles and produce next questions or titles to rank -- to find out "why you said you might recommend this movie to someone else".<br />
Example: my wife loves "House, M.D.". She says -- mostly because of Hugh Laurie character's personality. But at the same time she hates "A Bit of Fry and Laurie" -- for (her word) "stupidity" of those sketches. So it's not about the person H.Laurie, but about dialogs (script writer) and his acting while he's in his mid 40s. So based on someone's love to "House, M.D." we might want to find out if they'd like recommendations about other popular TV series, or TV series about doctors, or other movies Laurie played in, or other shows with smart-ass politically incorrect dialogs, or detective-type storytelling. And based on users' profiles those users recommendations (not in 5-stars scale but in 1-bit: would you or would you not recommend it because of this particular feature) will have more or less weight in computing recommendations to other users who share the same likes/dislikes -- not based on titles but on which particular things they recommended these titles for.</p>

<p>Profiling system should find out about each user how much (s)he sees and loves "art" in movies (everything that distinguish movie from literature, theatre and plain old TV); what genres he has preferences in (some don't like horror movies at all, but wouldn't mind to see one or two considered the landmarks in the genre, others hate high-school girlie stories, but will be OK to see their favorite actrees' early work); which persons (directors, actors, script writers, cameramen/cinematographers) might interest him (I'm curious about all Todd Solondz movies or all where Kristin Scott Thomas played); how omnivorous he is (I enjoyed "Shoot 'Em Up" and "Nostalghia", "When Harry met Sally" and "Death Proof" -- wouldn't be surprised if someone said those are way too different tastes -- but I liked all of them); how much he knows/saw already; etc. And questions to ask/lists of titles to present for ranking should be created not automatically but by alive persons/movie critiques to reflect the best achievements in movie-making history. And after we found that one particular person saw everything worth seeing in this genre/from this director/with this actor -- we'll need to switch from recommendations based on the fact too many people recommended this title to some rare stuff which still might interest him.</p>

<p>So based on a title I recommended I'd like to see at least:<br />
- "more titles from this director" (in back chronological order with rating from other users computed to reflect my preferences); <br />
- "more titles with this lead actor(s)" (his early years; his mature years; his best/worst movies...; his director's work); <br />
- "more titles with the similar story twist" ("she's older than him, he's a kid"; "monsters in New York, shot with handycam", "good cop/bad cop -- everyone dies at the end" -- OK, skip the last one, no spoilers); <br />
- "other pictures won the same fistival awards that year", etc.</p>

<p>So: don't try to guess what I will love. Suggest what might worth my time and list the factors why you think so.<br />
</p>]]>
    </content>
    <published>2008-02-28T02:51:09Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2008://1.5734-comment:48006</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2008://1.5734" type="text/html" href="http://www.readwriteweb.com/archives/rethinking_recommendation_engines.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/rethinking_recommendation_engines.php#c48006" />
    <title>Comment from Andrew Lee on 2008-02-28</title>
    <author>
        <name>Andrew Lee</name>
        <uri>http://www.andrewlee.com</uri>
    </author>
    <content type="html" xml:lang="en" xml:base="http://www.andrewlee.com">
        <![CDATA[<p>All of this in relation to your previous posts on the semantic web, seem to show that perhaps, the future of "intelligent agents" is not what we're interested in immediately, but rather a future where we receive a stream of information that we can click a button and filter/highlight the things that would interest us.</p>

<p>Odd, I wonder if there would be ways instead of SEO, there would be Recommendation algorithm optimization (RAO) for all different types of products.</p>]]>
    </content>
    <published>2008-02-28T23:45:12Z</published>
  </entry>

  <entry>
    <id>tag:www.readwriteweb.com,2008://1.5734-comment:48390</id>
    <thr:in-reply-to ref="tag:www.readwriteweb.com,2008://1.5734" type="text/html" href="http://www.readwriteweb.com/archives/rethinking_recommendation_engines.php"/>
    <link rel="alternate" type="text/html" href="http://www.readwriteweb.com/archives/rethinking_recommendation_engines.php#c48390" />
    <title>Comment from metropol.myopenid.com on 2008-03-05</title>
    <author>
        <name>metropol.myopenid.com</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>Hi.</p>

<p>About the <em>presentation (interaction) vs evaluation (playlist)</em> aspect of it.</p>

<p>One. It seems that, rather than the inherent or objective, computational relevance of recommended items and or ways of presenting them, what is more important is who is the <em>vehicle</em>, the recommender and how I value her, in absolute or relative terms.<br />
For example, I will value a recommendation by a person whose (movie) taste I appreciate, much more than any score a recommendation engine could provide.</p>

<p>Two. Recommendation engines can do a useful job in drastically reducing the hypothesis space, but still they don't deal with the possibly more critical aspect of how to have the user to buy (no pun intended) into some of the recommendable items. That is the interactive, argumentative aspect of a recommendation.<br />
Maybe more resources should be devoted at seeing the problems in terms of <em>what makes a good (way of) recommendation</em>, rather than what makes recommendation possible (which seems to be the focus of the common elements cited in the article).<br />
</p>]]>
    </content>
    <published>2008-03-05T08:08:08Z</published>
  </entry>

</feed>