<?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; oauth</title>
	<atom:link href="http://almaer.com/blog/tag/oauth/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, 28 Aug 2012 14:41:55 +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>
	</channel>
</rss>
