<?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: The Most Dangerous Social Media Tool Ever?</title>
	<atom:link href="http://socialmediarisk.com/2010/03/the-most-dangerous-social-media-tool-ever/feed/" rel="self" type="application/rss+xml" />
	<link>http://socialmediarisk.com/2010/03/the-most-dangerous-social-media-tool-ever/</link>
	<description>Exploring the risks of engaging in social media</description>
	<lastBuildDate>Wed, 17 Mar 2010 20:16:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: taulbee</title>
		<link>http://socialmediarisk.com/2010/03/the-most-dangerous-social-media-tool-ever/#comment-14</link>
		<dc:creator>taulbee</dc:creator>
		<pubDate>Thu, 11 Mar 2010 20:26:16 +0000</pubDate>
		<guid isPermaLink="false">http://socialmediarisk.com/?p=30#comment-14</guid>
		<description>Thanks Katie - awesome technology, look forward to using the desktop app!

Taulbee</description>
		<content:encoded><![CDATA[<p>Thanks Katie &#8211; awesome technology, look forward to using the desktop app!</p>
<p>Taulbee</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Katie Morse</title>
		<link>http://socialmediarisk.com/2010/03/the-most-dangerous-social-media-tool-ever/#comment-13</link>
		<dc:creator>Katie Morse</dc:creator>
		<pubDate>Thu, 11 Mar 2010 20:21:23 +0000</pubDate>
		<guid isPermaLink="false">http://socialmediarisk.com/?p=30#comment-13</guid>
		<description>Hi from Radian6 and thanks for sharing your thoughts!  My background includes working for companies that are both active and completely oblivious of the social space, and I couldn&#039;t agree more with the points you make about having a team who is educated in place before jumping in head first.  That being said, that goes with social media as a whole, not just our new Engagement Console.  Keep in mind that staff can be given or denied access to the Engagement Console (once publicly released) just as they would for any other piece of technology.

&quot;Just keep in mind where you point that thing.&quot; I kind of love that closing line.  

Cheers again and let us know if you have questions as our rollout begins!

Katie Morse
@misskatiemo &#124; Radian6</description>
		<content:encoded><![CDATA[<p>Hi from Radian6 and thanks for sharing your thoughts!  My background includes working for companies that are both active and completely oblivious of the social space, and I couldn&#8217;t agree more with the points you make about having a team who is educated in place before jumping in head first.  That being said, that goes with social media as a whole, not just our new Engagement Console.  Keep in mind that staff can be given or denied access to the Engagement Console (once publicly released) just as they would for any other piece of technology.</p>
<p>&#8220;Just keep in mind where you point that thing.&#8221; I kind of love that closing line.  </p>
<p>Cheers again and let us know if you have questions as our rollout begins!</p>
<p>Katie Morse<br />
@misskatiemo | Radian6</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced
Database Caching 4/4 queries in 0.002 seconds using disk: basic
Object Caching 489/489 objects using disk: basic

Served from: socialmediarisk.com @ 2012-05-19 08:00:24 -->
