<?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"
	>
<channel>
	<title>Comments on: Addressing an issue</title>
	<atom:link href="http://easytechtalk.com/2008/02/24/integrated-address-changing/feed/" rel="self" type="application/rss+xml" />
	<link>http://easytechtalk.com/2008/02/24/integrated-address-changing/</link>
	<description>Technology made simple</description>
	<pubDate>Tue, 07 Oct 2008 13:39:59 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Doug</title>
		<link>http://easytechtalk.com/2008/02/24/integrated-address-changing/#comment-1773</link>
		<dc:creator>Doug</dc:creator>
		<pubDate>Wed, 27 Feb 2008 05:19:02 +0000</pubDate>
		<guid isPermaLink="false">http://easytechtalk.com/2008/02/24/integrated-address-changing/#comment-1773</guid>
		<description>I realized as i hit publish that i said central database, i meant some sort of centralized way of changing addresses.  blasted itchy trigger finger.</description>
		<content:encoded><![CDATA[<p>I realized as i hit publish that i said central database, i meant some sort of centralized way of changing addresses.  blasted itchy trigger finger.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wayne Smallman</title>
		<link>http://easytechtalk.com/2008/02/24/integrated-address-changing/#comment-1757</link>
		<dc:creator>Wayne Smallman</dc:creator>
		<pubDate>Tue, 26 Feb 2008 22:23:28 +0000</pubDate>
		<guid isPermaLink="false">http://easytechtalk.com/2008/02/24/integrated-address-changing/#comment-1757</guid>
		<description>I agree with DCR. It's a nice idea, but there's just too much scope for abuse.

On balance, the inconvenience of updating your details is a price worth paying when the alternative is identity theft, or actual theft, say when you're on holiday...</description>
		<content:encoded><![CDATA[<p>I agree with DCR. It&#8217;s a nice idea, but there&#8217;s just too much scope for abuse.</p>
<p>On balance, the inconvenience of updating your details is a price worth paying when the alternative is identity theft, or actual theft, say when you&#8217;re on holiday&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dcr</title>
		<link>http://easytechtalk.com/2008/02/24/integrated-address-changing/#comment-1714</link>
		<dc:creator>dcr</dc:creator>
		<pubDate>Mon, 25 Feb 2008 23:09:21 +0000</pubDate>
		<guid isPermaLink="false">http://easytechtalk.com/2008/02/24/integrated-address-changing/#comment-1714</guid>
		<description>A centralized database would also be ripe for abuse.  Imagine the havoc that could be caused were hackers to break into it!

I would rather that fewer companies have access to my personal information than more.

What could be useful is a standard for updating addresses.  You could store the companies you deal with in your own personal database, and then, if you move, click a button and the database software would send each company a message (in that standard format) that your address has changed.

That way, no centralized database is in use that could be ripe for hackers to try to break into.  And the individual would have control over who receives the address change notification.</description>
		<content:encoded><![CDATA[<p>A centralized database would also be ripe for abuse.  Imagine the havoc that could be caused were hackers to break into it!</p>
<p>I would rather that fewer companies have access to my personal information than more.</p>
<p>What could be useful is a standard for updating addresses.  You could store the companies you deal with in your own personal database, and then, if you move, click a button and the database software would send each company a message (in that standard format) that your address has changed.</p>
<p>That way, no centralized database is in use that could be ripe for hackers to try to break into.  And the individual would have control over who receives the address change notification.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
