<?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: A Compromise for Disclosing Paid Links?; Netvibes Goes Public; and Zillow Banned!</title>
	<atom:link href="http://www.marketingpilgrim.com/2007/04/a-compromise-for-disclosing-paid-links-netvibes-goes-public-and-zillow-banned.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.marketingpilgrim.com/2007/04/a-compromise-for-disclosing-paid-links-netvibes-goes-public-and-zillow-banned.html</link>
	<description>Internet Marketing News</description>
	<lastBuildDate>Fri, 10 Feb 2012 17:00:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Andy Beard</title>
		<link>http://www.marketingpilgrim.com/2007/04/a-compromise-for-disclosing-paid-links-netvibes-goes-public-and-zillow-banned.html/comment-page-1#comment-24719</link>
		<dc:creator>Andy Beard</dc:creator>
		<pubDate>Tue, 17 Apr 2007 11:04:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.marketingpilgrim.com/2007/04/a-compromise-for-disclosing-paid-links-netvibes-goes-public-and-zillow-banned.html#comment-24719</guid>
		<description>Michael&#039;s solution isn&#039;t as ideal as his post makes out. It won&#039;t show up in feeds, and even if he uses inline CSS some feed readers strip that out.

A better alternative (for the legal side) is just to use a disclosure policy, and specific per post disclosure in text, either manually or with my plugin.
A few people have also found my Feedburner Feedflare useful</description>
		<content:encoded><![CDATA[<p>Michael&#8217;s solution isn&#8217;t as ideal as his post makes out. It won&#8217;t show up in feeds, and even if he uses inline CSS some feed readers strip that out.</p>
<p>A better alternative (for the legal side) is just to use a disclosure policy, and specific per post disclosure in text, either manually or with my plugin.<br />
A few people have also found my Feedburner Feedflare useful</p>
]]></content:encoded>
	</item>
</channel>
</rss>

