<?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: Universal Disclosure</title>
	<atom:link href="http://izea.com/universal-disclosure/feed/" rel="self" type="application/rss+xml" />
	<link>http://izea.com/universal-disclosure/</link>
	<description>Social Media Marketing</description>
	<lastBuildDate>Wed, 08 Feb 2012 00:28:54 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Theresia Sperdute</title>
		<link>http://izea.com/universal-disclosure/comment-page-1/#comment-26211</link>
		<dc:creator>Theresia Sperdute</dc:creator>
		<pubDate>Wed, 29 Dec 2010 12:42:16 +0000</pubDate>
		<guid isPermaLink="false">http://izea.com/?p=4368#comment-26211</guid>
		<description>Many thanks for the awsome article. I am going to keep an observation about your own website, i allready saved it to personal list :)</description>
		<content:encoded><![CDATA[<p>Many thanks for the awsome article. I am going to keep an observation about your own website, i allready saved it to personal list <img src='http://izea.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kiran</title>
		<link>http://izea.com/universal-disclosure/comment-page-1/#comment-7815</link>
		<dc:creator>Kiran</dc:creator>
		<pubDate>Tue, 25 Aug 2009 17:00:44 +0000</pubDate>
		<guid isPermaLink="false">http://izea.com/?p=4368#comment-7815</guid>
		<description>where to get this disclosure badge

plz tell me</description>
		<content:encoded><![CDATA[<p>where to get this disclosure badge</p>
<p>plz tell me</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Narrow vs broad: blogging and the FTC &#171; VIVIAN J. PAIGE &#124; All Politics is Local</title>
		<link>http://izea.com/universal-disclosure/comment-page-1/#comment-7814</link>
		<dc:creator>Narrow vs broad: blogging and the FTC &#171; VIVIAN J. PAIGE &#124; All Politics is Local</dc:creator>
		<pubDate>Sun, 28 Jun 2009 16:27:31 +0000</pubDate>
		<guid isPermaLink="false">http://izea.com/?p=4368#comment-7814</guid>
		<description>[...] without disclosure is naive at best. Even IZEA, who matches bloggers with advertisers, requires disclosure of the arrangements by its [...]</description>
		<content:encoded><![CDATA[<p>[...] without disclosure is naive at best. Even IZEA, who matches bloggers with advertisers, requires disclosure of the arrangements by its [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rackspace Cloud (Mosso) Link To Us Payola &#124; rapid-DEV.net</title>
		<link>http://izea.com/universal-disclosure/comment-page-1/#comment-7813</link>
		<dc:creator>Rackspace Cloud (Mosso) Link To Us Payola &#124; rapid-DEV.net</dc:creator>
		<pubDate>Mon, 15 Jun 2009 06:08:06 +0000</pubDate>
		<guid isPermaLink="false">http://izea.com/?p=4368#comment-7813</guid>
		<description>[...] This Rackspace marketing campaign seems totally unworkable, especially the direction disclosure is taking. [...]</description>
		<content:encoded><![CDATA[<p>[...] This Rackspace marketing campaign seems totally unworkable, especially the direction disclosure is taking. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: What Disclosure Issues Mean for PR &#124; Solo PR Pro &#124; Resources for Independent PR &#38; MarCom Consultants</title>
		<link>http://izea.com/universal-disclosure/comment-page-1/#comment-7812</link>
		<dc:creator>What Disclosure Issues Mean for PR &#124; Solo PR Pro &#124; Resources for Independent PR &#38; MarCom Consultants</dc:creator>
		<pubDate>Thu, 11 Jun 2009 16:10:34 +0000</pubDate>
		<guid isPermaLink="false">http://izea.com/?p=4368#comment-7812</guid>
		<description>[...] just another new frontier, and this is an area destined to be gray for some time. What constitutes disclosure?  What about social media mentions outside of [...]</description>
		<content:encoded><![CDATA[<p>[...] just another new frontier, and this is an area destined to be gray for some time. What constitutes disclosure?  What about social media mentions outside of [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Emily Leahy-Thieler</title>
		<link>http://izea.com/universal-disclosure/comment-page-1/#comment-7811</link>
		<dc:creator>Emily Leahy-Thieler</dc:creator>
		<pubDate>Thu, 11 Jun 2009 01:37:49 +0000</pubDate>
		<guid isPermaLink="false">http://izea.com/?p=4368#comment-7811</guid>
		<description>I think a Universal Disclosure Registry would legitimize marketing tactics that are widely-used, but, as you say, not all playing by the same rules. As a blogger or tweeter (twitterer), I wouldn&#039;t have to feel so &quot;icky&quot; about taking payments for participating in campaigns. As a marketer, I&#039;d feel more secure that there wouldn&#039;t be a huge customer backlash against my campaign. And as a reader, I filter the information I get based on whether it&#039;s a paid endorsement or not. I think it&#039;s a win all the way around. I think some shady marketers and bloggers might not willingly comply, but the vast majority want to use social media responsibly. Great work!

I blogged about the idea of sponsored tweets a while back and wanted to mention again that I think it&#039;s a great idea especially at a very local level. A UDR would go even further in providing value to everyone involved.</description>
		<content:encoded><![CDATA[<p>I think a Universal Disclosure Registry would legitimize marketing tactics that are widely-used, but, as you say, not all playing by the same rules. As a blogger or tweeter (twitterer), I wouldn&#8217;t have to feel so &#8220;icky&#8221; about taking payments for participating in campaigns. As a marketer, I&#8217;d feel more secure that there wouldn&#8217;t be a huge customer backlash against my campaign. And as a reader, I filter the information I get based on whether it&#8217;s a paid endorsement or not. I think it&#8217;s a win all the way around. I think some shady marketers and bloggers might not willingly comply, but the vast majority want to use social media responsibly. Great work!</p>
<p>I blogged about the idea of sponsored tweets a while back and wanted to mention again that I think it&#8217;s a great idea especially at a very local level. A UDR would go even further in providing value to everyone involved.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Beard</title>
		<link>http://izea.com/universal-disclosure/comment-page-1/#comment-7810</link>
		<dc:creator>Andy Beard</dc:creator>
		<pubDate>Wed, 10 Jun 2009 15:33:53 +0000</pubDate>
		<guid isPermaLink="false">http://izea.com/?p=4368#comment-7810</guid>
		<description>It won&#039;t work with the CMS providers, because other than complaining about disclosure as a form of linkbait, most top bloggers don&#039;t practice totally transparent blogging.

I paid for the development of a disclosure policy plugin which was in many ways even simpler.
You just create a set of things you need to disclose based upon keywords like company names, and the plugin would add footer notes, and it would apply them retroactively.
You could for instance disclose &quot;I am a Google employee, though the thoughts on this blog are my own&quot;

If you left Google, you could change the disclosure to &quot;I was a Google employee up until MM/DD/YY&quot;

Ultimately hardly anyone used it, and those that did used it as a way of advertising - I heard reports of revenue increases of 30%+

I haven&#039;t updated it as there wasn&#039;t enough interest.

I now have better solutions planned, but not specifically for disclosure.

Any central registry has another pitfall - many would look on that as being some kind of linking or advertising scheme, and for affiliates, it is a traffic leak.</description>
		<content:encoded><![CDATA[<p>It won&#8217;t work with the CMS providers, because other than complaining about disclosure as a form of linkbait, most top bloggers don&#8217;t practice totally transparent blogging.</p>
<p>I paid for the development of a disclosure policy plugin which was in many ways even simpler.<br />
You just create a set of things you need to disclose based upon keywords like company names, and the plugin would add footer notes, and it would apply them retroactively.<br />
You could for instance disclose &#8220;I am a Google employee, though the thoughts on this blog are my own&#8221;</p>
<p>If you left Google, you could change the disclosure to &#8220;I was a Google employee up until MM/DD/YY&#8221;</p>
<p>Ultimately hardly anyone used it, and those that did used it as a way of advertising &#8211; I heard reports of revenue increases of 30%+</p>
<p>I haven&#8217;t updated it as there wasn&#8217;t enough interest.</p>
<p>I now have better solutions planned, but not specifically for disclosure.</p>
<p>Any central registry has another pitfall &#8211; many would look on that as being some kind of linking or advertising scheme, and for affiliates, it is a traffic leak.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan...</title>
		<link>http://izea.com/universal-disclosure/comment-page-1/#comment-7809</link>
		<dc:creator>Dan...</dc:creator>
		<pubDate>Wed, 10 Jun 2009 14:16:48 +0000</pubDate>
		<guid isPermaLink="false">http://izea.com/?p=4368#comment-7809</guid>
		<description>Interesting idea, but prolly only part of full solution...similar to some thoughts Steve and I hashed out years ago (remember CleanStreamMedia Steve?)

I believe the best solution would loop in the major CMS providers with a disclosure/conflict field as ubiquitous as title, body, date, author, and tags.  Such a field could do at least three things:
1) Allows for disclosing the spectrum of conflicts, getting us out of the debate about conflict as a black-and-white issue.  There are many degrees of conflict that readers could care about.  Just a few categories are: No conflict, friend/family, shareholder, cash/goods  $100, employee
2) Defaults as &quot;No conflict&quot; so authors/posts shift from staying silent on the topic to making an affirmative statement.  This is critical.  Once people are making affirmative statements about their potential conflict, they are more likely to own up to the reality of their conflict. Silence on conflict is what all the hypocrites use as default, providing conflict excuses only when called out.
3) Possibly, links to universal registry from this field so readers can see more detail on relationship and possibly find other participants in same campaign.

I mention the CMS providers because they have the ability to change the disclosure landscape by adding a single field/default.  Few single companies are in such a position to drive transparency change for all bloggers/marketers.

I think industry-wide cooperation to this degree is a longshot, but enjoy seeing IZEA continue to drive the discussion of best practices and tools to maximize transparency for years to come...</description>
		<content:encoded><![CDATA[<p>Interesting idea, but prolly only part of full solution&#8230;similar to some thoughts Steve and I hashed out years ago (remember CleanStreamMedia Steve?)</p>
<p>I believe the best solution would loop in the major CMS providers with a disclosure/conflict field as ubiquitous as title, body, date, author, and tags.  Such a field could do at least three things:<br />
1) Allows for disclosing the spectrum of conflicts, getting us out of the debate about conflict as a black-and-white issue.  There are many degrees of conflict that readers could care about.  Just a few categories are: No conflict, friend/family, shareholder, cash/goods  $100, employee<br />
2) Defaults as &#8220;No conflict&#8221; so authors/posts shift from staying silent on the topic to making an affirmative statement.  This is critical.  Once people are making affirmative statements about their potential conflict, they are more likely to own up to the reality of their conflict. Silence on conflict is what all the hypocrites use as default, providing conflict excuses only when called out.<br />
3) Possibly, links to universal registry from this field so readers can see more detail on relationship and possibly find other participants in same campaign.</p>
<p>I mention the CMS providers because they have the ability to change the disclosure landscape by adding a single field/default.  Few single companies are in such a position to drive transparency change for all bloggers/marketers.</p>
<p>I think industry-wide cooperation to this degree is a longshot, but enjoy seeing IZEA continue to drive the discussion of best practices and tools to maximize transparency for years to come&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rackspace Cloud / Mosso Payola</title>
		<link>http://izea.com/universal-disclosure/comment-page-1/#comment-7808</link>
		<dc:creator>Rackspace Cloud / Mosso Payola</dc:creator>
		<pubDate>Wed, 10 Jun 2009 08:44:37 +0000</pubDate>
		<guid isPermaLink="false">http://izea.com/?p=4368#comment-7808</guid>
		<description>[...] This Rackspace marketing campaign seems totally unworkable, especially the direction disclosure is taking. [...]</description>
		<content:encoded><![CDATA[<p>[...] This Rackspace marketing campaign seems totally unworkable, especially the direction disclosure is taking. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andy Beard</title>
		<link>http://izea.com/universal-disclosure/comment-page-1/#comment-7807</link>
		<dc:creator>Andy Beard</dc:creator>
		<pubDate>Wed, 10 Jun 2009 07:59:19 +0000</pubDate>
		<guid isPermaLink="false">http://izea.com/?p=4368#comment-7807</guid>
		<description>Seem totally unworkable

I might use 100 different affiliate links in a day

Snippet of code?

Any disclosure has to transfer to feeds, and has to work with images off, and be totally accessible.

Thus is has to be in text form, in the posts.

There is no other alternative.</description>
		<content:encoded><![CDATA[<p>Seem totally unworkable</p>
<p>I might use 100 different affiliate links in a day</p>
<p>Snippet of code?</p>
<p>Any disclosure has to transfer to feeds, and has to work with images off, and be totally accessible.</p>
<p>Thus is has to be in text form, in the posts.</p>
<p>There is no other alternative.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

