<?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/"
		>
<channel>
	<title>Comments on: Death to Human Content Aggregators</title>
	<atom:link href="http://www.jackofallblogs.com/2008/03/29/death-to-human-content-aggregators/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jackofallblogs.com/2008/03/29/death-to-human-content-aggregators/</link>
	<description>Snarking the Web since 2004.</description>
	<lastBuildDate>Thu, 25 Feb 2010 15:30:41 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Michael</title>
		<link>http://www.jackofallblogs.com/2008/03/29/death-to-human-content-aggregators/comment-page-1/#comment-71699</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Sun, 30 Mar 2008 23:32:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.jackofallblogs.com/2008/03/29/death-to-human-content-aggregators/#comment-71699</guid>
		<description>I read your rants here and on the Blog Herald. At first, I wanted to chide you. Are you living in the past? Gripe all you want about casual scraping. People will do it, even if confronted publicly about their thievery. Many sued by RIAA probably found untraceable ways to steal music afterwards.

Then I may have grasped a solution. Google, Yahoo, MSN, and other major players can agree on a standard whereby authors submit content to search engines before making it public online. Submitted content is tagged for time and author, but not made listed in SERPs until made public on site and crawlable to search engine spiders. The author is notified immediately that content has been tagged. Then the author can display content publicly with greater assurance that scrapers will not be indexed favorably by search engines.

Time and author tags provide search engines in-house tracking that could be used to determine authenticity after content is indexed. Obviously, if you submit your content before making it public for indexing, then you probably are the author. Page rank and relevancy could be pegged to authenticity. Duplicate (scraped) content could be spotted immediately and ignored or penalized without jeopardizing the original&#039;s SERPs.

Those who submit content must have Google, Yahoo, MSN accounts, etc. (This would make it an easier sell to search engines.) All older content is grandfathered. In other words, content already indexed cannot be resubmitted for authentic tags. So I cannot submit my site&#039;s present poems for tags, only new poems. Someone could steal another&#039;s content, such as one of my handwritten poems, before the author submits it to search engines for tagging. In that case, the author could file a DMCA takedown notice and go to court if necessary, just like we have to do now.

How do author and search engine reconcile authentic tag to content location (URL) before content is made public? The author must tell the search engine at what URL the content will appear, although the content will not appear at that URL until a future date.

What if author wants to move content from one URL to another? The author could log into his or her account and change the authentic tag&#039;s URL information. This probably would be the most difficult problem this idea faces. Web sites go dark, and the author uploads old content elsewhere at a later date, etc.

What if author loses and cannot obtain again his or her login information? In the short term, I am not sure. In the long term, defunct accounts could have submitted content untagged after, say, a year has passed with no account activity. This would not negate copyright protection, but search engines need to clean house from time to time.

I think authentic tagging would work much better than the ragtag system we have now. Will bloggers still copy and paste? Will scrapers still scrape? Yes, but your original content would be ranked more favorably than theirs if tagged. Their &quot;content&quot; might be ignored altogether. What do you think?</description>
		<content:encoded><![CDATA[<p>I read your rants here and on the Blog Herald. At first, I wanted to chide you. Are you living in the past? Gripe all you want about casual scraping. People will do it, even if confronted publicly about their thievery. Many sued by <span class="caps">RIAA</span> probably found untraceable ways to steal music afterwards.</p>
<p>Then I may have grasped a solution. Google, Yahoo, <span class="caps">MSN</span>, and other major players can agree on a standard whereby authors submit content to search engines before making it public online. Submitted content is tagged for time and author, but not made listed in <span class="caps">SER</span>Ps until made public on site and crawlable to search engine spiders. The author is notified immediately that content has been tagged. Then the author can display content publicly with greater assurance that scrapers will not be indexed favorably by search engines.</p>
<p>Time and author tags provide search engines in-house tracking that could be used to determine authenticity after content is indexed. Obviously, if you submit your content before making it public for indexing, then you probably are the author. Page rank and relevancy could be pegged to authenticity. Duplicate (scraped) content could be spotted immediately and ignored or penalized without jeopardizing the original&#8217;s <span class="caps">SER</span>Ps.</p>
<p>Those who submit content must have Google, Yahoo, <span class="caps">MSN</span> accounts, etc. (This would make it an easier sell to search engines.) All older content is grandfathered. In other words, content already indexed cannot be resubmitted for authentic tags. So I cannot submit my site&#8217;s present poems for tags, only new poems. Someone could steal another&#8217;s content, such as one of my handwritten poems, before the author submits it to search engines for tagging. In that case, the author could file a <span class="caps">DMCA</span> takedown notice and go to court if necessary, just like we have to do now.</p>
<p>How do author and search engine reconcile authentic tag to content location (URL) before content is made public? The author must tell the search engine at what <span class="caps">URL</span> the content will appear, although the content will not appear at that <span class="caps">URL</span> until a future date.</p>
<p>What if author wants to move content from one <span class="caps">URL</span> to another? The author could log into his or her account and change the authentic tag&#8217;s <span class="caps">URL</span> information. This probably would be the most difficult problem this idea faces. Web sites go dark, and the author uploads old content elsewhere at a later date, etc.</p>
<p>What if author loses and cannot obtain again his or her login information? In the short term, I am not sure. In the long term, defunct accounts could have submitted content untagged after, say, a year has passed with no account activity. This would not negate copyright protection, but search engines need to clean house from time to time.</p>
<p>I think authentic tagging would work much better than the ragtag system we have now. Will bloggers still copy and paste? Will scrapers still scrape? Yes, but your original content would be ranked more favorably than theirs if tagged. Their &#8220;content&#8221; might be ignored altogether. What do you think?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Blogging vs. Human Content Aggregators : The Blog Herald</title>
		<link>http://www.jackofallblogs.com/2008/03/29/death-to-human-content-aggregators/comment-page-1/#comment-71669</link>
		<dc:creator>Blogging vs. Human Content Aggregators : The Blog Herald</dc:creator>
		<pubDate>Sun, 30 Mar 2008 12:57:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.jackofallblogs.com/2008/03/29/death-to-human-content-aggregators/#comment-71669</guid>
		<description>[...] recently blogged about my disdain for so-called &#8216;bloggers&#8217; who rip and run with your content. You know the drill. You stay up late researching and writing a post, only to [...]</description>
		<content:encoded><![CDATA[<p>[...] recently blogged about my disdain for so-called &#8216;bloggers&#8217; who rip and run with your content. You know the drill. You stay up late researching and writing a post, only to [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
