<HTML dir=ltr><HEAD></HEAD>
<BODY>
<DIV id=idOWAReplyText55560 dir=ltr>
<DIV dir=ltr><FONT face=Arial color=#000000>I not sure which cause folks are gearing up for a fight over.</FONT></DIV>
<DIV dir=ltr><FONT face=Arial></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial>Its pretty obviously true that the traditional mega-plexes (LiveID, Yahoo, AOL) are trying to exercise a disapportionate amount of control - when offering a UCI identity yet being unwilling to rely on those of others. This is somewhat like LiveJournal spewing our FOAF files, that nobody can rely upon - for anything particularly useful. Its all a very nice PR gimmick ... which was the journalist's main point (as paraphrased by Peter).</FONT></DIV>
<DIV dir=ltr><FONT face=Arial></FONT> </DIV>
<DIV dir=ltr><FONT face=Arial>At least Google is bucking the trend, by offering to be SAML2 or openid relying party (within a Google-as-TTP-SP-Hub risk model and when whichever protocol best fits (currently) the app domain).</FONT></DIV>
<DIV dir=ltr><FONT face=Arial color=#000000></FONT> </DIV></DIV>
<DIV><FONT face=Arial>Google is giving away free SAML2 IDP code... open source style. Its promoting outsourcing your IDP to an id-broker bureau ... in its newest Google Apps service (albeit SAML2, for now). Dont criticise *them* for having a lack of open source commitement! Obviously, there is no shortage of openid open source materials to talk to Google's blog service.</FONT></DIV>
<DIV><FONT face=Arial></FONT> </DIV>
<DIV><FONT face=Arial>---------</FONT></DIV>
<DIV><FONT face=Arial></FONT> </DIV>
<DIV><FONT face=Arial>So, I wonder how of the 11,000 places that accept openid are Google blogspots?</FONT></DIV>
<DIV><FONT face=Arial></FONT> </DIV>
<DIV><FONT face=Arial>I think we need a better definition of "adoption", so our cliams stays credible - acting as a trustworthy indicator for professional journalists, etc.</FONT></DIV>
<DIV><FONT face=Arial></FONT> </DIV>
<P><BR> </P>
<DIV>
<HR tabIndex=-1>
</DIV>
<DIV><FONT face=Tahoma size=2><B>From:</B> David Recordon<BR><B>Sent:</B> Thu 3/27/2008 8:48 AM<BR><B>To:</B> tom<BR><B>Cc:</B> OpenID List<BR><B>Subject:</B> Re: [OpenID] Putting the "open" back into OpenID - a call to the FSOSS community<BR></FONT><BR></DIV>
<DIV><PRE style="WORD-WRAP: break-word">Hey Tom,
Between LiveJournal and now Movable Type Open Source, we're game. I'd
love to see this end up as something published by the Foundation, for
whatever that ends up meaning. :)
--David
On Mar 26, 2008, at 11:07 PM, tom wrote:
> Hello folks,
>
> I am fed up with those "I get the ID but not the open" comments that
> arrive under blogs written about OpenID. [ latest here ->
> http://www.techcrunch.com/2008/03/24/is-openid-being-exploited-by-the-big-internet-companies/
> ]
>
> It's time to fight back and it's the Free software and Open source
> (FSOSS) community that can best explain why OpenID is open and how the
> FSOSS is using it in an open way.
>
> We (Barnraiser) have three amazing [being humble] free software
> products
> built around OpenID. We've been able to do that because it's open. We
> wish to collaborate with 9 other members of the FSOSS community to
> write
> an article entitled "10 FSOSS initiatives embracing OpenID" and we
> want
> to publish that to Slashdot, Techcrunch etc.
>
> We are looking for 9 other great, amazing and insanely awesome FSOSS
> projects that want to join with us in being in the article, so if you
> are one of those please write to me with a few sentences outlining
> your
> project to me.
>
> Kind regards,
>
> Tom
>
>
>
> --
> Tom Calthrop
> Founding director, Barnraiser.
>
> Dedicated to giving people the tools they need to share
> knowledge and advance society through social software.
>
> Web site: http://www.barnraiser.org/
> OpenID: http://tom.calthrop.info/
>
> _______________________________________________
> general mailing list
> general@openid.net
> http://openid.net/mailman/listinfo/general
_______________________________________________
general mailing list
general@openid.net
http://openid.net/mailman/listinfo/general
</PRE></DIV></BODY></HTML>