<?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: Bush &#8220;No Torture&#8221; Statement &#8220;Clarified&#8221;</title>
	<atom:link href="http://donklephant.com/2005/11/14/bush-no-torture-statement-clarified/feed/" rel="self" type="application/rss+xml" />
	<link>http://donklephant.com/2005/11/14/bush-no-torture-statement-clarified/</link>
	<description>Big Teeth. Huge Ass. Surprisingly Reasonable.</description>
	<pubDate>Fri, 09 Jan 2009 12:33:21 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: DosPeros</title>
		<link>http://donklephant.com/2005/11/14/bush-no-torture-statement-clarified/comment-page-1/#comment-3760</link>
		<dc:creator>DosPeros</dc:creator>
		<pubDate>Mon, 14 Nov 2005 21:00:31 +0000</pubDate>
		<guid isPermaLink="false">http://donklephant.com/2005/11/14/bush-no-torture-statement-clarified/#comment-3760</guid>
		<description>"Either torture everybody or torture nobody. There is no inbetween."

I think there is an in-between torture policy (if we are going to have a torture policy), in fact an entire sliding-scale torture policy based on, for instance: 1) intelligence already known about the detainee and 2) the potential value of the information sought.  

I would hardly deem it appropriate to torture an Afgani farmer who might know where a weapon cache exists in order find those weapons.  

My torture position might soften if say: A known terrorists had particular information regarding a known terrorist threat that would kill millions of people.  

Torture is nuanced.  What is torture?  Who to torture?  How to torture, leading back to, What is torture?  When to torture?  Why to torture? Who should do the torturing? 

I can't speak to the success or failure of torture in intelligence gathering.  I once tried to torture my 3 year old by making her listen to Meet the Press until she finished her breakfast, instead of cartoons.  It was remarkably successful after an hour and further threats of the Mclaughlin Group.   

Maybe it's a waste of time, maybe it is useful...depending on the who, where, when, how and whys.  But one would think that a certain about behavioral science would suggest the possibility that torture could be useful.</description>
		<content:encoded><![CDATA[<p>&#8220;Either torture everybody or torture nobody. There is no inbetween.&#8221;</p>
<p>I think there is an in-between torture policy (if we are going to have a torture policy), in fact an entire sliding-scale torture policy based on, for instance: 1) intelligence already known about the detainee and 2) the potential value of the information sought.  </p>
<p>I would hardly deem it appropriate to torture an Afgani farmer who might know where a weapon cache exists in order find those weapons.  </p>
<p>My torture position might soften if say: A known terrorists had particular information regarding a known terrorist threat that would kill millions of people.  </p>
<p>Torture is nuanced.  What is torture?  Who to torture?  How to torture, leading back to, What is torture?  When to torture?  Why to torture? Who should do the torturing? </p>
<p>I can&#8217;t speak to the success or failure of torture in intelligence gathering.  I once tried to torture my 3 year old by making her listen to Meet the Press until she finished her breakfast, instead of cartoons.  It was remarkably successful after an hour and further threats of the Mclaughlin Group.   </p>
<p>Maybe it&#8217;s a waste of time, maybe it is useful&#8230;depending on the who, where, when, how and whys.  But one would think that a certain about behavioral science would suggest the possibility that torture could be useful.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.466 seconds -->
