<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:rawvoice="http://www.rawvoice.com/rawvoiceRssModule/"
	>
<channel>
	<title>Comments on: Budget09: the tech take and lessons learned</title>
	<atom:link href="http://www.accmanpro.com/2009/04/22/budget09-the-tech-take-and-lessons-learned/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.accmanpro.com/2009/04/22/budget09-the-tech-take-and-lessons-learned/</link>
	<description></description>
	<lastBuildDate>Thu, 09 Feb 2012 10:01:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Mark Lee</title>
		<link>http://www.accmanpro.com/2009/04/22/budget09-the-tech-take-and-lessons-learned/comment-page-1/#comment-6214</link>
		<dc:creator>Mark Lee</dc:creator>
		<pubDate>Fri, 24 Apr 2009 16:56:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.accmanpro.com/?p=4634#comment-6214</guid>
		<description>Well done Dennis.  You worked hard on this.

Took me a while to understand what CiL was adding. I thought it was to aggregate various related twitter hashtags into one stream.  Suspect it was also for people who couldn&#039;t access a constant twitter stream in tweetdeck or a similar application.

Dominating the choice of hashtag and getting it out there early enough is clearly key as otherwise tweets have to be short enough to leave space for &gt;1 hashtag which is daft.  So well done on #budget09 - the obvious one with the benefit of hindsight.

I struggled to watch the speech on tv, post tweets, make some notes for later use and monitor the other tweets using #budget09.  I&#039;m not a natural multitasker. (well not that much anyway. I don&#039;t know how you do it!)</description>
		<content:encoded><![CDATA[<p>Well done Dennis.  You worked hard on this.</p>
<p>Took me a while to understand what CiL was adding. I thought it was to aggregate various related twitter hashtags into one stream.  Suspect it was also for people who couldn&#8217;t access a constant twitter stream in tweetdeck or a similar application.</p>
<p>Dominating the choice of hashtag and getting it out there early enough is clearly key as otherwise tweets have to be short enough to leave space for &gt;1 hashtag which is daft.  So well done on #budget09 &#8211; the obvious one with the benefit of hindsight.</p>
<p>I struggled to watch the speech on tv, post tweets, make some notes for later use and monitor the other tweets using #budget09.  I&#8217;m not a natural multitasker. (well not that much anyway. I don&#8217;t know how you do it!)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: New Clickbank Products for April 23, 2009</title>
		<link>http://www.accmanpro.com/2009/04/22/budget09-the-tech-take-and-lessons-learned/comment-page-1/#comment-6213</link>
		<dc:creator>New Clickbank Products for April 23, 2009</dc:creator>
		<pubDate>Thu, 23 Apr 2009 13:53:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.accmanpro.com/?p=4634#comment-6213</guid>
		<description>[...]  Budget09: the tech take and lessons learned  (accmanpro.com) [...]</description>
		<content:encoded><![CDATA[<p>[...]  Budget09: the tech take and lessons learned  (accmanpro.com) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Architectural Technologist - Architects want protection of function &#171; The Konstrukshon Weblog</title>
		<link>http://www.accmanpro.com/2009/04/22/budget09-the-tech-take-and-lessons-learned/comment-page-1/#comment-6212</link>
		<dc:creator>Architectural Technologist - Architects want protection of function &#171; The Konstrukshon Weblog</dc:creator>
		<pubDate>Thu, 23 Apr 2009 11:58:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.accmanpro.com/?p=4634#comment-6212</guid>
		<description>[...]  Budget09: the tech take and lessons learned  (accmanpro.com) [...]</description>
		<content:encoded><![CDATA[<p>[...]  Budget09: the tech take and lessons learned  (accmanpro.com) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Budget coverage using CoveritLive to capture tweets &#124; Stuart Glendinning Hall</title>
		<link>http://www.accmanpro.com/2009/04/22/budget09-the-tech-take-and-lessons-learned/comment-page-1/#comment-6211</link>
		<dc:creator>Budget coverage using CoveritLive to capture tweets &#124; Stuart Glendinning Hall</dc:creator>
		<pubDate>Thu, 23 Apr 2009 07:24:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.accmanpro.com/?p=4634#comment-6211</guid>
		<description>[...] Dennis Howlett deployed CoveritLive to good effect on the ICAEW&#8217;s online communities today to cover the UK budget as it unfolded, as caught (via hash tags) by individual tweets. His reflections on the project here. [...]</description>
		<content:encoded><![CDATA[<p>[...] Dennis Howlett deployed CoveritLive to good effect on the ICAEW&#8217;s online communities today to cover the UK budget as it unfolded, as caught (via hash tags) by individual tweets. His reflections on the project here. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MCCIA workshop: Intellectual property Right awarness, acquisition and commercialization - 24 April &#124; PuneTech</title>
		<link>http://www.accmanpro.com/2009/04/22/budget09-the-tech-take-and-lessons-learned/comment-page-1/#comment-6210</link>
		<dc:creator>MCCIA workshop: Intellectual property Right awarness, acquisition and commercialization - 24 April &#124; PuneTech</dc:creator>
		<pubDate>Thu, 23 Apr 2009 05:29:12 +0000</pubDate>
		<guid isPermaLink="false">http://www.accmanpro.com/?p=4634#comment-6210</guid>
		<description>[...]  Budget09: the tech take and lessons learned  (accmanpro.com) [...]</description>
		<content:encoded><![CDATA[<p>[...]  Budget09: the tech take and lessons learned  (accmanpro.com) [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

