<?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: Social media in emergencies: is there a responsibility to verify?</title>
	<atom:link href="http://sm4good.com/2012/09/20/social-media-emergencies-responsibility-verify/feed/" rel="self" type="application/rss+xml" />
	<link>http://sm4good.com/2012/09/20/social-media-emergencies-responsibility-verify/</link>
	<description>Exploring the use of digital communications tools for NGOs, non-profit organizations and to support humanitarian relief</description>
	<lastBuildDate>Tue, 07 May 2013 18:09:37 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Jakob Rogstadius</title>
		<link>http://sm4good.com/2012/09/20/social-media-emergencies-responsibility-verify/comment-page-1/#comment-144944</link>
		<dc:creator>Jakob Rogstadius</dc:creator>
		<pubDate>Fri, 21 Sep 2012 09:19:25 +0000</pubDate>
		<guid isPermaLink="false">http://sm4good.com/?p=2739#comment-144944</guid>
		<description><![CDATA[Thank you Timo for your insightful post. We will definitely take these reflections into account when discussing how to best refine the prototype and make it ready for &quot;real-world use&quot;. 
 
It may be worth clarifying that in CrisisTracker you don&#039;t work directly with curating tweets. Rather, the tool first clusters similar tweets into stories, and these stories are then the unit of information being curated in the tool. Without this first clustering step, the tool would be no different from services like Hootsuite and manual curation of millions of tweets would be completely impossible. You are free to consider the workload to still be overwhelming, but at least clustering makes it  significantly smaller. ]]></description>
		<content:encoded><![CDATA[<p>Thank you Timo for your insightful post. We will definitely take these reflections into account when discussing how to best refine the prototype and make it ready for &quot;real-world use&quot;. </p>
<p>It may be worth clarifying that in CrisisTracker you don&#039;t work directly with curating tweets. Rather, the tool first clusters similar tweets into stories, and these stories are then the unit of information being curated in the tool. Without this first clustering step, the tool would be no different from services like Hootsuite and manual curation of millions of tweets would be completely impossible. You are free to consider the workload to still be overwhelming, but at least clustering makes it  significantly smaller. </p>
]]></content:encoded>
	</item>
</channel>
</rss>
