<?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: Should we ban unlabled affiliate links from Mahalo?</title>
	<atom:link href="http://calacanis.com/2008/02/28/should-we-ban-unlabled-affiliate-links-from-mahalo/feed/" rel="self" type="application/rss+xml" />
	<link>http://calacanis.com/2008/02/28/should-we-ban-unlabled-affiliate-links-from-mahalo/</link>
	<description>Just another WordPress site</description>
	<lastBuildDate>Wed, 10 Nov 2010 14:11:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.3</generator>
	<item>
		<title>By: Phil Barnhart</title>
		<link>http://calacanis.com/2008/02/28/should-we-ban-unlabled-affiliate-links-from-mahalo/#comment-1159</link>
		<dc:creator>Phil Barnhart</dc:creator>
		<pubDate>Sat, 06 Jun 2009 13:35:29 +0000</pubDate>
		<guid isPermaLink="false">http://calacanis.wordpress.com/2008/02/28/should-we-ban-unlabled-affiliate-links-from-mahalo/#comment-1159</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>

