<?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 for @FindThomas</title>
	<atom:link href="http://www.findthomas.net/blog/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.findthomas.net/blog</link>
	<description>Digital Identity, Trust and Privacy on the open Internet</description>
	<lastBuildDate>Sun, 30 Dec 2012 06:25:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>Comment on Limitations of the OAuth 2.0 definition of &#8220;Client&#8221; by Re: Limitations of the OAuth 2.0 definition of “Client” : =nat</title>
		<link>http://www.findthomas.net/blog/2012/12/29/limitations-of-the-oauth-2-0-definition-of-client/#comment-266</link>
		<dc:creator>Re: Limitations of the OAuth 2.0 definition of “Client” : =nat</dc:creator>
		<pubDate>Sun, 30 Dec 2012 06:25:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.findthomas.net/blog/?p=178#comment-266</guid>
		<description><![CDATA[[...] Re: Limitations of the OAuth 2.0 definition of “Client”  December 30th, 2012OAuth0 Comments   Thomas Hardjono has a very good blog entry &lt;&lt;Limitations of the OAuth 2.0 definition of &#8220;Client&#8221;&gt;&gt;. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Re: Limitations of the OAuth 2.0 definition of “Client”  December 30th, 2012OAuth0 Comments   Thomas Hardjono has a very good blog entry &lt;&lt;Limitations of the OAuth 2.0 definition of &#8220;Client&#8221;&gt;&gt;. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A market for leakage in derived identities by Thomas Hardjono</title>
		<link>http://www.findthomas.net/blog/2012/03/09/a-market-for-leakage-in-derived-identities/#comment-3</link>
		<dc:creator>Thomas Hardjono</dc:creator>
		<pubDate>Mon, 12 Mar 2012 14:41:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.findthomas.net/blog/?p=5#comment-3</guid>
		<description><![CDATA[Hi kevin,

Rather than trying to &quot;scrape-off&quot; information (from the Internet), perhaps more $$ can be made by eco-system players through supporting efforts to maintain the privacy of consumers.  After all, if my credit-card information was &quot;lost&quot; or &quot;stolen&quot; by shop (online or brick-mortar), I would not go back to do business with them again.]]></description>
		<content:encoded><![CDATA[<p>Hi kevin,</p>
<p>Rather than trying to &#8220;scrape-off&#8221; information (from the Internet), perhaps more $$ can be made by eco-system players through supporting efforts to maintain the privacy of consumers.  After all, if my credit-card information was &#8220;lost&#8221; or &#8220;stolen&#8221; by shop (online or brick-mortar), I would not go back to do business with them again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on A market for leakage in derived identities by Kevin Cox</title>
		<link>http://www.findthomas.net/blog/2012/03/09/a-market-for-leakage-in-derived-identities/#comment-2</link>
		<dc:creator>Kevin Cox</dc:creator>
		<pubDate>Sun, 11 Mar 2012 07:46:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.findthomas.net/blog/?p=5#comment-2</guid>
		<description><![CDATA[The market in leaked identities is large and the players - particularly those interested in surveillance - has powerful sponsors.

User managed access can help address the problem because it lets us know when our information is released.  However we need to make sure our information is not leaked beyond the originating sources. If every organisation was required to use a unique identifier for each individual and if every individual was permitted to access their own information held by the organisation then it reduces the ability for leaked identities to survive. This is because we, as individuals, can check to see where our information is held.]]></description>
		<content:encoded><![CDATA[<p>The market in leaked identities is large and the players &#8211; particularly those interested in surveillance &#8211; has powerful sponsors.</p>
<p>User managed access can help address the problem because it lets us know when our information is released.  However we need to make sure our information is not leaked beyond the originating sources. If every organisation was required to use a unique identifier for each individual and if every individual was permitted to access their own information held by the organisation then it reduces the ability for leaked identities to survive. This is because we, as individuals, can check to see where our information is held.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
