<?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: Choosing between Twitter, live blogging or fast publishing</title>
	<atom:link href="http://www.blogherald.com/2008/04/28/choosing-between-twitter-live-blogging-or-fast-publishing/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.blogherald.com/2008/04/28/choosing-between-twitter-live-blogging-or-fast-publishing/</link>
	<description>The leading source of news covering social media and the blogosphere.</description>
	<lastBuildDate>Mon, 13 Feb 2012 09:18:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Prashanth</title>
		<link>http://www.blogherald.com/2008/04/28/choosing-between-twitter-live-blogging-or-fast-publishing/comment-page-1/#comment-429524</link>
		<dc:creator>Prashanth</dc:creator>
		<pubDate>Tue, 29 Apr 2008 16:14:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogherald.com/2008/04/28/chosing-between-twitter-live-blogging-or-fast-publishing/#comment-429524</guid>
		<description>I go for Fast Publishing.
I love coveritlive, it&#039;s a great ajaxy tool with loads of features.
I love twitter too, the best part of Twitter is you will find one or the other way to update!
But the major drawback of these two is being, as already mentioned content is not on your blog &amp; fetched from somewhere else. You will be loosing traffic from major traffic source &lt;b&gt;Search Engines&lt;/b&gt;</description>
		<content:encoded><![CDATA[<p>I go for Fast Publishing.<br />
I love coveritlive, it&#8217;s a great ajaxy tool with loads of features.<br />
I love twitter too, the best part of Twitter is you will find one or the other way to update!<br />
But the major drawback of these two is being, as already mentioned content is not on your blog &amp; fetched from somewhere else. You will be loosing traffic from major traffic source <b>Search Engines</b></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anne Helmond</title>
		<link>http://www.blogherald.com/2008/04/28/choosing-between-twitter-live-blogging-or-fast-publishing/comment-page-1/#comment-429194</link>
		<dc:creator>Anne Helmond</dc:creator>
		<pubDate>Tue, 29 Apr 2008 08:22:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogherald.com/2008/04/28/chosing-between-twitter-live-blogging-or-fast-publishing/#comment-429194</guid>
		<description>@Erwin Blom: both as a publisher and a receiver I see the advantages of Twitter because it allows for real time conversation. Twitter is perfect if you keep track of conference tweets as they happen. It is a moment tool and not one that allows you to read the conversation a day later because of its lack of coherence.

It does not have to be an either/or situation. I can imagine using Twitter as the live blogging tool and then at the end of the conference taking an hour to wrap your tweets up into a coherent blog post. Turn your tweets into an archivable and readable blog post.

@Jay Kelly: Great point. I think converting your CoverIt Live session into a blog post offers a lot of value to both your blog and your readers.

@Sue: I also rather take an extra thirty minutes to convert my notes or tweets into a blog post. I think the latter is an excellent solution.</description>
		<content:encoded><![CDATA[<p>@Erwin Blom: both as a publisher and a receiver I see the advantages of Twitter because it allows for real time conversation. Twitter is perfect if you keep track of conference tweets as they happen. It is a moment tool and not one that allows you to read the conversation a day later because of its lack of coherence.</p>
<p>It does not have to be an either/or situation. I can imagine using Twitter as the live blogging tool and then at the end of the conference taking an hour to wrap your tweets up into a coherent blog post. Turn your tweets into an archivable and readable blog post.</p>
<p>@Jay Kelly: Great point. I think converting your CoverIt Live session into a blog post offers a lot of value to both your blog and your readers.</p>
<p>@Sue: I also rather take an extra thirty minutes to convert my notes or tweets into a blog post. I think the latter is an excellent solution.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sue @ TameBay</title>
		<link>http://www.blogherald.com/2008/04/28/choosing-between-twitter-live-blogging-or-fast-publishing/comment-page-1/#comment-429168</link>
		<dc:creator>Sue @ TameBay</dc:creator>
		<pubDate>Tue, 29 Apr 2008 07:33:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogherald.com/2008/04/28/chosing-between-twitter-live-blogging-or-fast-publishing/#comment-429168</guid>
		<description>Fast publishing - as both a writer and a reader. If I&#039;m not *at* the conference, that thirty minutes isn&#039;t going to make that much difference to me - I can wait for your blog post. I&#039;d rather have coherence than speed that leaves me with more questions than answers. 

What I have seen recently is people using Twitter to take notes which they then turn into a blog post, which might be a good dual-location solution?</description>
		<content:encoded><![CDATA[<p>Fast publishing &#8211; as both a writer and a reader. If I&#8217;m not *at* the conference, that thirty minutes isn&#8217;t going to make that much difference to me &#8211; I can wait for your blog post. I&#8217;d rather have coherence than speed that leaves me with more questions than answers. </p>
<p>What I have seen recently is people using Twitter to take notes which they then turn into a blog post, which might be a good dual-location solution?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jay Kelly</title>
		<link>http://www.blogherald.com/2008/04/28/choosing-between-twitter-live-blogging-or-fast-publishing/comment-page-1/#comment-428978</link>
		<dc:creator>Jay Kelly</dc:creator>
		<pubDate>Mon, 28 Apr 2008 22:53:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogherald.com/2008/04/28/chosing-between-twitter-live-blogging-or-fast-publishing/#comment-428978</guid>
		<description>Great thoughts. &#039;It&#039;s the archive that counts&#039; is a very good reason to prefer fast publishing.

I&#039;m wondering, though, if converting a Cover It Live session to a post or three might be the best of both worlds.

You get the interactivity of Cover It Live with the archiving of a regular blog post.

Thanks for making me think!</description>
		<content:encoded><![CDATA[<p>Great thoughts. &#8216;It&#8217;s the archive that counts&#8217; is a very good reason to prefer fast publishing.</p>
<p>I&#8217;m wondering, though, if converting a Cover It Live session to a post or three might be the best of both worlds.</p>
<p>You get the interactivity of Cover It Live with the archiving of a regular blog post.</p>
<p>Thanks for making me think!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: erwin blom</title>
		<link>http://www.blogherald.com/2008/04/28/choosing-between-twitter-live-blogging-or-fast-publishing/comment-page-1/#comment-428952</link>
		<dc:creator>erwin blom</dc:creator>
		<pubDate>Mon, 28 Apr 2008 21:59:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.blogherald.com/2008/04/28/chosing-between-twitter-live-blogging-or-fast-publishing/#comment-428952</guid>
		<description>You prefer it a a publisher, but you should ask the question to the receiver. I am both and understand you. But twitter is more fun than fast blogging because it combines real time publishing with real time conversation. Archive or no archive.</description>
		<content:encoded><![CDATA[<p>You prefer it a a publisher, but you should ask the question to the receiver. I am both and understand you. But twitter is more fun than fast blogging because it combines real time publishing with real time conversation. Archive or no archive.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

