<?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>Joho the Blog &#187; boston marathon</title>
	<atom:link href="http://www.hyperorg.com/blogger/tag/boston-marathon/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.hyperorg.com/blogger</link>
	<description>Let's just see what happens</description>
	<lastBuildDate>Sat, 15 Jun 2013 21:48:22 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
		<item>
		<title>Marathon</title>
		<link>http://www.hyperorg.com/blogger/2013/04/16/12780/</link>
		<comments>http://www.hyperorg.com/blogger/2013/04/16/12780/#comments</comments>
		<pubDate>Tue, 16 Apr 2013 17:09:33 +0000</pubDate>
		<dc:creator>davidw</dc:creator>
				<category><![CDATA[misc]]></category>
		<category><![CDATA[boston marathon]]></category>
		<category><![CDATA[poems]]></category>
		<category><![CDATA[poetry]]></category>

		<guid isPermaLink="false">http://www.hyperorg.com/blogger/?p=12780</guid>
		<description><![CDATA[Everything happens by ones. Each step Each cobble Each mile Each leg crossing a line. Then in a moment we close our eyes and remember how the sea&#8217;s front edge paws at its shore. April 16, 2013 Please remember that according to the official Rules of Blogging, on the Web we must forgive one another&#8217;s [...]]]></description>
				<content:encoded><![CDATA[<blockquote>
<p>Everything happens by ones.<br />
Each step<br />
Each cobble<br />
Each mile<br />
Each leg<br />
crossing a line.</p>
<p>Then in a moment<br />
we close our eyes<br />
and remember how <br />
the sea&#8217;s front edge<br />
paws at its shore.</p>
<p><em>April 16, 2013</em></p>
</blockquote>
<p>Please remember that according to the official Rules of Blogging, on the Web we must forgive one another&#8217;s bad poetry</p>
]]></content:encoded>
			<wfw:commentRss>http://www.hyperorg.com/blogger/2013/04/16/12780/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>[misc][2b2k] Making Twitter better for disasters</title>
		<link>http://www.hyperorg.com/blogger/2013/04/16/misc2b2k-making-twitter-better-for-disasters/</link>
		<comments>http://www.hyperorg.com/blogger/2013/04/16/misc2b2k-making-twitter-better-for-disasters/#comments</comments>
		<pubDate>Tue, 16 Apr 2013 15:13:08 +0000</pubDate>
		<dc:creator>davidw</dc:creator>
				<category><![CDATA[everythingIsMiscellaneous]]></category>
		<category><![CDATA[journalism]]></category>
		<category><![CDATA[2b2k]]></category>
		<category><![CDATA[boston marathon]]></category>
		<category><![CDATA[everythingismisc]]></category>
		<category><![CDATA[twitter]]></category>

		<guid isPermaLink="false">http://www.hyperorg.com/blogger/?p=12777</guid>
		<description><![CDATA[I had both CNN and Twitter on yesterday all afternoon, looking for news about the Boston Marathon bombings. I have not done a rigorous analysis (nor will I, nor have I ever), but it felt to me that Twitter put forward more and more varied claims about the situation, and reacted faster to misstatements. CNN [...]]]></description>
				<content:encoded><![CDATA[<p>I had both CNN and Twitter on yesterday all afternoon, looking for news about the Boston Marathon bombings. I have not done a rigorous analysis (nor will I, nor have I ever), but it felt to me that Twitter put forward more and more varied claims about the situation, and reacted faster to misstatements. CNN plodded along, but didn&#8217;t feel more reliable overall. This seems predictable given the unfiltered (or post-filtered) nature of Twitter. </p>
<p>But Twitter also ran into some scaling problems for me yesterday. I follow about 500 people on Twitter, which gives my stream a pace and variety that I find helpful on a normal day. But yesterday afternoon, the stream roared by, and approached <a href="http://web2expo.blip.tv/file/1277460/">filter failure</a>. A couple of changes would help: </p>
<p> First,  let us sort by most retweeted. When I&#8217;m in my &#8220;home stream,&#8221; let me choose a frequency of tweets so that the scrolling doesn&#8217;t become unwatchable; use the frequency to determine the threshold for the number of retweets required. (Alternatively: simply highlight highly re-tweeted tweets.) </p>
<p> Second, let us mute based on hashtag or by user. Some Twitter cascades I just don&#8217;t care about. For example, I don&#8217;t want to hear play-by-plays of the World Series, and I know that many of the people who follow me get seriously annoyed when I suddenly am tweeting twice a minute during a presidential debate. So let us temporarily suppress tweet streams we don&#8217;t care about. </p>
<p> It is a lesson of the Web that as services scale up, they need to provide more and more ways of filtering. Twitter had &#8220;follow&#8221; as an initial filter, and users then came up with hashtags as a second filter. It&#8217;s time for a new round as Twitter becomes an essential part of our news ecosystem.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.hyperorg.com/blogger/2013/04/16/misc2b2k-making-twitter-better-for-disasters/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>

<!-- Dynamic page generated in 0.325 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2013-06-16 05:31:07 -->