<?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: Will Buzz change the social media landscape</title>
	<atom:link href="http://www.museummarketing.co.uk/2010/02/14/will-buzz-change-the-social-media-landscape/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.museummarketing.co.uk/2010/02/14/will-buzz-change-the-social-media-landscape/</link>
	<description></description>
	<lastBuildDate>Fri, 03 Sep 2010 09:20:34 +0100</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Martin</title>
		<link>http://www.museummarketing.co.uk/2010/02/14/will-buzz-change-the-social-media-landscape/comment-page-1/#comment-2715</link>
		<dc:creator>Martin</dc:creator>
		<pubDate>Sun, 14 Feb 2010 21:54:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.museummarketing.co.uk/?p=759#comment-2715</guid>
		<description>Buzz is only new, yet there&#039;s already a backlash against it, most often dealing with the privacy issues, the fact that it&#039;s opt-out, not opt in (with further privacy implications), and also that it produces a huge stream of updates if you&#039;re connected to a number of people.
It&#039;s great that museums are ready to take advantage of new social networks, rather than being behind the curve, but a good rule of thumb is to decide how you will engage with your audience, and then choose the tool which fits the bill.
As museums are often strapped for resources, I think they should wait for Buzz to bed in a bit, and judge the mood before taking the plunge into &#039;another&#039; social network.</description>
		<content:encoded><![CDATA[<p>Buzz is only new, yet there&#8217;s already a backlash against it, most often dealing with the privacy issues, the fact that it&#8217;s opt-out, not opt in (with further privacy implications), and also that it produces a huge stream of updates if you&#8217;re connected to a number of people.<br />
It&#8217;s great that museums are ready to take advantage of new social networks, rather than being behind the curve, but a good rule of thumb is to decide how you will engage with your audience, and then choose the tool which fits the bill.<br />
As museums are often strapped for resources, I think they should wait for Buzz to bed in a bit, and judge the mood before taking the plunge into &#8216;another&#8217; social network.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shona Carnall</title>
		<link>http://www.museummarketing.co.uk/2010/02/14/will-buzz-change-the-social-media-landscape/comment-page-1/#comment-2714</link>
		<dc:creator>Shona Carnall</dc:creator>
		<pubDate>Sun, 14 Feb 2010 21:28:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.museummarketing.co.uk/?p=759#comment-2714</guid>
		<description>I think I may wait until there is more activity on Buzz before I add the museum to it.  At the moment, there are still some issues with it (collapsable comments Google! We need them!), and I haven&#039;t really got my head round it yet.  Linking it with Twitter and Facebook is useful so I don&#039;t have yet another thing to check in the morning.  

It is nice to see some museums already embracing it and setting the trend! But I think I may wait and see how it develops.</description>
		<content:encoded><![CDATA[<p>I think I may wait until there is more activity on Buzz before I add the museum to it.  At the moment, there are still some issues with it (collapsable comments Google! We need them!), and I haven&#8217;t really got my head round it yet.  Linking it with Twitter and Facebook is useful so I don&#8217;t have yet another thing to check in the morning.  </p>
<p>It is nice to see some museums already embracing it and setting the trend! But I think I may wait and see how it develops.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
