<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>I am Zef - Latest Comments in OpenID, baby!</title><link>http://zefme.disqus.com/</link><description>None</description><atom:link href="https://zefme.disqus.com/openid_baby/latest.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Thu, 25 Jan 2007 11:29:08 -0000</lastBuildDate><item><title>Re: OpenID, baby!</title><link>http://zef.me/1249/openid-baby#comment-15004421</link><description>&lt;p&gt;Hm.  Having multiple _single_ signons would be a bit of a contradiction.&lt;/p&gt;&lt;p&gt;I think I'll first write a SINP server that also acts as a OpenID server.  And a client library which works via SINP or openID.&lt;/p&gt;&lt;p&gt;(When I got time :))&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Bas Westerbaan</dc:creator><pubDate>Thu, 25 Jan 2007 11:29:08 -0000</pubDate></item><item><title>Re: OpenID, baby!</title><link>http://zef.me/1249/openid-baby#comment-15004418</link><description>&lt;p&gt;I'm not sure if I would spend my time writing bridges between authentication systems, but it could be interesting. But as the amount of data we're talking about here (profile data for now) is fairly limited I would be tempted to just create an account once with the major single sign on providers out there. There are not that many that are being widely used. I have a Microsoft Passport, I have OpenID, I have a Google account. That's all I need.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Zef Hemel</dc:creator><pubDate>Wed, 24 Jan 2007 16:57:34 -0000</pubDate></item><item><title>Re: OpenID, baby!</title><link>http://zef.me/1249/openid-baby#comment-15004419</link><description>&lt;p&gt;It's actually pretty easy to create bridges between OpenID and other browser-based auth technologies. See my blog entry on the subject for a quick summary of how it works:&lt;br&gt;&lt;a href="http://www.apparently.me.uk/2767.html" rel="nofollow noopener" target="_blank" title="http://www.apparently.me.uk/2767.html"&gt;http://www.apparently.me.uk...&lt;/a&gt;&lt;/p&gt;&lt;p&gt;My take on it is a proxy that allows you to another auth provider as an OpenID IdP via the proxy, but I imagine you could probably do it the other way too if you want, depending on the flexibility of the other protocol.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Martin Atkins</dc:creator><pubDate>Wed, 24 Jan 2007 16:34:07 -0000</pubDate></item><item><title>Re: OpenID, baby!</title><link>http://zef.me/1249/openid-baby#comment-15004420</link><description>&lt;p&gt;It's tempting to suggest (in my opinion improvements) borrowed from SINP to OpenID, but I'm afraid they are already too big for drastic changes (they'd loose users) and not big enough to cope with that.&lt;/p&gt;&lt;p&gt;It's tempting to work on SINP again, but SINP hasn't got any momentum at all. (Ok, I'll be honoust. I really didn't work on it anymore)&lt;/p&gt;&lt;p&gt;Jabber has got this really great thing that are called gateways. You can chat with someone using msn via a gateway server with jabber. Maybe it would be nice to implement this for SINP/OpenID. (and all those others)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Bas Westerbaan</dc:creator><pubDate>Wed, 24 Jan 2007 14:32:18 -0000</pubDate></item></channel></rss>