<?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: How libraries can learn from Twitter</title>
	<atom:link href="http://www.paulhagon.com/blog/2009/05/29/how-libraries-can-learn-from-twitter/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.paulhagon.com/blog/2009/05/29/how-libraries-can-learn-from-twitter/</link>
	<description>Linking my thinking with computer technology</description>
	<lastBuildDate>Tue, 29 Jun 2010 12:33:31 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Mal Booth</title>
		<link>http://www.paulhagon.com/blog/2009/05/29/how-libraries-can-learn-from-twitter/comment-page-1/#comment-715</link>
		<dc:creator>Mal Booth</dc:creator>
		<pubDate>Fri, 29 May 2009 04:54:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.paulhagon.com/?p=240#comment-715</guid>
		<description>Hahahahaha! Loved that last statement of yours.</description>
		<content:encoded><![CDATA[<p>Hahahahaha! Loved that last statement of yours.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Hagon</title>
		<link>http://www.paulhagon.com/blog/2009/05/29/how-libraries-can-learn-from-twitter/comment-page-1/#comment-714</link>
		<dc:creator>Paul Hagon</dc:creator>
		<pubDate>Fri, 29 May 2009 04:44:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.paulhagon.com/?p=240#comment-714</guid>
		<description>Definitely. Control is seen as power. Control is an outdated concept. Control is now fear.</description>
		<content:encoded><![CDATA[<p>Definitely. Control is seen as power. Control is an outdated concept. Control is now fear.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mal Booth</title>
		<link>http://www.paulhagon.com/blog/2009/05/29/how-libraries-can-learn-from-twitter/comment-page-1/#comment-713</link>
		<dc:creator>Mal Booth</dc:creator>
		<pubDate>Fri, 29 May 2009 04:27:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.paulhagon.com/?p=240#comment-713</guid>
		<description>Thanks Paulie, this is just in time for me. And one difference is that this year I first saw anything about your post on Twitter. Last year it would have been Google Reader and the year before word of mouth I suppose, maybe on a Monday night?
I agree that libraries have a lot to learn from both Twitter and Flickr - even the basic web interfaces they offer - and the growing number of APIs we are now seeing, particularly to do with Twitter. The APIs provide personalised, tailored, bespoke add-ons and changes that people want. Nobody is really controlling much of that, but libraries don&#039;t really like operating in a space that isn&#039;t controlled. So maybe in that way we are a bit like what Rev Dan Catt said about Flickr: you can get more stuff done working outside the library (assuming the data is open!) than inside it?</description>
		<content:encoded><![CDATA[<p>Thanks Paulie, this is just in time for me. And one difference is that this year I first saw anything about your post on Twitter. Last year it would have been Google Reader and the year before word of mouth I suppose, maybe on a Monday night?<br />
I agree that libraries have a lot to learn from both Twitter and Flickr &#8211; even the basic web interfaces they offer &#8211; and the growing number of APIs we are now seeing, particularly to do with Twitter. The APIs provide personalised, tailored, bespoke add-ons and changes that people want. Nobody is really controlling much of that, but libraries don&#8217;t really like operating in a space that isn&#8217;t controlled. So maybe in that way we are a bit like what Rev Dan Catt said about Flickr: you can get more stuff done working outside the library (assuming the data is open!) than inside it?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
