<?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: New microsyntax for Twitter: three pointers and the slasher</title>
	<atom:link href="http://factoryjoe.com/blog/2009/11/08/new-microsyntax-for-twitter-three-pointers-and-the-slasher/feed/" rel="self" type="application/rss+xml" />
	<link>http://factoryjoe.com/blog/2009/11/08/new-microsyntax-for-twitter-three-pointers-and-the-slasher/</link>
	<description>This can all be made better. Ready? Begin.</description>
	<lastBuildDate>Sat, 13 Mar 2010 14:54:17 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jay Bienvenu</title>
		<link>http://factoryjoe.com/blog/2009/11/08/new-microsyntax-for-twitter-three-pointers-and-the-slasher/comment-page-1/#comment-116994</link>
		<dc:creator>Jay Bienvenu</dc:creator>
		<pubDate>Wed, 27 Jan 2010 08:37:58 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/?p=1760#comment-116994</guid>
		<description>For some time now I&#039;ve had an idea for &quot;bangtags&quot; that would identify characteristics of linked content such as video or explicit content. I used the exclamation point rather than the hashmark for two reasons: to avoid confusion with coincidental nonstandardized hashtags, and to denote the fact that the tag alerts the reader to some characteristic of the linked content that might be problematic. 

I thought about augmenting the slashtags with this proposal, and decided not to because the slash doesn&#039;t denote caution like the bang does. 

My basic proposal for bangtags is at my website link. What do you think about this idea?</description>
		<content:encoded><![CDATA[<p>For some time now I&#8217;ve had an idea for &#8220;bangtags&#8221; that would identify characteristics of linked content such as video or explicit content. I used the exclamation point rather than the hashmark for two reasons: to avoid confusion with coincidental nonstandardized hashtags, and to denote the fact that the tag alerts the reader to some characteristic of the linked content that might be problematic. </p>
<p>I thought about augmenting the slashtags with this proposal, and decided not to because the slash doesn&#8217;t denote caution like the bang does. </p>
<p>My basic proposal for bangtags is at my website link. What do you think about this idea?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: A Guide to Writing Good on Twitter &#171; Coffee Conversations</title>
		<link>http://factoryjoe.com/blog/2009/11/08/new-microsyntax-for-twitter-three-pointers-and-the-slasher/comment-page-1/#comment-116963</link>
		<dc:creator>A Guide to Writing Good on Twitter &#171; Coffee Conversations</dc:creator>
		<pubDate>Tue, 26 Jan 2010 10:06:40 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/?p=1760#comment-116963</guid>
		<description>[...] it to be extremely convenient. They have gained acceptance among a lot of users lately. They were introduced by Chris Messina, the same dude who suggested [...]</description>
		<content:encoded><![CDATA[<p>[...] it to be extremely convenient. They have gained acceptance among a lot of users lately. They were introduced by Chris Messina, the same dude who suggested [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Logan</title>
		<link>http://factoryjoe.com/blog/2009/11/08/new-microsyntax-for-twitter-three-pointers-and-the-slasher/comment-page-1/#comment-115807</link>
		<dc:creator>Logan</dc:creator>
		<pubDate>Thu, 07 Jan 2010 07:49:58 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/?p=1760#comment-115807</guid>
		<description>I vote that we make RT and /via the same thing. Having RT seems to break the syntax, unless we move it to the end: /rt. As it is, it seems like there are too many ways to give credit when I believe really only one is needed. I understand the differences between RT, via, OH, and by, but there just isn&#039;t enough of a difference or enough of a benefit to justify the complexity. /via can technically mean any of these, and therefore seems the best suited to replace them all. 

That said, I really like the /cc and /me concepts. Great stuff. Very useful.</description>
		<content:encoded><![CDATA[<p>I vote that we make RT and /via the same thing. Having RT seems to break the syntax, unless we move it to the end: /rt. As it is, it seems like there are too many ways to give credit when I believe really only one is needed. I understand the differences between RT, via, OH, and by, but there just isn&#8217;t enough of a difference or enough of a benefit to justify the complexity. /via can technically mean any of these, and therefore seems the best suited to replace them all. </p>
<p>That said, I really like the /cc and /me concepts. Great stuff. Very useful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Introducing Twitter-disclosure Slashtags</title>
		<link>http://factoryjoe.com/blog/2009/11/08/new-microsyntax-for-twitter-three-pointers-and-the-slasher/comment-page-1/#comment-115801</link>
		<dc:creator>Introducing Twitter-disclosure Slashtags</dc:creator>
		<pubDate>Wed, 06 Jan 2010 23:35:11 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/?p=1760#comment-115801</guid>
		<description>[...] To make disclosure easy on Twitter, I’m proposing a set of Twitter-disclosure slashtags. [...]</description>
		<content:encoded><![CDATA[<p>[...] To make disclosure easy on Twitter, I’m proposing a set of Twitter-disclosure slashtags. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rivolutionary use of Slashtags, new microsyntax for Twitter</title>
		<link>http://factoryjoe.com/blog/2009/11/08/new-microsyntax-for-twitter-three-pointers-and-the-slasher/comment-page-1/#comment-114466</link>
		<dc:creator>Rivolutionary use of Slashtags, new microsyntax for Twitter</dc:creator>
		<pubDate>Sun, 13 Dec 2009 16:54:52 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/?p=1760#comment-114466</guid>
		<description>[...] I read this amazing post from Chris Messina writing about slashtags, that I called the TwitterTags 2.0 so the new Twitter [...]</description>
		<content:encoded><![CDATA[<p>[...] I read this amazing post from Chris Messina writing about slashtags, that I called the TwitterTags 2.0 so the new Twitter [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Messina</title>
		<link>http://factoryjoe.com/blog/2009/11/08/new-microsyntax-for-twitter-three-pointers-and-the-slasher/comment-page-1/#comment-114359</link>
		<dc:creator>Chris Messina</dc:creator>
		<pubDate>Fri, 04 Dec 2009 23:08:35 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/?p=1760#comment-114359</guid>
		<description>@Michael Kozakewich: I&#039;ve been meaning to redesign this blog for a while.

I&#039;ll make sure to separate the tweets from the local comments. Thanks for the suggestion.</description>
		<content:encoded><![CDATA[<p>@Michael Kozakewich: I&#8217;ve been meaning to redesign this blog for a while.</p>
<p>I&#8217;ll make sure to separate the tweets from the local comments. Thanks for the suggestion.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Kozakewich</title>
		<link>http://factoryjoe.com/blog/2009/11/08/new-microsyntax-for-twitter-three-pointers-and-the-slasher/comment-page-1/#comment-114356</link>
		<dc:creator>Michael Kozakewich</dc:creator>
		<pubDate>Fri, 04 Dec 2009 21:46:04 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/?p=1760#comment-114356</guid>
		<description>(Chris, is it possible to move the &#039;Post a Comment&#039; form above the bazillion twitter comments?)

Wayan, RT hasn&#039;t gone anywhere. Twitter has added a &quot;Retweet&quot; link, which will do a hard retweet of someone&#039;s tweet, but you can still &quot;RT @so-and-so...&quot; if you want. I&#039;ve seen some of those RTs, lately.
I don&#039;t think Twitter has ever touched RTs.

However, apps like Tweetie have historically added their own functionality to Twitter, such as an actual Retweet button, and they should now give people a choice to decide which &#039;retweet&#039; they mean. TweetDeck, for example, asks users which one they mean, with the option of setting that to &quot;do-this-and-don&#039;t-ask-again.&quot;
(i.e. It&#039;s your fault for relying on those apps)</description>
		<content:encoded><![CDATA[<p>(Chris, is it possible to move the &#8216;Post a Comment&#8217; form above the bazillion twitter comments?)</p>
<p>Wayan, RT hasn&#8217;t gone anywhere. Twitter has added a &#8220;Retweet&#8221; link, which will do a hard retweet of someone&#8217;s tweet, but you can still &#8220;RT @so-and-so&#8230;&#8221; if you want. I&#8217;ve seen some of those RTs, lately.<br />
I don&#8217;t think Twitter has ever touched RTs.</p>
<p>However, apps like Tweetie have historically added their own functionality to Twitter, such as an actual Retweet button, and they should now give people a choice to decide which &#8216;retweet&#8217; they mean. TweetDeck, for example, asks users which one they mean, with the option of setting that to &#8220;do-this-and-don&#8217;t-ask-again.&#8221;<br />
(i.e. It&#8217;s your fault for relying on those apps)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wayan</title>
		<link>http://factoryjoe.com/blog/2009/11/08/new-microsyntax-for-twitter-three-pointers-and-the-slasher/comment-page-1/#comment-114355</link>
		<dc:creator>Wayan</dc:creator>
		<pubDate>Fri, 04 Dec 2009 20:30:59 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/?p=1760#comment-114355</guid>
		<description>And RT is even less letters &amp; better knowledge transfer than /via.  

Bring Back the RT!</description>
		<content:encoded><![CDATA[<p>And RT is even less letters &amp; better knowledge transfer than /via.  </p>
<p>Bring Back the RT!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Kozakewich</title>
		<link>http://factoryjoe.com/blog/2009/11/08/new-microsyntax-for-twitter-three-pointers-and-the-slasher/comment-page-1/#comment-114298</link>
		<dc:creator>Michael Kozakewich</dc:creator>
		<pubDate>Wed, 02 Dec 2009 20:45:13 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/?p=1760#comment-114298</guid>
		<description>My concern, a few months ago, was that we should put quotes around RTs and then add whatever afterwards, or do some sort of annotation syntax before annotating with our own remarks. I think the problem is that there&#039;s no real way to annotate in Twitter. We could cram what we can in the remaining space beside someone&#039;s tweet (I say at the end, to avoid an out-of-context phrase preceding the tweet), or we could link to someone else&#039;s RT in our tweet (if Twitter had its own url shortener for tweets, it would be easier), because RTing now seems to be similar to linking to others&#039; tweets.

At the moment, tweets have the link http://twitter.com/[usernmae]/status/##########
if it was http://s.twitter.com/?????????? or such, it would save us twenty characters. Even tweets.twitter.com would save.

Anyway, Twitter could have a function that allowed us to click &#039;Retweet&#039;, give us a whole 140 characters to type an annotation (&quot;I really like this article, but feel that [blah blah issue] should be handled [blah blah matter].&quot;) and then post a link to the RT with the annotation tweet.

Or something.

Things being as they are, at this moment, I still see a lot of &quot;I don&#039;t think so. RT @so-and-so I really would like @first-person to kiss a frog,&quot; the beginning of which makes no sense until you realize it&#039;s a RT and read the second half of the tweet.


I&#039;m an advocate of something like the following, for now:

RT @so-and-so : &quot;I really would like @first-person to kiss a frog&quot; I don&#039;t think so!</description>
		<content:encoded><![CDATA[<p>My concern, a few months ago, was that we should put quotes around RTs and then add whatever afterwards, or do some sort of annotation syntax before annotating with our own remarks. I think the problem is that there&#8217;s no real way to annotate in Twitter. We could cram what we can in the remaining space beside someone&#8217;s tweet (I say at the end, to avoid an out-of-context phrase preceding the tweet), or we could link to someone else&#8217;s RT in our tweet (if Twitter had its own url shortener for tweets, it would be easier), because RTing now seems to be similar to linking to others&#8217; tweets.</p>
<p>At the moment, tweets have the link <a href="http://twitter.com/usernmae/status/##########" rel="nofollow">http://twitter.com/usernmae/status/##########</a><br />
if it was <a href="http://s.twitter.com/??????????" rel="nofollow">http://s.twitter.com/??????????</a> or such, it would save us twenty characters. Even tweets.twitter.com would save.</p>
<p>Anyway, Twitter could have a function that allowed us to click &#8216;Retweet&#8217;, give us a whole 140 characters to type an annotation (&#8220;I really like this article, but feel that [blah blah issue] should be handled [blah blah matter].&#8221;) and then post a link to the RT with the annotation tweet.</p>
<p>Or something.</p>
<p>Things being as they are, at this moment, I still see a lot of &#8220;I don&#8217;t think so. RT @so-and-so I really would like @first-person to kiss a frog,&#8221; the beginning of which makes no sense until you realize it&#8217;s a RT and read the second half of the tweet.</p>
<p>I&#8217;m an advocate of something like the following, for now:</p>
<p>RT @so-and-so : &#8220;I really would like @first-person to kiss a frog&#8221; I don&#8217;t think so!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jack Repenning</title>
		<link>http://factoryjoe.com/blog/2009/11/08/new-microsyntax-for-twitter-three-pointers-and-the-slasher/comment-page-1/#comment-114297</link>
		<dc:creator>Jack Repenning</dc:creator>
		<pubDate>Wed, 02 Dec 2009 16:51:12 +0000</pubDate>
		<guid isPermaLink="false">http://factoryjoe.com/blog/?p=1760#comment-114297</guid>
		<description>@Michael Kozakewich: while I&#039;m sympathetic with your desire to simplify, I don&#039;t see what you&#039;re suggesting for the case of &quot;forwarding with annotation.&quot; The un-annotated RT was already widely discouraged before Twitter commandeered it for their &quot;un-annotated and masquerading as someone else&quot; feature (which perhaps ought better to be called &quot;channelling&quot; ;-) 

Consider the real-life metaphore: at a party or in a pub, when you want to introduce two friends, you don&#039;t grab them and mash them face to face, you add something: &quot;This is Rick, we went to high-school together&quot; or &quot;Do you know Jenny? She&#039;s VP of marketing and IBM&quot; or &quot;Frank here can put three pool balls in his mouth!&quot;</description>
		<content:encoded><![CDATA[<p>@Michael Kozakewich: while I&#8217;m sympathetic with your desire to simplify, I don&#8217;t see what you&#8217;re suggesting for the case of &#8220;forwarding with annotation.&#8221; The un-annotated RT was already widely discouraged before Twitter commandeered it for their &#8220;un-annotated and masquerading as someone else&#8221; feature (which perhaps ought better to be called &#8220;channelling&#8221; <img src='http://factoryjoe.com/blog/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' />  </p>
<p>Consider the real-life metaphore: at a party or in a pub, when you want to introduce two friends, you don&#8217;t grab them and mash them face to face, you add something: &#8220;This is Rick, we went to high-school together&#8221; or &#8220;Do you know Jenny? She&#8217;s VP of marketing and IBM&#8221; or &#8220;Frank here can put three pool balls in his mouth!&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
