<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Identity, relationships and why OAuth and OpenID matter</title>
	<atom:link href="http://derivadow.com/2009/01/08/identity-relationships-and-why-oauth-and-openid-matter/feed/" rel="self" type="application/rss+xml" />
	<link>http://derivadow.com/2009/01/08/identity-relationships-and-why-oauth-and-openid-matter/</link>
	<description>...is a blog by Tom Scott a place where I ramble about my thoughts and observations on the open web, linked data, URIs and generally how technology and design can create great things for people to use.</description>
	<lastBuildDate>Mon, 06 Feb 2012 21:20:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Tom Scott</title>
		<link>http://derivadow.com/2009/01/08/identity-relationships-and-why-oauth-and-openid-matter/#comment-2410</link>
		<dc:creator><![CDATA[Tom Scott]]></dc:creator>
		<pubDate>Thu, 08 Jan 2009 21:53:55 +0000</pubDate>
		<guid isPermaLink="false">http://derivadow.com/?p=849#comment-2410</guid>
		<description><![CDATA[Chris, the relationship type stuff came from here: http://itc.conversationsnetwork.org/shows/detail3829.html but it was in fact Bob Blakley not Jamie.

And yes completely agree with your points - my bad - I have confused the situation somewhat by messing up the history. Sorry folks.]]></description>
		<content:encoded><![CDATA[<p>Chris, the relationship type stuff came from here: <a href="http://itc.conversationsnetwork.org/shows/detail3829.html" rel="nofollow">http://itc.conversationsnetwork.org/shows/detail3829.html</a> but it was in fact Bob Blakley not Jamie.</p>
<p>And yes completely agree with your points &#8211; my bad &#8211; I have confused the situation somewhat by messing up the history. Sorry folks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris Messina</title>
		<link>http://derivadow.com/2009/01/08/identity-relationships-and-why-oauth-and-openid-matter/#comment-2409</link>
		<dc:creator><![CDATA[Chris Messina]]></dc:creator>
		<pubDate>Thu, 08 Jan 2009 18:50:07 +0000</pubDate>
		<guid isPermaLink="false">http://derivadow.com/?p=849#comment-2409</guid>
		<description><![CDATA[Great post Tom. I really like the different classes of relationships -- do you have a reference where Jamie lays them out?

Also, I want to point out two important points.

1. Twitter was hacked with a dictionary attack against an admin&#039;s account. Not from phishing, and not from a third-party&#039;s database with Twitter credentials.
2. The phishing scam worked because it tricked people into thinking that they received a real email from Twitter.

In both cases, neither OpenID nor OAuth would have prevented the abuse from happening. It&#039;s important that that&#039;s clarified, because, while it&#039;s essential that Twitter support these technologies, it should be made clear that vigilance and strong passwords really were the only things that would have prevented this blow up.

I get what you&#039;re saying and completely agree -- but it&#039;s important that we address this situation as it actually happened.]]></description>
		<content:encoded><![CDATA[<p>Great post Tom. I really like the different classes of relationships &#8212; do you have a reference where Jamie lays them out?</p>
<p>Also, I want to point out two important points.</p>
<p>1. Twitter was hacked with a dictionary attack against an admin&#8217;s account. Not from phishing, and not from a third-party&#8217;s database with Twitter credentials.<br />
2. The phishing scam worked because it tricked people into thinking that they received a real email from Twitter.</p>
<p>In both cases, neither OpenID nor OAuth would have prevented the abuse from happening. It&#8217;s important that that&#8217;s clarified, because, while it&#8217;s essential that Twitter support these technologies, it should be made clear that vigilance and strong passwords really were the only things that would have prevented this blow up.</p>
<p>I get what you&#8217;re saying and completely agree &#8212; but it&#8217;s important that we address this situation as it actually happened.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

