<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>techno.blog(&#34;Dion&#34;) &#187; openid</title>
	<atom:link href="http://almaer.com/blog/tag/openid/feed" rel="self" type="application/rss+xml" />
	<link>http://almaer.com/blog</link>
	<description>blogging about life, the universe, and everything tech</description>
	<lastBuildDate>Tue, 03 Jan 2012 19:27:51 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Gears Future APIs: OpenID and OAuth</title>
		<link>http://almaer.com/blog/gears-future-apis-openid-and-oauth</link>
		<comments>http://almaer.com/blog/gears-future-apis-openid-and-oauth#comments</comments>
		<pubDate>Wed, 19 Mar 2008 16:20:14 +0000</pubDate>
		<dc:creator>dion</dc:creator>
				<category><![CDATA[Gears]]></category>
		<category><![CDATA[Tech]]></category>
		<category><![CDATA[Web Browsing]]></category>
		<category><![CDATA[oauth]]></category>
		<category><![CDATA[openid]]></category>

		<guid isPermaLink="false">http://almaer.com/blog/gears-future-apis-openid-and-oauth</guid>
		<description><![CDATA[
When I was looking over Brad Neuberg&#8217;s Paper Airplane thought experiment I noticed the single sign on feature, where you login to the browser, and then you are done.
I realized that this is what I actually want. Having one signon via OpenID is really nice. It allows me to plug in &#8220;http://almaer.com&#8221; as my identifier. [...]]]></description>
			<content:encoded><![CDATA[<p><img src='http://almaer.com/blog/uploads/singlesignon.png' alt='Single Sign On' border='0' style="float: right; padding: 8px"/></p>
<p>When I was looking over Brad Neuberg&#8217;s <a href="http://codinginparadise.org/paperairplane/">Paper Airplane</a> thought experiment I noticed the single sign on feature, where you login to the browser, and then you are done.</p>
<p>I realized that this is what I actually want. Having one signon via OpenID is really nice. It allows me to plug in &#8220;http://almaer.com&#8221; as my identifier. However, I always have to go around finding the OpenID option (if it exists) and put that in.</p>
<p>What I really want is for the browser to do that work for me. If a site groks OpenID the browser should be able to pass that over without having me intervene at all. It could hide the entire login process if we came up with a microformat to let all sides know what is going on.</p>
<p>It would be a breath of fresh air to be able to jump through sites leaving comments on blogs, and checking out my todo list, all without me once having to actually login.</p>
<p>I wonder if a Gear could be made with a complementary microformat / server side handshake that could then give us single sign-on in all of the browsers.</p>
<p>As Brian McCallister suggests:</p>

<div class="wp_syntax"><div class="code"><pre class="html" style="font-family:monospace;">&lt;link rel=&quot;openid-auth&quot; href=&quot;...&quot; /&gt;</pre></div></div>

<p><b>Other Future APIs</b></p>
<ul>
<li><a href="http://almaer.com/blog/gears-future-apis-services-daemon-api">Services / Daemon API</a></li>
<li><a href="http://almaer.com/blog/gears-future-apis-notification-api">Notification API</a></li>
<li><a href="http://almaer.com/blog/gears-future-apis-crypto-api">Crypto API</a></li>
<li><a href="http://almaer.com/blog/gears-future-apis-developer-tools">Developer Tools</a></li>
<li><a href="http://almaer.com/blog/gears-future-apis-factory-api-updates">Factory API updates</a></li>
<li><a href="http://almaer.com/blog/gears-future-apis-blob-api">Blob API</a></li>
<li><a href="http://almaer.com/blog/gears-future-apis-logging-api">Logging API</a></li>
<li><a href="http://almaer.com/blog/gears-future-apis-messaging-api">Messaging API</a></li>
<li><a href="http://almaer.com/blog/gears-future-apis-location-api">Location API</a></li>
<li><a href="http://almaer.com/blog/gears-future-apis-desktop-shortcut-api">Desktop Shortcut API</a></li>
<li><a href="http://almaer.com/blog/gears-future-apis-image-manipulation-api">Image Manipulation API</a></li>
<li><a href="http://almaer.com/blog/google-gears-upgrading-from-a-1950s-chevy-in-cuba">Introduction to the series</a></li>
</ul>
<p><em>Disclaimer: This is me rambling about APIs and tools that I would love to see in Gears, or the Open Web as a whole. Do you have ideas for cool Gears that make the Web better? <a href="http://groups.google.com/group/google-gears/">Let us know!</a>.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://almaer.com/blog/gears-future-apis-openid-and-oauth/feed</wfw:commentRss>
		<slash:comments>14</slash:comments>
		</item>
		<item>
		<title>Taking ownership of OpenID</title>
		<link>http://almaer.com/blog/taking-ownership-of-openid</link>
		<comments>http://almaer.com/blog/taking-ownership-of-openid#comments</comments>
		<pubDate>Thu, 13 Mar 2008 15:00:06 +0000</pubDate>
		<dc:creator>dion</dc:creator>
				<category><![CDATA[Tech]]></category>
		<category><![CDATA[clickpass]]></category>
		<category><![CDATA[openid]]></category>

		<guid isPermaLink="false">http://almaer.com/blog/taking-ownership-of-openid</guid>
		<description><![CDATA[
Peter Nixey is a good bloke that I met at a conference way back. At the time he showed me a killer CMS product that was nice and Ajax-y, and most of all usable enough for my mother.
Now he is in the news with his Y Combinator startup Clickpass and how it is trying to [...]]]></description>
			<content:encoded><![CDATA[<p><img src='http://almaer.com/blog/uploads/clickpass.png' alt='Clickpass' border='0' style="float: right; padding: 8px;"/></p>
<p>Peter Nixey is a good bloke that I met at a conference way back. At the time he showed me a killer CMS product that was nice and Ajax-y, and most of all usable enough for my mother.</p>
<p>Now he is in the news with his Y Combinator startup <a href="http://www.clickpass.com/">Clickpass</a> and how it is <a href="http://www.techcrunch.com/2008/03/11/clickpass-could-change-the-way-you-surf-the-web/">trying to make OpenID more usable</a>.</p>
<p>I decided to give it a roll, and switched out my delegated open id to:</p>

<div class="wp_syntax"><div class="code"><pre class="html" style="font-family:monospace;">&lt;link rel=&quot;openid.server&quot; href=&quot;https://www.clickpass.com/openid_server&quot;&gt;
&lt;link rel=&quot;openid.delegate&quot; href=&quot;http://clickpass.com/public/dalmaer&quot;&gt;</pre></div></div>

<p>When OpenID providers first started to come out of the woodwork it felt like deja vu. Of IM providers. Of email. Of blogs.</p>
<p>I am in a situation these days where I want to own the end point, but have the service outsourced. almaer.com forever. I didn&#8217;t want to be switching from myopenid.com/dion to youropenid.com/dion and hoping to be able to bridge the accounts. I want to use almaer.com as my rel=&#8221;me&#8221;. As soon as delegation came about, I was able to do that and life is happy.</p>
<p>I am looking forward to seeing Peter, and others, crack the nut on cool openid features, and also doing enough to allow Simon to not say &#8220;we are no worse than before&#8221; and be able to say &#8220;we are way better than before&#8221;.</p>
]]></content:encoded>
			<wfw:commentRss>http://almaer.com/blog/taking-ownership-of-openid/feed</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
		<item>
		<title>Mainstream OpenID?</title>
		<link>http://almaer.com/blog/mainstream-openid</link>
		<comments>http://almaer.com/blog/mainstream-openid#comments</comments>
		<pubDate>Sun, 10 Feb 2008 06:56:58 +0000</pubDate>
		<dc:creator>dion</dc:creator>
				<category><![CDATA[Comic]]></category>
		<category><![CDATA[Tech]]></category>
		<category><![CDATA[openid]]></category>

		<guid isPermaLink="false">http://almaer.com/blog/mainstream-openid</guid>
		<description><![CDATA[
Us techies love to talk about OpenID and the like. We complain about the idea of signing for one more bloody service.
However, OpenID has a few usability issues for non-technical folk. I can&#8217;t imagine explaining to my mum that she has to login using a domain URL. &#8220;You want me to type http://myopenidserver.com/seeg in the [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://almaer.com/blog/category/comic"><img src='http://almaer.com/blog/uploads/mainstreamopenid.png' alt='Mainstream OpenID' border='0'/></a></p>
<p>Us techies love to talk about OpenID and the like. We complain about the idea of signing for one more bloody service.</p>
<p>However, OpenID has a few usability issues for non-technical folk. I can&#8217;t imagine explaining to my mum that she has to login using a domain URL. &#8220;You want me to type http://myopenidserver.com/seeg in the browser?&#8221; &#8220;No! that is your username!&#8221;.</p>
<p>Well, these days could be numbered. I heard that there was a lot of chatter on this topic at Social Foo, and Brad has one <a href="http://brad.livejournal.com/2357444.html">solution</a> using < a href="http://yadis.org/wiki/Main_Page">Yadis</a> as opposed to the more pure DNS, or hacky ~username solutions.</p>
<p>Getting my mum to use her email as a username won&#8217;t be an issue. Hopefully she won&#8217;t fall for any OpenID phishing attacks though if it becomes popular.</p>
]]></content:encoded>
			<wfw:commentRss>http://almaer.com/blog/mainstream-openid/feed</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>

