<?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>Copac Developments &#187; twitter</title>
	<atom:link href="http://copac.ac.uk/development-blog/tag/twitter/feed/" rel="self" type="application/rss+xml" />
	<link>http://copac.ac.uk/development-blog</link>
	<description>What's happening behind the scenes at Copac</description>
	<lastBuildDate>Wed, 23 Nov 2011 15:28:59 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
		<item>
		<title>Copac is twittering:  the where and the why</title>
		<link>http://copac.ac.uk/development-blog/2009/02/copac-is-twittering-the-where-and-the-why/</link>
		<comments>http://copac.ac.uk/development-blog/2009/02/copac-is-twittering-the-where-and-the-why/#comments</comments>
		<pubDate>Mon, 16 Feb 2009 16:40:39 +0000</pubDate>
		<dc:creator>bethan</dc:creator>
				<category><![CDATA[Communication]]></category>
		<category><![CDATA[library 2.0]]></category>
		<category><![CDATA[twitter]]></category>
		<category><![CDATA[web 2.0]]></category>

		<guid isPermaLink="false">http://copac.ac.uk/development-blog/?p=175</guid>
		<description><![CDATA[Many of you will know that Copac now has a presence on Twitter.Â  Some of you may have come to this blog from our Twitter feed.Â  Many of you, Iâ€™m sure, will be devout Twitterers, tweeting away with your pithy and insightful comments.Â  Others will be shaking their head and saying â€˜Eh now? Tweeting? Is [...]]]></description>
			<content:encoded><![CDATA[<p>Many of you will know that Copac now has a presence on <a title="Twitter homepage" href="https://twitter.com/home">Twitter</a>.Â   Some of you may have come to this blog from   <a title="Copac's Twitter page" href="https://twitter.com/Copac">our Twitter feed</a>.Â  Many of you, Iâ€™m sure, will be devout Twitterers, tweeting away with your pithy and   insightful comments.Â  Others will be shaking their head and saying â€˜Eh now?  Tweeting?  Is the latest   interweb craze to pretend youâ€™re a bird?!?â€™  [note:  stereotype used for comedy purposes only, and guaranteed   to bear no actual resemblance to any of our readers.]</p>
<p>Twitter is a microblogging service, where users answer the question â€œWhat are you doing?â€ in 140 characters   or less.  Thanks to prominent Twitterers such as <a title="Barack Obama's Twitter page" href="http://twitter.com/BarackObama">Barack Obama</a>, <a title="Stephen Fry's Twitter page" href="http://twitter.com/stephenfry">Stephen Fry</a>, and â€¦ ummâ€¦ <a title="Darth Vader's Twitter page" href="http://twitter.com/darthvader">Darth Vader</a>, Twitter has recently   gained enormous media coverage.  Obama used it for campaigning.  Stephen Fry live-tweeted being stuck in a   lift.  Darth Vader does Thriller.</p>
<p>Itâ€™s fairly obvious that thereâ€™s a large amount of the wild and wacky on Twitter â€“ as well as a fair amount   of the frankly banal.  Updates about meals/gym regimes/bedtimes may be scintillating stuff for your close   circle of friends, but unless you have a particularly effulgent turn of phrase â€“ or a dangerously exciting   lifestyle â€“ they arenâ€™t going to thrill the twitosphere.</p>
<p>Weâ€™re all guilty of it.  A look at <a title="Bethanar's Twitter page" href="http://twitter.com/bethanar">my personal tweets</a> will â€¦ well, you looked.    However, itâ€™s a bit different when youâ€™re not tweeting for yourself.  Tweeting on behalf of Copac means that   I have a whole different audience, a different set of priorities.  What will Copac users find interesting?    What will they ignore with a yawn?  And Iâ€™m finding it surprisingly difficult to do in that format.</p>
<p>The tweet, the microblog, is â€“ like the Facebook status â€“ an informal medium.   Itâ€™s hard to be otherwise in   140 characters.  Trying to be formal results in very stilted tweets, where the occasional   (space-necessitated) contraction and web-speak glares and jars.  If youâ€™ve got this far, youâ€™ve probably   realised that formal isnâ€™t really my style.  And yet the point of the Copac Twitter account is toâ€¦ is toâ€¦</p>
<p>Ah.  I think weâ€™ve found the root of my style problem.  What is the point of the Copac Twitter account?    Surely weâ€™re not just doing it to be fashionably web 2.0.  Are we doing it to inform people of Copac news?    Yes, but we already have a <a title="Copac News Blog" href="http://copac.ac.uk/blog/blog.html">news blog</a> for that.  Are we doing it to   promote Copac developments?  Yes, but we already have a <a title="Copac Development Blog homepage" href="http://copac.ac.uk/development-blog/">development blog</a> for that.  Are we doing it to   connect with our users and our peers?  To get closer to the Copac community?  Yes!</p>
<p>So there we are.  Weâ€™ve found our audience.  Now can you help us find our voice?  What do you want Copac to   tweet about?  How do you want us to speak to you?  Please let us know!  You can contact us through the   comments here, at the <a title="Copac News Blog" href="http://copac.ac.uk/blog/">news blog</a>, on our <a title="Copac's Twitter page" href="https://twitter.com/Copac">Twitter account</a>, on our <a title="Copac's Facebook page" href="http://www.facebook.com/apps/application.php?id=2464321389,">Facebook page</a>,Â  by <a title="copac@mimas.ac.uk" href="mailto:copac@mimas.ac.uk">email</a>, or <a title="How to contact Copac" href="http://copac.ac.uk/contact/">phone</a>.  Or shine   the Copac symbol from the top of a tall building on a dark and stormy night, and await the caped librariansâ€¦</p>
]]></content:encoded>
			<wfw:commentRss>http://copac.ac.uk/development-blog/2009/02/copac-is-twittering-the-where-and-the-why/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

