<?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:series="http://unfoldingneurons.com/"
		>
<channel>
	<title>Comments on: Splogs Solution: Class Action Lawsuit Against Google?</title>
	<atom:link href="http://www.ensight.org/2005/10/25/splogs-solution-class-action-lawsuit-against-google/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ensight.org/2005/10/25/splogs-solution-class-action-lawsuit-against-google/</link>
	<description>I&#039;m The Boss @ netmobs, past CEO of b5media, author of Blog Marketing and a hardcore Canadian</description>
	<lastBuildDate>Fri, 05 Mar 2010 15:46:26 -0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Mr. Real Estate</title>
		<link>http://www.ensight.org/2005/10/25/splogs-solution-class-action-lawsuit-against-google/comment-page-1/#comment-48179</link>
		<dc:creator>Mr. Real Estate</dc:creator>
		<pubDate>Tue, 01 Nov 2005 02:56:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.ensight.org/archives/2005/10/25/splogs-solution-class-action-lawsuit-against-google/#comment-48179</guid>
		<description>Oh, and by the way, Jeremy, I&#039;m reviewing your book. Looking forward to the read. =)</description>
		<content:encoded><![CDATA[<p>Oh, and by the way, Jeremy, I&#8217;m reviewing your book. Looking forward to the read. =)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mr. Real Estate</title>
		<link>http://www.ensight.org/2005/10/25/splogs-solution-class-action-lawsuit-against-google/comment-page-1/#comment-48178</link>
		<dc:creator>Mr. Real Estate</dc:creator>
		<pubDate>Tue, 01 Nov 2005 02:55:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.ensight.org/archives/2005/10/25/splogs-solution-class-action-lawsuit-against-google/#comment-48178</guid>
		<description>If you&#039;re a business blog it may not be a bad thing that another blog is stealing your content via RSS syndication. Even if they&#039;re putting their website link below my article, my link&#039;s still there first, and my PageRank still is higher than the content-thief because they stole my content. People can complain about it, or they can use Feedburner to make it so not all of their content can be stolen, or they can allow it to be stolen and reap the benefits from it.

If Google gets involved with the legal aspects, all they would be doing is claiming liability for a problem they didn&#039;t create (but they bought Blogger to SPAM text ads, hellooooo). You can shut down syndication, you can create permission-based syndication, or limit what content is syndicated. The thief is liable, not Google/Blogger. There are ways to stop content thiefs.

I have had one &quot;cease and desist&quot; letter issued to one content thief, previously. I have also previously asked another Realtor to remove a post from her blog for reprinting one of my posts without permission (she was rude about it, but she removed it).

This is the blogosphere and it&#039;s very open-source. If you don&#039;t like dealing with the pitfalls of an open-source environment, maybe you should stick to ads and postcards, or print publications. If you want content removed go to the source. I do. And when I do I pull out my lawyers if I need to.

If you sign your posts and link back to your blog via your name, it really benefits you more than the spammer if they steal your content, anyway. My leads and PR were hgher when I allowed spammers to steal my blog posts with my full name linked back to my site. I kind of regret limiting what they can steal now, as most of them no longer steal my content because they can&#039;t take the full post. Limit what they can take via Feedster and they won&#039;t take it. However, if you can, use spammers to your benefit. They&#039;re going to be here, so we may as well use them for something.

Cheers.</description>
		<content:encoded><![CDATA[<p>If you&#8217;re a business blog it may not be a bad thing that another blog is stealing your content via RSS syndication. Even if they&#8217;re putting their website link below my article, my link&#8217;s still there first, and my PageRank still is higher than the content-thief because they stole my content. People can complain about it, or they can use Feedburner to make it so not all of their content can be stolen, or they can allow it to be stolen and reap the benefits from it.</p>
<p>If Google gets involved with the legal aspects, all they would be doing is claiming liability for a problem they didn&#8217;t create (but they bought Blogger to SPAM text ads, hellooooo). You can shut down syndication, you can create permission-based syndication, or limit what content is syndicated. The thief is liable, not Google/Blogger. There are ways to stop content thiefs.</p>
<p>I have had one &#8220;cease and desist&#8221; letter issued to one content thief, previously. I have also previously asked another Realtor to remove a post from her blog for reprinting one of my posts without permission (she was rude about it, but she removed it).</p>
<p>This is the blogosphere and it&#8217;s very open-source. If you don&#8217;t like dealing with the pitfalls of an open-source environment, maybe you should stick to ads and postcards, or print publications. If you want content removed go to the source. I do. And when I do I pull out my lawyers if I need to.</p>
<p>If you sign your posts and link back to your blog via your name, it really benefits you more than the spammer if they steal your content, anyway. My leads and PR were hgher when I allowed spammers to steal my blog posts with my full name linked back to my site. I kind of regret limiting what they can steal now, as most of them no longer steal my content because they can&#8217;t take the full post. Limit what they can take via Feedster and they won&#8217;t take it. However, if you can, use spammers to your benefit. They&#8217;re going to be here, so we may as well use them for something.</p>
<p>Cheers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Uli Iserloh</title>
		<link>http://www.ensight.org/2005/10/25/splogs-solution-class-action-lawsuit-against-google/comment-page-1/#comment-48169</link>
		<dc:creator>Uli Iserloh</dc:creator>
		<pubDate>Thu, 27 Oct 2005 12:39:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.ensight.org/archives/2005/10/25/splogs-solution-class-action-lawsuit-against-google/#comment-48169</guid>
		<description>Related to this discussion is &lt;strong&gt;trademark infringement&lt;/strong&gt; through splogs. Rather than stealing your content, spammers register splogs that ride on your popular trademark. However, as with splogs in general, Blogger/Google refuses to get involved and take down such splogs - despite trademark infringement being a violation of their terms of service.

Instead, Blogger is asking you to take up the issue with the splog owner.... yeah, right, that&#039;s gonna work...</description>
		<content:encoded><![CDATA[<p>Related to this discussion is <strong>trademark infringement</strong> through splogs. Rather than stealing your content, spammers register splogs that ride on your popular trademark. However, as with splogs in general, Blogger/Google refuses to get involved and take down such splogs &#8211; despite trademark infringement being a violation of their terms of service.</p>
<p>Instead, Blogger is asking you to take up the issue with the splog owner&#8230;. yeah, right, that&#8217;s gonna work&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon</title>
		<link>http://www.ensight.org/2005/10/25/splogs-solution-class-action-lawsuit-against-google/comment-page-1/#comment-48159</link>
		<dc:creator>Jon</dc:creator>
		<pubDate>Wed, 26 Oct 2005 18:50:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.ensight.org/archives/2005/10/25/splogs-solution-class-action-lawsuit-against-google/#comment-48159</guid>
		<description>This comment isn&#039;t really on topic, but slightly related.

The splog problem on Blogspot is one of the things that makes me shake my head. For all their technological savvy, Google seems to fumble a lot when it comes to Blogger.

Another case in point is the recent addition of the captcha functionality on Blogger to reduce comment spam. Since day one I&#039;ve been curious (and dismayed) to see that even logged in Blogspot users must fill out the captcha in order to post a comment (assuming the blog owner has the captcha turned on).

IMHO,  the fact that a user is logged into the system with a legitimate account should short-circuit all other spam tests. 

The current situation shows that Google can&#039;t even trust legititmate accounts to be human and not spambots, which is indicative of the &lt;em&gt;real &lt;/em&gt;rot underneath Blogspot.

Thinking out loud...</description>
		<content:encoded><![CDATA[<p>This comment isn&#8217;t really on topic, but slightly related.</p>
<p>The splog problem on Blogspot is one of the things that makes me shake my head. For all their technological savvy, Google seems to fumble a lot when it comes to Blogger.</p>
<p>Another case in point is the recent addition of the captcha functionality on Blogger to reduce comment spam. Since day one I&#8217;ve been curious (and dismayed) to see that even logged in Blogspot users must fill out the captcha in order to post a comment (assuming the blog owner has the captcha turned on).</p>
<p>IMHO,  the fact that a user is logged into the system with a legitimate account should short-circuit all other spam tests. </p>
<p>The current situation shows that Google can&#8217;t even trust legititmate accounts to be human and not spambots, which is indicative of the <em>real </em>rot underneath Blogspot.</p>
<p>Thinking out loud&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg Hughes</title>
		<link>http://www.ensight.org/2005/10/25/splogs-solution-class-action-lawsuit-against-google/comment-page-1/#comment-48155</link>
		<dc:creator>Greg Hughes</dc:creator>
		<pubDate>Wed, 26 Oct 2005 03:46:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.ensight.org/archives/2005/10/25/splogs-solution-class-action-lawsuit-against-google/#comment-48155</guid>
		<description>&lt;em&gt;&quot;Maybe, if nothing else, someone should setup a page whereby we can point out content that’s been stolen and automatically email Google about it?&quot;&lt;/em&gt;

Yeah, good idea - a blog that consists of making comments as posts, and auto-email each one to google&#039;s abuse email address maybe? That would take like 5 minutes to set up.</description>
		<content:encoded><![CDATA[<p><em>&#8220;Maybe, if nothing else, someone should setup a page whereby we can point out content that’s been stolen and automatically email Google about it?&#8221;</em></p>
<p>Yeah, good idea &#8211; a blog that consists of making comments as posts, and auto-email each one to google&#8217;s abuse email address maybe? That would take like 5 minutes to set up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeremy Wright</title>
		<link>http://www.ensight.org/2005/10/25/splogs-solution-class-action-lawsuit-against-google/comment-page-1/#comment-48152</link>
		<dc:creator>Jeremy Wright</dc:creator>
		<pubDate>Tue, 25 Oct 2005 18:44:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.ensight.org/archives/2005/10/25/splogs-solution-class-action-lawsuit-against-google/#comment-48152</guid>
		<description>Elliott / Jon: Yeah, this is sort of what I was wondering. I&#039;ve NEVER heard of Google removing content, in spite of numerous requests. Obviously it&#039;s not like they&#039;re empowering users to create splogs (though one could create the argument that they are, I don&#039;t intend to).

So if they aren&#039;t removing content, and have been asked to remove it because of a copyright issue, isnt&#039; there grounds for legal action?

Maybe, if nothing else, someone should setup a page whereby we can point out content that&#039;s been stolen and automatically email Google about it?</description>
		<content:encoded><![CDATA[<p>Elliott / Jon: Yeah, this is sort of what I was wondering. I&#8217;ve NEVER heard of Google removing content, in spite of numerous requests. Obviously it&#8217;s not like they&#8217;re empowering users to create splogs (though one could create the argument that they are, I don&#8217;t intend to).</p>
<p>So if they aren&#8217;t removing content, and have been asked to remove it because of a copyright issue, isnt&#8217; there grounds for legal action?</p>
<p>Maybe, if nothing else, someone should setup a page whereby we can point out content that&#8217;s been stolen and automatically email Google about it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Gales</title>
		<link>http://www.ensight.org/2005/10/25/splogs-solution-class-action-lawsuit-against-google/comment-page-1/#comment-48151</link>
		<dc:creator>Jon Gales</dc:creator>
		<pubDate>Tue, 25 Oct 2005 18:19:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.ensight.org/archives/2005/10/25/splogs-solution-class-action-lawsuit-against-google/#comment-48151</guid>
		<description>I talked to Blogger about a takedown request and they told me to make a DMCA request (with directions for the format). I did so and faxed it to Google HQ and nothing was ever done about it.  According to a WSJ reporter who followed up on it for a story, Google responded. But the site was never deleted and I never heard from them. In fact, the site was mentioned in the WSJ  story and it STILL remains with my story as the latest post.</description>
		<content:encoded><![CDATA[<p>I talked to Blogger about a takedown request and they told me to make a DMCA request (with directions for the format). I did so and faxed it to Google HQ and nothing was ever done about it.  According to a WSJ reporter who followed up on it for a story, Google responded. But the site was never deleted and I never heard from them. In fact, the site was mentioned in the WSJ  story and it STILL remains with my story as the latest post.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Elliott Back</title>
		<link>http://www.ensight.org/2005/10/25/splogs-solution-class-action-lawsuit-against-google/comment-page-1/#comment-48150</link>
		<dc:creator>Elliott Back</dc:creator>
		<pubDate>Tue, 25 Oct 2005 17:49:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.ensight.org/archives/2005/10/25/splogs-solution-class-action-lawsuit-against-google/#comment-48150</guid>
		<description>Yes, you are.  Google or Microsoft as blog providers/hosts are afforded a measure of irresponsibility with regards to the content that their users host, just like a web server company cannot be found liable for distributing copyright content if their users abuse the service.  You can, however, go after users individually and request to the host that offending material be removed.

And as for LJ and typepad, Typepad is a pay-service.  Spammers don&#039;t want to pay to setup quick spam blogs.  And, I&#039;ve come across LJ splogs:  http://elliottback.com/wp/archives/2005/10/17/livejournal-splog/ , although there&#039;s a disincentive because they are by default non-indexable.</description>
		<content:encoded><![CDATA[<p>Yes, you are.  Google or Microsoft as blog providers/hosts are afforded a measure of irresponsibility with regards to the content that their users host, just like a web server company cannot be found liable for distributing copyright content if their users abuse the service.  You can, however, go after users individually and request to the host that offending material be removed.</p>
<p>And as for LJ and typepad, Typepad is a pay-service.  Spammers don&#8217;t want to pay to setup quick spam blogs.  And, I&#8217;ve come across LJ splogs:  <a href="http://elliottback.com/wp/archives/2005/10/17/livejournal-splog/" rel="nofollow">http://elliottback.com/wp/archives/2005/10/17/livejournal-splog/</a> , although there&#8217;s a disincentive because they are by default non-indexable.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Larry Borsato</title>
		<link>http://www.ensight.org/2005/10/25/splogs-solution-class-action-lawsuit-against-google/comment-page-1/#comment-48149</link>
		<dc:creator>Larry Borsato</dc:creator>
		<pubDate>Tue, 25 Oct 2005 16:15:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.ensight.org/archives/2005/10/25/splogs-solution-class-action-lawsuit-against-google/#comment-48149</guid>
		<description>Under the DMCA Notice-and-Takedown provisions the must remove copyrighted materials at the request of the owner. However, there is no requirement for anyone to proactively look for copyright violations. It is up to you to protect your copyright.

Also, you would be unable to launch a class action lawsuit unless there was a cause of action - i.e. Google refuses to take down your copyrighted material</description>
		<content:encoded><![CDATA[<p>Under the DMCA Notice-and-Takedown provisions the must remove copyrighted materials at the request of the owner. However, there is no requirement for anyone to proactively look for copyright violations. It is up to you to protect your copyright.</p>
<p>Also, you would be unable to launch a class action lawsuit unless there was a cause of action &#8211; i.e. Google refuses to take down your copyrighted material</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AIMForum</title>
		<link>http://www.ensight.org/2005/10/25/splogs-solution-class-action-lawsuit-against-google/comment-page-1/#comment-48147</link>
		<dc:creator>AIMForum</dc:creator>
		<pubDate>Tue, 25 Oct 2005 15:32:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.ensight.org/archives/2005/10/25/splogs-solution-class-action-lawsuit-against-google/#comment-48147</guid>
		<description>If you inform them of copyrighted content being hosted at their server, they need to remove it.</description>
		<content:encoded><![CDATA[<p>If you inform them of copyrighted content being hosted at their server, they need to remove it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
