<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Putting Recommendations on the Map -- Visualizing Clusters and Relations · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/0906.5286/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/0906.5286/feed.xml" rel="self" type="application/rss+xml" /><item><title>Putting Recommendations on the Map -- Visualizing Clusters and Relations — mentioned by repeatingbeats</title><link>https://news.ycombinator.com/item?id=978293</link><guid isPermaLink="false">urn:hackerpapers:mention:0906.5286:978293</guid><pubDate>Sat, 05 Dec 2009 17:44:31 GMT</pubDate><description>&lt;p&gt;My first guess was that they used the artist.getSimilar API method. I dug around a little and found this: &amp;quot;In April 2009, we crawled the website [last.fm] by starting with Beethoven, and the top 20 musicians most similar to Beethoven, provided that each has at least 100,000 listeners. We then found the top 20 most similar musicians to each of those with at least 100,000 listeners and proceed recursively. Our crawl yielded a graph with 2782 musicians, with edge weights the similarity between musicians.&amp;quot; - Emden Gansner, Yifan Hu, Stephen Kobourov and Chris Volinsky, Putting Recommendations on…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/0906.5286/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.IR</category></item></channel></rss>
