I expect Google might have a (legal) opinion on characterizing this
application as 'Google OpenID'
I think I'll wait for Google itself to enable my Gmail as an OpenID.
paul
Vinay Gupta wrote:
http://openid-provider.appspot.com/
Somebody used their app hosting service and implemented an
When Google eventually does make a proper OpenID provider all the OpenIDs
provided by openid-provider.appspot.com would not match.
Would get very confusing apart from advanced users that understand the
distinction.
Immad
On Wed, Apr 9, 2008 at 12:49 PM, Paul Madsen [EMAIL PROTECTED] wrote:
I
I agree. I think this is an excellent technology demonstration, but it is a
third-party, not Google, that is enabling the ID.
John
2008/4/9 Immad Akhund [EMAIL PROTECTED]:
When Google eventually does make a proper OpenID provider all the OpenIDs
provided by openid-provider.appspot.com would
James,
I don't think we need SRV records to do this. NAPTR would suffice, as that
would allow one to transform one string into another.
But, it seems that there is an overwhelming preference for using some kind
of string of undetermined structure to identify a user which is not of an
e-mail
I think that kind of misses the point. The *namespace* that google
manages is now open for business as an OpenID provider. It's an
unanticipated side-effect of the APIs.
I think it's kind of a big deal, actually, in terms of how OpenID is
right from an engineering perspective and how it
Any sufficiently advanced web site system is indistinguishable from an OP.
Or, rather, can be turned into an OP. :)
Vinay Gupta wrote:
I think that kind of misses the point. The *namespace* that google
manages is now open for business as an OpenID provider. It's an
unanticipated side-effect
