<?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:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: Can Affiliate Link Disclosure Go Too Far?</title>
	<atom:link href="http://www.whoisandrewwee.com/affiliate-marketing/affiliate-link-disclosure/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.whoisandrewwee.com/affiliate-marketing/affiliate-link-disclosure/</link>
	<description>BizExcellerated Internet Marketing: Achieve mastery in blogging, affiliate marketing, social traffic generation at Andrew Wee</description>
	<lastBuildDate>Wed, 08 Feb 2012 05:18:24 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Phillip Barnhart</title>
		<link>http://www.whoisandrewwee.com/affiliate-marketing/affiliate-link-disclosure/comment-page-1/#comment-505534</link>
		<dc:creator>Phillip Barnhart</dc:creator>
		<pubDate>Sat, 06 Jun 2009 03:54:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.whoisandrewwee.com/?p=786#comment-505534</guid>
		<description>Excluding twitter for the moment, why not use an existing paradigm to deal with affiliate links - semantically as &lt;a href=&quot;http://microformats.org/about/&quot; rel=&quot;nofollow&quot;&gt;microformats?&lt;/a&gt;. 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&quot;).

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&#039;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 <a href="http://microformats.org/about/" rel="nofollow">microformats?</a>. 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&#8221;).</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&#8217;s permission to start!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shawn Collins</title>
		<link>http://www.whoisandrewwee.com/affiliate-marketing/affiliate-link-disclosure/comment-page-1/#comment-505516</link>
		<dc:creator>Shawn Collins</dc:creator>
		<pubDate>Thu, 04 Jun 2009 14:43:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.whoisandrewwee.com/?p=786#comment-505516</guid>
		<description>There have been a handful of vocal folks that insist on the need for disclosure, but I haven&#039;t yet seen a single solution.

I think jamming a hashtag or (aff) is intrusive and creates a bad experience for the end user.

Not to mention the fact that these gestures would just confuse readers.

I am very confident that none of my friends and family would know what that stuff meant, and they&#039;ve been hearing me ramble on about this stuff for 15 years.</description>
		<content:encoded><![CDATA[<p>There have been a handful of vocal folks that insist on the need for disclosure, but I haven&#8217;t yet seen a single solution.</p>
<p>I think jamming a hashtag or (aff) is intrusive and creates a bad experience for the end user.</p>
<p>Not to mention the fact that these gestures would just confuse readers.</p>
<p>I am very confident that none of my friends and family would know what that stuff meant, and they&#8217;ve been hearing me ramble on about this stuff for 15 years.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

