<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Accounting for page popularity</title>
	<atom:link href="http://blog.jonudell.net/2007/06/26/accounting-for-page-popularity/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.jonudell.net/2007/06/26/accounting-for-page-popularity/</link>
	<description>Strategies for Internet citizens</description>
	<lastBuildDate>Sun, 12 Feb 2012 18:22:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Steve Champagne</title>
		<link>http://blog.jonudell.net/2007/06/26/accounting-for-page-popularity/#comment-34362</link>
		<dc:creator><![CDATA[Steve Champagne]]></dc:creator>
		<pubDate>Wed, 27 Jun 2007 18:46:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jonudell.net/2007/06/26/accounting-for-page-popularity/#comment-34362</guid>
		<description><![CDATA[Google shouldn&#039;t be apologizing for content that isn&#039;t their own to begin with. But if they feel they must, the apology should general, not preferential to one word. Certainly anti-semites would see the cited apology as nothing short of pandering.]]></description>
		<content:encoded><![CDATA[<p>Google shouldn&#8217;t be apologizing for content that isn&#8217;t their own to begin with. But if they feel they must, the apology should general, not preferential to one word. Certainly anti-semites would see the cited apology as nothing short of pandering.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Udell</title>
		<link>http://blog.jonudell.net/2007/06/26/accounting-for-page-popularity/#comment-34285</link>
		<dc:creator><![CDATA[Jon Udell]]></dc:creator>
		<pubDate>Wed, 27 Jun 2007 13:20:13 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jonudell.net/2007/06/26/accounting-for-page-popularity/#comment-34285</guid>
		<description><![CDATA[Although I do agree with Lauren Weinstein&#039;s notion that a dispute mechanism will sometimes be necessary, it will by definition have to be used only in rare and exceptional cases.

The question I&#039;m raising is whether, in parallel, it will be generally helpful to have more transparency about what we might call the infrastructure of popularity. Banning a hate site is problematic for a bunch of reasons, one of them being that if that site is popular, its popularity is telling us something we might want to understand better -- and could with more data.]]></description>
		<content:encoded><![CDATA[<p>Although I do agree with Lauren Weinstein&#8217;s notion that a dispute mechanism will sometimes be necessary, it will by definition have to be used only in rare and exceptional cases.</p>
<p>The question I&#8217;m raising is whether, in parallel, it will be generally helpful to have more transparency about what we might call the infrastructure of popularity. Banning a hate site is problematic for a bunch of reasons, one of them being that if that site is popular, its popularity is telling us something we might want to understand better &#8212; and could with more data.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rick Moynihan</title>
		<link>http://blog.jonudell.net/2007/06/26/accounting-for-page-popularity/#comment-34035</link>
		<dc:creator><![CDATA[Rick Moynihan]]></dc:creator>
		<pubDate>Tue, 26 Jun 2007 23:10:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jonudell.net/2007/06/26/accounting-for-page-popularity/#comment-34035</guid>
		<description><![CDATA[After reading your post I found myself browsing to the Google owned photo sharing system Picasa.  What is curious and prompted me to write this comment is that at the bottom of the album pages they have a link
to &quot;Report inappropriate content&quot;.  Why treat Picasa photo albums differently from Google Search results?  From the outside it might appear like Google is suffering from corporate schizophrenia; on the
one hand not willing to censor search results, yet on the other hand willing to play the role of censor.  Yet I suspect the distinction arises for a complex mix of reasons:



        Because Picasa (Google) are hosting the photographs themselves they feel/(are) more responsible for the content.  Though I&#039;ve not checked, I&#039;m guessing they explicitly specify in the terms of service what content they feel is appropriate for Picasa users to publish.
        

        Google search and Picasa are clearly different products with different purposes and uses.  Users may be more likely to browse Picasa for content, rather than search explicitly.  A search request heuristically tends to mirror intention, where as browsing behaviour tends be more ephemeral.  If a user        searches explicitly for something, they usually want what they&#039;re looking for (unless of course, you want to stay in a Hilton hotel in Paris).  Consequently they are less likely to be surprised by what they find.
        

        There are no universally recognised &quot;terms of service&quot; for the Internet.  Filtering search results effectively puts them in a position of being an arbiter for what&#039;s allowed on the web.  This is obviously a position they need to be very careful about adopting. 
        

         Having a &quot;inappropriate content&quot; button on search pages would doubtless expose their ranking algorithms to easier gaming.
        

         Many Google properties such as Blogger, Picassa and youtube were acquisitions, so in many ways it is not surprising that there are differences. 



Does the distinction here arise solely through the terms of service?

Whilst these and many more reasons might be used to justify the different approaches between their products, it is interesting to note that there is a different attitude.  Will this prevail; or will we see
a unified approach to the problem across the board? 

I&#039;d argue that a slight modification of the &#039;disputed page&#039; idea could work for Picasa, providing of course that the content is legal and there are no awkward copyright issues (nasty-grams).  Indeed this
approach is used by the other Google owned site, youtube.  The youtube community flag potentially offensive videos as such.  Users stumbling across such content are warned and are then required to login and
verify their age.  It seems that the suggested strategy could form the basis of Googles censorship stance across the board, though questions of abuse and fairness will always arise.]]></description>
		<content:encoded><![CDATA[<p>After reading your post I found myself browsing to the Google owned photo sharing system Picasa.  What is curious and prompted me to write this comment is that at the bottom of the album pages they have a link<br />
to &#8220;Report inappropriate content&#8221;.  Why treat Picasa photo albums differently from Google Search results?  From the outside it might appear like Google is suffering from corporate schizophrenia; on the<br />
one hand not willing to censor search results, yet on the other hand willing to play the role of censor.  Yet I suspect the distinction arises for a complex mix of reasons:</p>
<p>        Because Picasa (Google) are hosting the photographs themselves they feel/(are) more responsible for the content.  Though I&#8217;ve not checked, I&#8217;m guessing they explicitly specify in the terms of service what content they feel is appropriate for Picasa users to publish.</p>
<p>        Google search and Picasa are clearly different products with different purposes and uses.  Users may be more likely to browse Picasa for content, rather than search explicitly.  A search request heuristically tends to mirror intention, where as browsing behaviour tends be more ephemeral.  If a user        searches explicitly for something, they usually want what they&#8217;re looking for (unless of course, you want to stay in a Hilton hotel in Paris).  Consequently they are less likely to be surprised by what they find.</p>
<p>        There are no universally recognised &#8220;terms of service&#8221; for the Internet.  Filtering search results effectively puts them in a position of being an arbiter for what&#8217;s allowed on the web.  This is obviously a position they need to be very careful about adopting. </p>
<p>         Having a &#8220;inappropriate content&#8221; button on search pages would doubtless expose their ranking algorithms to easier gaming.</p>
<p>         Many Google properties such as Blogger, Picassa and youtube were acquisitions, so in many ways it is not surprising that there are differences. </p>
<p>Does the distinction here arise solely through the terms of service?</p>
<p>Whilst these and many more reasons might be used to justify the different approaches between their products, it is interesting to note that there is a different attitude.  Will this prevail; or will we see<br />
a unified approach to the problem across the board? </p>
<p>I&#8217;d argue that a slight modification of the &#8216;disputed page&#8217; idea could work for Picasa, providing of course that the content is legal and there are no awkward copyright issues (nasty-grams).  Indeed this<br />
approach is used by the other Google owned site, youtube.  The youtube community flag potentially offensive videos as such.  Users stumbling across such content are warned and are then required to login and<br />
verify their age.  It seems that the suggested strategy could form the basis of Googles censorship stance across the board, though questions of abuse and fairness will always arise.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

