<?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: Should Google, Yahoo, Mahalo, etc. ban affiliate links? (or &#8220;Will the FTC ban undisclosed affiliate links for us all?&#8221;)</title>
	<atom:link href="http://calacanis.com/2008/02/29/will-the-ftc-ban-undisclosed-affiliate-links/feed/" rel="self" type="application/rss+xml" />
	<link>http://calacanis.com/2008/02/29/will-the-ftc-ban-undisclosed-affiliate-links/</link>
	<description>Weblog by Jason Calacanis, formerly of Weblogs, Inc. and AOL.</description>
	<lastBuildDate>Fri, 20 Nov 2009 00:21:07 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Calacanis Wants to Ban Affiliate Links; What About Banning Employee Linking? &#124; CenterNetworks</title>
		<link>http://calacanis.com/2008/02/29/will-the-ftc-ban-undisclosed-affiliate-links/#comment-13229</link>
		<dc:creator>Calacanis Wants to Ban Affiliate Links; What About Banning Employee Linking? &#124; CenterNetworks</dc:creator>
		<pubDate>Sat, 12 Sep 2009 02:02:41 +0000</pubDate>
		<guid isPermaLink="false">http://calacanis.wordpress.com/2008/02/29/will-the-ftc-ban-undisclosed-affiliate-links/#comment-13229</guid>
		<description>[...] apparently left the world of pissing off SEO folk and is now pissing off affiliate folk. This time he wonders if the search engines (including Google, Yahoo and Mahalo) should ban affiliate links from being indexed. First, how [...]</description>
		<content:encoded><![CDATA[<p>[...] apparently left the world of pissing off SEO folk and is now pissing off affiliate folk. This time he wonders if the search engines (including Google, Yahoo and Mahalo) should ban affiliate links from being indexed. First, how [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil Barnhart - Web Developer</title>
		<link>http://calacanis.com/2008/02/29/will-the-ftc-ban-undisclosed-affiliate-links/#comment-11384</link>
		<dc:creator>Phil Barnhart - Web Developer</dc:creator>
		<pubDate>Sat, 06 Jun 2009 13:33:51 +0000</pubDate>
		<guid isPermaLink="false">http://calacanis.wordpress.com/2008/02/29/will-the-ftc-ban-undisclosed-affiliate-links/#comment-11384</guid>
		<description>Excluding twitter for the moment, why not use an existing paradigm to deal with affiliate links - semantically as microformats?. Something as simple as rel=&quot;affiliate&quot; might be sufficient. A more complex microformat might identify the advertiser or network (a la rel=&quot;license&quot; microformat”).

This way, the small percentage of people who may be concerned can download the inevitable plugin if needed, management and links to privacy and disclosure pages automated, etc. Of course, the real drivers of this may need to the actual affiliate programs - if CJ for example put this in their auto code generation tool.

As for Twitter, the major URL shorteners like BudURL could simply set up a complementary domain for affiliate/sponsored links and maintain the disclosure on their site via a link preview function. Again, it would help if Twitter then autotagged the URL.

A modest proposal, at least. And requires no one else’s permission to start!</description>
		<content:encoded><![CDATA[<p>Excluding twitter for the moment, why not use an existing paradigm to deal with affiliate links &#8211; semantically as microformats?. Something as simple as rel=&#8221;affiliate&#8221; might be sufficient. A more complex microformat might identify the advertiser or network (a la rel=&#8221;license&#8221; microformat”).</p>
<p>This way, the small percentage of people who may be concerned can download the inevitable plugin if needed, management and links to privacy and disclosure pages automated, etc. Of course, the real drivers of this may need to the actual affiliate programs &#8211; if CJ for example put this in their auto code generation tool.</p>
<p>As for Twitter, the major URL shorteners like BudURL could simply set up a complementary domain for affiliate/sponsored links and maintain the disclosure on their site via a link preview function. Again, it would help if Twitter then autotagged the URL.</p>
<p>A modest proposal, at least. And requires no one else’s permission to start!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
