<?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: Social Media Use: For the U.S. Air Force it’s a Benefit, not a Threat</title>
	<atom:link href="http://www.jplcreative.com/blog/index.php/2010/07/06/social-media-use-by-employees-for-the-u-s-air-force-its-a-benefit-not-a-threat/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jplcreative.com/blog/index.php/2010/07/06/social-media-use-by-employees-for-the-u-s-air-force-its-a-benefit-not-a-threat/</link>
	<description>Blog - Strategic Communications &#38; Digital Marketing</description>
	<lastBuildDate>Fri, 04 May 2012 17:32:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: John Walker</title>
		<link>http://www.jplcreative.com/blog/index.php/2010/07/06/social-media-use-by-employees-for-the-u-s-air-force-its-a-benefit-not-a-threat/comment-page-1/#comment-1400</link>
		<dc:creator>John Walker</dc:creator>
		<pubDate>Thu, 08 Jul 2010 14:24:38 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jplcreative.com/?p=592#comment-1400</guid>
		<description>Paul,

Thanks for your comment. I have to say that I have been very  pleasantly surprised by how forward thinking the Air Force appears to be regarding social media. A colleague commented to me that if there is any organization that would have a strong argument for locking down communications by its staff, it would be the Air Force. However, you have taken the opposite approach. Very interesting.
John</description>
		<content:encoded><![CDATA[<p>Paul,</p>
<p>Thanks for your comment. I have to say that I have been very  pleasantly surprised by how forward thinking the Air Force appears to be regarding social media. A colleague commented to me that if there is any organization that would have a strong argument for locking down communications by its staff, it would be the Air Force. However, you have taken the opposite approach. Very interesting.<br />
John</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Bove</title>
		<link>http://www.jplcreative.com/blog/index.php/2010/07/06/social-media-use-by-employees-for-the-u-s-air-force-its-a-benefit-not-a-threat/comment-page-1/#comment-1376</link>
		<dc:creator>Paul Bove</dc:creator>
		<pubDate>Wed, 07 Jul 2010 13:51:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jplcreative.com/?p=592#comment-1376</guid>
		<description>John, thanks for recognizing the strides we&#039;ve made in embracing social media at the Air Force. It&#039;s been a challenge, especially since many of the websites were blocked from our computers until just a couple months ago. But as you mentioned, if we don&#039;t allow the Airmen to tell the story, somebody else will. Education is key to ensuring they do it safely. There is an updated version to the social media guide (just a few edits and updated stats) located here: http://www.af.mil/shared/media/document/AFD-091210-043.pdf.

Again, thanks.
Paul F. Bove, Social Media Strategist
Air Force Public Affairs Agency</description>
		<content:encoded><![CDATA[<p>John, thanks for recognizing the strides we&#8217;ve made in embracing social media at the Air Force. It&#8217;s been a challenge, especially since many of the websites were blocked from our computers until just a couple months ago. But as you mentioned, if we don&#8217;t allow the Airmen to tell the story, somebody else will. Education is key to ensuring they do it safely. There is an updated version to the social media guide (just a few edits and updated stats) located here: <a href="http://www.af.mil/shared/media/document/AFD-091210-043.pdf" rel="nofollow">http://www.af.mil/shared/media/document/AFD-091210-043.pdf</a>.</p>
<p>Again, thanks.<br />
Paul F. Bove, Social Media Strategist<br />
Air Force Public Affairs Agency</p>
]]></content:encoded>
	</item>
</channel>
</rss>

