<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Full Disclosure &#187; Twitter</title>
	<atom:link href="http://www.fullstopinteractive.com/blog/tag/twitter/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.fullstopinteractive.com/blog</link>
	<description>A weblog from Full Stop Interactive</description>
	<lastBuildDate>Mon, 21 Nov 2011 19:45:19 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>In Defense of Comments.</title>
		<link>http://www.fullstopinteractive.com/blog/2010/10/in-defense-of-comments/</link>
		<comments>http://www.fullstopinteractive.com/blog/2010/10/in-defense-of-comments/#comments</comments>
		<pubDate>Fri, 08 Oct 2010 17:52:39 +0000</pubDate>
		<dc:creator>Nate</dc:creator>
				<category><![CDATA[article]]></category>
		<category><![CDATA[communication]]></category>
		<category><![CDATA[Innovation]]></category>
		<category><![CDATA[Twitter]]></category>

		<guid isPermaLink="false">http://www.fullstopinteractive.com/blog/?p=1250</guid>
		<description><![CDATA[Excuse our ignorance, but at what point did it become apparent that &#8220;inline blog comments are going the way of the BBS and Gopher sites of yore&#8221;? We understand there are certain inefficiencies in the traditional way of handling comments, including but not limited to spam, follow-ups, digressions, fragmentation, trolls, and idiots. Yet we fail [...]]]></description>
			<content:encoded><![CDATA[<p><span class="first-letter">E</span>xcuse our ignorance, but at what point did it become apparent that <a href="http://cognition.happycog.com/article/is-this-thing-on">&#8220;inline blog comments are going the way of the BBS and Gopher sites of yore&#8221;</a>? We understand there are certain inefficiencies in the traditional way of handling comments, including but not limited to spam, follow-ups, digressions, fragmentation, trolls, and idiots. Yet we fail to see how the tweet-as-comment paradigm resolves any of those issues.</p>
<p><em>If</em> building a better comment system was the goal, iterating on the progress made by dedicated comment sites like Hacker News, Slashdot, Digg, Reddit, et al seems a much savvier plan than blowing it up and starting over. While we stop short of praising comment threading, voting, and flagging as panaceas, it does seem undeniable that Twitter solves none of those issues, introducing instead a host of its own.</p>
<p>By replacing comments with tweets, Happy Cog twice undermines its audience, first by contributing to the general Internet noise pollution (as well as the specific article comment thread noise) and second by trivializing the resulting discussion. Artificial brevity is a flaw not a feature. It makes substantive conversation if not impossible at least heavily discouraged. Ex-communicating the indefinite length, local comment as the fundamental unit of a larger intellectual discussion is inimical to Internet culture and, most importantly, learning — which we presume is a core value of any blog post.</p>
<p>But perhaps we&#8217;re unfair. We tremble at the thought of standing in the  way of progress and stick-in-the-mud traditionalism is hardly our  philosophy. Maybe the goal was to simply make it easier for people to  leave feedback on the article. In that case, Cognition has succeeded wildly. It is a bold move (though perhaps a bit shy of &#8220;brilliant&#8221; as many <span style="text-decoration: line-through;">commenters</span> tweeters gush)  worthy of applause. If upsetting the rotting apple cart of blog commenting is one outcome, it won&#8217;t all have been for naught.</p>
<p>Our metaphorical fingers are crossed that Happy Cog instituted this system not as part of a grand PR scheme but in the sincere belief that it offered at least the chance of a better model by holding commenters accountable and elevating responding blogs to first-class comment citizens. If that is the case, we humbly suggest supplementing Twitter and blogs with good, old-fashioned comments à la <a href="http://disqus.com/">Disqus</a> because, on some level, a well-considered comment system is irreducibly complex. It requires a spectrum of <em>in situ</em> response lengths to adequately simulate real conversation.<sup><a href="http://www.fullstopinteractive.com/blog/2010/10/in-defense-of-comments/#footnote_0_1250" id="identifier_0_1250" class="footnote-link footnote-identifier-link" title="And, if beggars were choosers, things like voting, threading, burying,  author highlighting, comment email or RSS subscriptions, etc. There is  much room for improvement.">1</a></sup> By striving for &#8220;simple&#8221; we fear Happy Cog has strayed into &#8220;simplistic.&#8221; Unless changes are made, commenting on a Cognition post is an exercise in futility, home only to well-meaning pats-on-the-back and vapid gestures.</p>
<p>Let us be clear: we have no objection to decentralizing, extending, or otherwise improving the conversation. We do, however, oppose its infantilization.</p>
<p>In Zeldman we trust.</p>
<ol class="footnotes"><li id="footnote_0_1250" class="footnote">And, if beggars were choosers, things like voting, threading, burying,  author highlighting, comment email or RSS subscriptions, etc. There is  much room for improvement.</li></ol>]]></content:encoded>
			<wfw:commentRss>http://www.fullstopinteractive.com/blog/2010/10/in-defense-of-comments/feed/</wfw:commentRss>
		<slash:comments>19</slash:comments>
		</item>
		<item>
		<title>Here They Come to Snuff The Rooster.</title>
		<link>http://www.fullstopinteractive.com/blog/2009/12/here-they-come-to-snuff-the-rooster/</link>
		<comments>http://www.fullstopinteractive.com/blog/2009/12/here-they-come-to-snuff-the-rooster/#comments</comments>
		<pubDate>Tue, 08 Dec 2009 05:27:57 +0000</pubDate>
		<dc:creator>Jay</dc:creator>
				<category><![CDATA[short]]></category>
		<category><![CDATA[Twitter]]></category>

		<guid isPermaLink="false">http://www.fullstopinteractive.com/blog/?p=285</guid>
		<description><![CDATA[Over the weekend, Dean Allen unexpectedly killed his survival-of-the-funniest Twitter curation site Favrd with a glib, abrupt, and profane announcement. The nugget: There are still lots of clever and funny things to read every day, but finding these is no longer a challenge – you already follow your sources. Sites like this one now serve [...]]]></description>
			<content:encoded><![CDATA[<p><span class="first-letter">O</span>ver the weekend, <a title="Textism" href="http://twitter.com/textism" target="_self">Dean Allen</a> unexpectedly killed his survival-of-the-funniest Twitter curation site <a title="Favrd" href="http://favrd.textism.com/" target="_self">Favrd</a> with a glib, abrupt, and profane announcement. The nugget:</p>
<blockquote><p>There are still lots of clever and funny things to read every day, but finding these is no longer a challenge – you already follow your sources. Sites like this one now serve mainly as fuel for emotional up-fuckedness in the guise of a game.</p></blockquote>
<p>Although I never had much luck with Favrd—my most favorited tweets only gathered a handful of stars, the majority coming from fellow Pittsburgher <a title="CranberryPerson" href="https://twitter.com/CranberryPerson" target="_self">Jason Logue</a>—it undoubtedly sharpened my game. Competing for laughs with the likes of <a title="Badbanana" href="http://twitter.com/badBanana" target="_self">Tim Siedell</a>, <a title="Sween" href="http://twitter.com/SWEEN" target="_self">Jason Sweeney</a>, and <a title="DWineman" href="http://twitter.com/dwineman" target="_self">Dan Wineman</a> will have that effect. But while Favrd&#8217;s rising tide raised all tweets, it also created the conditions that ultimately forced its demise. What started as a daily bulletin board for Twitter&#8217;s funniest quickly mutated into a destination for shameless ego-boosting. This is not a new concept, Favrd just made it quantifiable.</p>
<p>Since I come not only to bury Favrd, but also to praise it, Favrd had another unintended consequence: people became friends. They didn&#8217;t &#8220;friend&#8221; each other, mind you. They became <a title="Tweetup" href="http://www.flickr.com/photos/sween/3787347680/" target="_self">real-life, meatspace friends</a>. And out of this accidental syndicate came tweetups, collaborations, and iPhone apps. It also spawned two, uh, &#8220;short films&#8221;: SeoulBrother&#8217;s <a title="Eff-You Gruber" href="http://www.vimeo.com/7345725" target="_self">two-fisted eff-you</a> to John Gruber and <a title="Skyward: Birdhouse Stories" href="http://www.vimeo.com/4271613" target="_self">Skyward</a>, Geoff Barnes&#8217; &#8220;We Are The World&#8221; to the tweet incubator app, <a title="Birdhouse" href="http://birdhouseapp.com/" target="_self">Birdhouse</a>—not to mention Birdhouse itself. Not a bad legacy (your move, <a title="Favstar" href="http://www.favstar.fm" target="_self">Favstar</a>).</p>
<p>If you&#8217;re looking for a proper eulogy, I&#8217;m hardly the person to deliver it. Besides, there are <a href="http://weblog.muledesign.com/2009/12/the_death_of_favrd.php" target="_self">plenty</a> <a href="http://www.zeldman.com/2009/12/06/the-stars-look-down/" target="_self">out</a> <a href="http://blog.texburgher.com/post/272666147/in-praise-of-castration-its-not-that-i-wont" target="_self">there</a> <a href="http://www.downloadsquad.com/2009/12/07/favrd-a-beloved-twitter-favorites-tracker-shuts-down/" target="_self">already</a>. But I can&#8217;t say I&#8217;m not gonna miss it. Favrd is dead. Long live Favrd.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.fullstopinteractive.com/blog/2009/12/here-they-come-to-snuff-the-rooster/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

