<?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: Citizens Against Government Waste: porkerofthemonth</title>
	<atom:link href="http://enfranchisedmind.com/blog/2006/02/27/citizens-against-government-waste-porkerofthemonth/feed/" rel="self" type="application/rss+xml" />
	<link>http://enfranchisedmind.com/blog/2006/02/27/citizens-against-government-waste-porkerofthemonth/</link>
	<description>Robert Fischer and Brian Hurt on Punditry, Programming Languages, and Other Religious Issues</description>
	<pubDate>Wed, 07 Jan 2009 07:37:29 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: TheHawk</title>
		<link>http://enfranchisedmind.com/blog/2006/02/27/citizens-against-government-waste-porkerofthemonth/comment-page-1/#comment-226</link>
		<dc:creator>TheHawk</dc:creator>
		<pubDate>Wed, 01 Mar 2006 22:56:09 +0000</pubDate>
		<guid isPermaLink="false">http://enfranchisedmind.com/blog/archive/2006/02/27/110#comment-226</guid>
		<description>First off, you're two first complaints are both valid and irrelevant. Of course we need to make sure the system is implemented in such a way as to make it both secure and accurate. Any system which is badly implemented is bad, regardless. If a system can't be done well, it shouldn't be done at all.

That being said, I never said this was the solution, or even a solution. All I said was it might have some merit. I realize that there are a number of problems with the implementation and there are certainly a number of other security holes which need to be addressed as well. But that doesn't mean the entire thing is bad, only that if it is to go forward, it must be done carefully and with the direct input of people in the relevant fields who know what they are talking about. And even if it is to go forward, that certainly doesn't mean we should not take steps to address the other security holes.</description>
		<content:encoded><![CDATA[<p>First off, you&#8217;re two first complaints are both valid and irrelevant. Of course we need to make sure the system is implemented in such a way as to make it both secure and accurate. Any system which is badly implemented is bad, regardless. If a system can&#8217;t be done well, it shouldn&#8217;t be done at all.</p>
<p>That being said, I never said this was the solution, or even a solution. All I said was it might have some merit. I realize that there are a number of problems with the implementation and there are certainly a number of other security holes which need to be addressed as well. But that doesn&#8217;t mean the entire thing is bad, only that if it is to go forward, it must be done carefully and with the direct input of people in the relevant fields who know what they are talking about. And even if it is to go forward, that certainly doesn&#8217;t mean we should not take steps to address the other security holes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Candide</title>
		<link>http://enfranchisedmind.com/blog/2006/02/27/citizens-against-government-waste-porkerofthemonth/comment-page-1/#comment-225</link>
		<dc:creator>Candide</dc:creator>
		<pubDate>Wed, 01 Mar 2006 20:12:31 +0000</pubDate>
		<guid isPermaLink="false">http://enfranchisedmind.com/blog/archive/2006/02/27/110#comment-225</guid>
		<description>You're assuming then, that the database would be kept accurate enough to credibly discount someone's entry (or re-entry) into the United States?  And that it would be more secure than the anti-forgery capabilities of the US Passport?  And the expensive database system still wouldn't protect against bribed customs officials, which (AFAIK) is the easiest way to circumvent the border security.

Yes, a good messaging system communicating which passports are bad, and the ability to have them uniquely identified, is a good thing.  We have that already, though, in email.  PGP encrypt it and now it's a secure(r) system.

The problem which I have with both your statement and this whole movement of RFID is the assumption that somehow an expensive, complicated application of technology is the solution to these national security problems.  We have the technology -- the major holes in the system are much simpler.</description>
		<content:encoded><![CDATA[<p>You&#8217;re assuming then, that the database would be kept accurate enough to credibly discount someone&#8217;s entry (or re-entry) into the United States?  And that it would be more secure than the anti-forgery capabilities of the US Passport?  And the expensive database system still wouldn&#8217;t protect against bribed customs officials, which (AFAIK) is the easiest way to circumvent the border security.</p>
<p>Yes, a good messaging system communicating which passports are bad, and the ability to have them uniquely identified, is a good thing.  We have that already, though, in email.  PGP encrypt it and now it&#8217;s a secure(r) system.</p>
<p>The problem which I have with both your statement and this whole movement of RFID is the assumption that somehow an expensive, complicated application of technology is the solution to these national security problems.  We have the technology &#8212; the major holes in the system are much simpler.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TheHawk</title>
		<link>http://enfranchisedmind.com/blog/2006/02/27/citizens-against-government-waste-porkerofthemonth/comment-page-1/#comment-224</link>
		<dc:creator>TheHawk</dc:creator>
		<pubDate>Wed, 01 Mar 2006 07:27:38 +0000</pubDate>
		<guid isPermaLink="false">http://enfranchisedmind.com/blog/archive/2006/02/27/110#comment-224</guid>
		<description>I never said we had to, I said there probably were some merits to it. Having a digital database backing the passport could help prevent forgery. Print a scannable barcode or magnetic strip on the passports which the agents could scan and would display a digital copy of the passport information. That way they can check the physical copy against the digital for any alterations. If you don't mind irritating the privacy people, it allows for effective monitoring of people leaving and entering the U.S. I'll admit thats likely to be a touchy area and the uses of any such information can certainly be carefully discussed, but having the technollogy for it isn't that bad. Along the same lines as the first, it enables the quick, effective dissemination of information such as warrants or other legal rulings which would interfere with a citizen's right to cross the border. Not dealing in any way with law enforcement or immigration thats all I can come up with of the top of my head, but there may be others. Of course each of these or other reasons must be weighed against the cost and effectiveness of any implementation.</description>
		<content:encoded><![CDATA[<p>I never said we had to, I said there probably were some merits to it. Having a digital database backing the passport could help prevent forgery. Print a scannable barcode or magnetic strip on the passports which the agents could scan and would display a digital copy of the passport information. That way they can check the physical copy against the digital for any alterations. If you don&#8217;t mind irritating the privacy people, it allows for effective monitoring of people leaving and entering the U.S. I&#8217;ll admit thats likely to be a touchy area and the uses of any such information can certainly be carefully discussed, but having the technollogy for it isn&#8217;t that bad. Along the same lines as the first, it enables the quick, effective dissemination of information such as warrants or other legal rulings which would interfere with a citizen&#8217;s right to cross the border. Not dealing in any way with law enforcement or immigration thats all I can come up with of the top of my head, but there may be others. Of course each of these or other reasons must be weighed against the cost and effectiveness of any implementation.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
