<?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: Army Retreats on Milblogging</title>
	<atom:link href="http://www.outsidethebeltway.com/archives/army_retreats_on_milblogging_/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.outsidethebeltway.com/archives/army_retreats_on_milblogging_/</link>
	<description>Online Journal of Politics and Foreign Affairs</description>
	<lastBuildDate>Thu, 26 Nov 2009 03:22:53 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: legion</title>
		<link>http://www.outsidethebeltway.com/archives/army_retreats_on_milblogging_/comment-page-1/#comment-123537</link>
		<dc:creator>legion</dc:creator>
		<pubDate>Fri, 04 May 2007 05:14:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.outsidethebeltway.com/archives/2007/05/army_retreats_on_milblogging_/#comment-123537</guid>
		<description>Wayne,
At face value, you&#039;re quite correct. But it&#039;s the Army&#039;s constant shifting of answers, backtracking, and equivocating that forces the listener to consider strongly that they&#039;re being hornswoggled.</description>
		<content:encoded><![CDATA[<p>Wayne,<br />
At face value, you're quite correct. But it's the Army's constant shifting of answers, backtracking, and equivocating that forces the listener to consider strongly that they're being hornswoggled.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wayne</title>
		<link>http://www.outsidethebeltway.com/archives/army_retreats_on_milblogging_/comment-page-1/#comment-123499</link>
		<dc:creator>Wayne</dc:creator>
		<pubDate>Thu, 03 May 2007 23:02:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.outsidethebeltway.com/archives/2007/05/army_retreats_on_milblogging_/#comment-123499</guid>
		<description>It cracks me up how many people automatically assume that anything the military does is for sinister purposes.  There is a caution in the military for anything their members’ say. The presses will taken any little discontent or miss up and blow it way out of proportion or take a piece out of context and misuse it. 

The OPSEC concerns of blogs, e-mail, mail and any other communication are very real. A private letter if it contains material that can compromises security can cause a military member to be court martial.  Does the military stop personal letters? Sometimes. However, for the sake of moral they allow it most of the time.  There is a trade off that must be managed. The Army spends a great deal of time and effort informing their members of what is appropriate and what is not. If a member has a question about it, they are advised to seek guidance since they are held liable for their communications. We don’t need to send a good soldier to jail for lack of poor judgment in communication. 

The military tends to be secretive in nature and its members who spend much time in sensitive areas tend to be secretive in nature. It is or could be a tough deal to live with the fact that a stupid comment ended up getting someone killed.</description>
		<content:encoded><![CDATA[<p>It cracks me up how many people automatically assume that anything the military does is for sinister purposes.  There is a caution in the military for anything their members&rsquo; say. The presses will taken any little discontent or miss up and blow it way out of proportion or take a piece out of context and misuse it. </p>
<p>The OPSEC concerns of blogs, e-mail, mail and any other communication are very real. A private letter if it contains material that can compromises security can cause a military member to be court martial.  Does the military stop personal letters? Sometimes. However, for the sake of moral they allow it most of the time.  There is a trade off that must be managed. The Army spends a great deal of time and effort informing their members of what is appropriate and what is not. If a member has a question about it, they are advised to seek guidance since they are held liable for their communications. We don&rsquo;t need to send a good soldier to jail for lack of poor judgment in communication. </p>
<p>The military tends to be secretive in nature and its members who spend much time in sensitive areas tend to be secretive in nature. It is or could be a tough deal to live with the fact that a stupid comment ended up getting someone killed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Joyner</title>
		<link>http://www.outsidethebeltway.com/archives/army_retreats_on_milblogging_/comment-page-1/#comment-123485</link>
		<dc:creator>James Joyner</dc:creator>
		<pubDate>Thu, 03 May 2007 21:44:26 +0000</pubDate>
		<guid isPermaLink="false">http://www.outsidethebeltway.com/archives/2007/05/army_retreats_on_milblogging_/#comment-123485</guid>
		<description>&lt;em&gt;The Army can spin it how it likes now that they&#039;re taking flak, but the intent was to quielty kill off independent milblogging &amp; co-opt the remainder as just another piece of propaganda.&lt;/em&gt;

That&#039;s my hunch as well.  That&#039;s why I use the verb &quot;claim&quot; rather than &quot;says&quot; or some variant.  

Incidentally, that&#039;s why I hate when supposedly objective press reports use the word &quot;claim,&quot; because it gives the impression (to me at least) that they&#039;re calling the person a liar.</description>
		<content:encoded><![CDATA[<p><em>The Army can spin it how it likes now that they're taking flak, but the intent was to quielty kill off independent milblogging &#038; co-opt the remainder as just another piece of propaganda.</em></p>
<p>That's my hunch as well.  That's why I use the verb "claim" rather than "says" or some variant.  </p>
<p>Incidentally, that's why I hate when supposedly objective press reports use the word "claim," because it gives the impression (to me at least) that they're calling the person a liar.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: legion</title>
		<link>http://www.outsidethebeltway.com/archives/army_retreats_on_milblogging_/comment-page-1/#comment-123484</link>
		<dc:creator>legion</dc:creator>
		<pubDate>Thu, 03 May 2007 21:36:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.outsidethebeltway.com/archives/2007/05/army_retreats_on_milblogging_/#comment-123484</guid>
		<description>I call shenanigans. From the &lt;a href=&quot;http://blog.wired.com/defense/2007/05/the_army_has_is.html#more&quot; rel=&quot;nofollow&quot;&gt;Danger Room&lt;/a&gt; blog, interviewing the Major who _wrote_ the new reg, 
&lt;blockquote&gt;Q: If a soldier has to consult his supervisor or an OPSEC officer every time he wants e-mail home or put up a blog posting, doesn&#039;t that effectively kill the practice?  What supervisor is going to have the time to check all of that material?  

The regulation says that a Soldier or other U.S. Army personnel must consult with their immediate supervisor and OPSEC officer prior to posting information in a public forum.  However, this is where unit commander or organization leadership specifies in orders, policies, or directives how this will be done.  Some units may require that Soldiers register their blog with the unit for identification purposes with occasional spot checks after an initial review.  &lt;strong&gt;Other units may require a review before every posting.&lt;/strong&gt;  A private e-mail message to Family Members is not considered posting information in a public forum, but U.S. Army personnel are informed that unclassified e-mails can be intercepted and that they shouldn’t write anything that they wouldn’t say on an unsecure phone. While it is not practical to check all communication, especially private communication, the U.S. Army trusts that Soldiers and U.S. Army personnel will do the right things to maintain proper security when they understand their role in it. &lt;/blockquote&gt; (Emphasis mine)

Say what you want about how commanders can _choose_ to implement it, the actual wording of the reg is fairly straightforward; see para 2-1g:
&lt;blockquote&gt;Consult with &lt;strong&gt;their immediate supervisor and their OPSEC Officer&lt;/strong&gt; for an OPSEC review prior to publishing or posting information in a public forum.

(1) This includes, but is not limited to letters, resumes, articles for publication, &lt;strong&gt;electronic mail (e-mail), Web site postings, web log (blog) postings&lt;/strong&gt;, discussion in Internet information forums, discussion in Internet message boards or other forms of dissemination or documentation.&lt;/blockquote&gt;
Yeah, individual commanders have some wiggle room to interpret that, but that means every commander at every level could have a different policy. That won&#039;t happen. Some general somewhere will make his own policy standard for the entire theater.
&lt;blockquote&gt;Indeed, they claim no real change was ever in the offing&lt;/blockquote&gt;Bullshit. The Army can spin it how it likes now that they&#039;re taking flak, but the intent was to quielty kill off independent milblogging &amp; co-opt the remainder as just another piece of propaganda.</description>
		<content:encoded><![CDATA[<p>I call shenanigans. From the <a href="http://blog.wired.com/defense/2007/05/the_army_has_is.html#more" rel="nofollow">Danger Room</a> blog, interviewing the Major who _wrote_ the new reg, </p>
<blockquote><p>Q: If a soldier has to consult his supervisor or an OPSEC officer every time he wants e-mail home or put up a blog posting, doesn't that effectively kill the practice?  What supervisor is going to have the time to check all of that material?  </p>
<p>The regulation says that a Soldier or other U.S. Army personnel must consult with their immediate supervisor and OPSEC officer prior to posting information in a public forum.  However, this is where unit commander or organization leadership specifies in orders, policies, or directives how this will be done.  Some units may require that Soldiers register their blog with the unit for identification purposes with occasional spot checks after an initial review.  <strong>Other units may require a review before every posting.</strong>  A private e-mail message to Family Members is not considered posting information in a public forum, but U.S. Army personnel are informed that unclassified e-mails can be intercepted and that they shouldn&rsquo;t write anything that they wouldn&rsquo;t say on an unsecure phone. While it is not practical to check all communication, especially private communication, the U.S. Army trusts that Soldiers and U.S. Army personnel will do the right things to maintain proper security when they understand their role in it. </p></blockquote>
<p> (Emphasis mine)</p>
<p>Say what you want about how commanders can _choose_ to implement it, the actual wording of the reg is fairly straightforward; see para 2-1g:</p>
<blockquote><p>Consult with <strong>their immediate supervisor and their OPSEC Officer</strong> for an OPSEC review prior to publishing or posting information in a public forum.</p>
<p>(1) This includes, but is not limited to letters, resumes, articles for publication, <strong>electronic mail (e-mail), Web site postings, web log (blog) postings</strong>, discussion in Internet information forums, discussion in Internet message boards or other forms of dissemination or documentation.</p></blockquote>
<p>Yeah, individual commanders have some wiggle room to interpret that, but that means every commander at every level could have a different policy. That won't happen. Some general somewhere will make his own policy standard for the entire theater.</p>
<blockquote><p>Indeed, they claim no real change was ever in the offing</p></blockquote>
<p>Bullshit. The Army can spin it how it likes now that they're taking flak, but the intent was to quielty kill off independent milblogging &amp; co-opt the remainder as just another piece of propaganda.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
