<?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: Introducing Twitter-disclosure Slashtags</title>
	<atom:link href="http://jeffsayre.com/2010/01/06/introducing-twitter-disclosure-slashtags/feed/" rel="self" type="application/rss+xml" />
	<link>http://jeffsayre.com/2010/01/06/introducing-twitter-disclosure-slashtags/</link>
	<description>Thoughts on startups, leadership, the Web, and disruptive technologies</description>
	<lastBuildDate>Mon, 16 Apr 2012 17:24:11 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Jeff Sayre</title>
		<link>http://jeffsayre.com/2010/01/06/introducing-twitter-disclosure-slashtags/#comment-408</link>
		<dc:creator>Jeff Sayre</dc:creator>
		<pubDate>Sat, 23 Jan 2010 03:07:10 +0000</pubDate>
		<guid isPermaLink="false">http://jeffsayre.com/?p=187#comment-408</guid>
		<description>Chris-

Thank for the suggestion. I will add my proposal to the microsyntax wiki. I do believe it may be too complex of a proposal to catch on. The most important issue is discussing the need for proper disclosure coding in a microblogging context.

Your spot on in your assessment of the potential pitfalls of using tweet-specific disclosure hashtags in general. Extending your retweet scenario, what would the potential FTC ramifications be of someone RTing a tweet that originally included a disclosure hashtag but was removed due to space limitations? Could the OT (original tweeter) be improperly accused of tweeting without disclosure?

The other issue with my proposed hashtags is the use of the dollar sign. I&#039;m not sure how Twitter will treat that symbol in searches&#8212;although it should be okay since the pound sign is parsed correctly.</description>
		<content:encoded><![CDATA[<p>Chris-</p>
<p>Thank for the suggestion. I will add my proposal to the microsyntax wiki. I do believe it may be too complex of a proposal to catch on. The most important issue is discussing the need for proper disclosure coding in a microblogging context.</p>
<p>Your spot on in your assessment of the potential pitfalls of using tweet-specific disclosure hashtags in general. Extending your retweet scenario, what would the potential FTC ramifications be of someone RTing a tweet that originally included a disclosure hashtag but was removed due to space limitations? Could the OT (original tweeter) be improperly accused of tweeting without disclosure?</p>
<p>The other issue with my proposed hashtags is the use of the dollar sign. I&#8217;m not sure how Twitter will treat that symbol in searches&mdash;although it should be okay since the pound sign is parsed correctly.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Messina</title>
		<link>http://jeffsayre.com/2010/01/06/introducing-twitter-disclosure-slashtags/#comment-407</link>
		<dc:creator>Chris Messina</dc:creator>
		<pubDate>Sat, 23 Jan 2010 02:52:52 +0000</pubDate>
		<guid isPermaLink="false">http://jeffsayre.com/?p=187#comment-407</guid>
		<description>Hi Jeff,

Just got around to reading this post.

The idea is interesting, and I suggest that you document it on the microsyntax wiki: http://microsyntax.pbworks.com.

My initial feedback is that these tags don&#039;t connect to normal conventions very clearly, and would mostly confuse people. I think you are right that if they were widely adopted and became a standard convention, that issue might go away, but you should never underestimate how hard it is to get people to adopt a new behavior!

Instead, I think a better general practice is to use the URL field in the Twitter bio to link to a personal homepage, and from there, link to a disclosure statement. It&#039;s not ideal, and it&#039;s somewhat removed from the point of interaction, but one of the issues with embedding the disclosure in a tweet itself is the consequence of retweets or quoted tweets... that is, what happens when I retweet you with YOUR disclosure in my tweet? Although I wasn&#039;t paid (let&#039;s say) that creates kind of a weird situation, does it not?

Perhaps a simpler approach (though longer) would be to just use the #paidendorsement hashtag?</description>
		<content:encoded><![CDATA[<p>Hi Jeff,</p>
<p>Just got around to reading this post.</p>
<p>The idea is interesting, and I suggest that you document it on the microsyntax wiki: <a href="http://microsyntax.pbworks.com" rel="nofollow">http://microsyntax.pbworks.com</a>.</p>
<p>My initial feedback is that these tags don&#8217;t connect to normal conventions very clearly, and would mostly confuse people. I think you are right that if they were widely adopted and became a standard convention, that issue might go away, but you should never underestimate how hard it is to get people to adopt a new behavior!</p>
<p>Instead, I think a better general practice is to use the URL field in the Twitter bio to link to a personal homepage, and from there, link to a disclosure statement. It&#8217;s not ideal, and it&#8217;s somewhat removed from the point of interaction, but one of the issues with embedding the disclosure in a tweet itself is the consequence of retweets or quoted tweets&#8230; that is, what happens when I retweet you with YOUR disclosure in my tweet? Although I wasn&#8217;t paid (let&#8217;s say) that creates kind of a weird situation, does it not?</p>
<p>Perhaps a simpler approach (though longer) would be to just use the #paidendorsement hashtag?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

