<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.2" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Google AdSense doesn&#8217;t honor their policy on inappropriate content</title>
	<link>http://www.dankohn.com/archives/344</link>
	<description>Freedom of the press belongs to those who own one. - A.J. Liebling</description>
	<pubDate>Fri, 09 May 2008 14:42:52 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.2</generator>
		<item>
		<title>By: Dee Wilson</title>
		<link>http://www.dankohn.com/archives/344#comment-56</link>
		<dc:creator>Dee Wilson</dc:creator>
		<pubDate>Wed, 17 Oct 2007 15:37:46 +0000</pubDate>
		<guid>http://www.dankohn.com/archives/344#comment-56</guid>
		<description>Couldn't agree more. I had to recently remove a 3rd party guestbook from a primary school website as the ads were totally inappropriate for small children to see.</description>
		<content:encoded><![CDATA[<p>Couldn&#8217;t agree more. I had to recently remove a 3rd party guestbook from a primary school website as the ads were totally inappropriate for small children to see.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gearspring</title>
		<link>http://www.dankohn.com/archives/344#comment-51</link>
		<dc:creator>Gearspring</dc:creator>
		<pubDate>Sun, 28 Aug 2005 18:47:20 +0000</pubDate>
		<guid>http://www.dankohn.com/archives/344#comment-51</guid>
		<description>Maybe there is a loophole.  Obfuscated email addresses don't violate AdSense rules, so maybe we need a wikimedia markup that obfuscates generaly. &#60;obfuscate&#62;HGH&#60;/obfuscate&#62; which can be rendered in multiple ways that are hard to scrape. Possibilities are a picture, letters mixed with invisible html markup, look-a-like fonts, and more.
</description>
		<content:encoded><![CDATA[<p>Maybe there is a loophole.  Obfuscated email addresses don&#8217;t violate AdSense rules, so maybe we need a wikimedia markup that obfuscates generaly. &lt;obfuscate&gt;HGH&lt;/obfuscate&gt; which can be rendered in multiple ways that are hard to scrape. Possibilities are a picture, letters mixed with invisible html markup, look-a-like fonts, and more.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Klaws</title>
		<link>http://www.dankohn.com/archives/344#comment-50</link>
		<dc:creator>Klaws</dc:creator>
		<pubDate>Thu, 04 Aug 2005 11:42:48 +0000</pubDate>
		<guid>http://www.dankohn.com/archives/344#comment-50</guid>
		<description>Yup. Right. And the Google AdSense rules leave no loopholes at all. In other word, one may not use any software to process or filter AdSense ads (and the required AdSense code snippet, as provided by Google, may not be modifiend or altered anyway).

Of course you might choose to try things out, like having the web server request the AdSense ad, filter it, and then forward it to the browser. Of course, Google will see that all views come from the same IP address, so I guess that you might lose a substantial part of the pay-per-view compensation (pay-per-click would still work). Google's threat is that they might kick you out of AdSense, if they find out.</description>
		<content:encoded><![CDATA[<p>Yup. Right. And the Google AdSense rules leave no loopholes at all. In other word, one may not use any software to process or filter AdSense ads (and the required AdSense code snippet, as provided by Google, may not be modifiend or altered anyway).</p>
<p>Of course you might choose to try things out, like having the web server request the AdSense ad, filter it, and then forward it to the browser. Of course, Google will see that all views come from the same IP address, so I guess that you might lose a substantial part of the pay-per-view compensation (pay-per-click would still work). Google&#8217;s threat is that they might kick you out of AdSense, if they find out.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.714 seconds -->
