hehehehe can you give me one more say at this one.<div><br></div><div>all the code i can see is "php". Can i see "python" "java" or "ruby" or "c++" please!<br><br><div class="gmail_quote">
On Sun, May 16, 2010 at 8:26 PM, Santosh Rajan <span dir="ltr"><<a href="mailto:santrajan@gmail.com">santrajan@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
hehehe this is so hilarious, i am sorry i can't help it.<div><div></div><div class="h5"><br><br><div class="gmail_quote">On Sun, May 16, 2010 at 8:03 PM, Hans Granqvist <span dir="ltr"><<a href="mailto:hans@granqvist.com" target="_blank">hans@granqvist.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div>Putting the spec itself aside for a moment, I think the moniker "OpenID Connect" is not helping... unless you're designing this only for people who already know and use OpenID.</div>
<div><br></div><div>Facebook Connect was all about connecting to a single end point, a company, a concrete institution. People know what Facebook is before seeing the FB Connect button.</div><div><br></div><div>Anyone who sees OpenID Connect is going to look for the Open ID equivalence. But there is no such single end point or company. This will confuse and annoy since almost everyone is conditioned by Facebook connect & few know what OpenID is.</div>
<div><br></div><div>Perhaps it would be better to put forward the mechanism, "Connect using OpenID" or similar.</div><div><br></div><div>Thanks,</div><div>Hans</div><div><br><div><div>On May 15, 2010, at 6:58 PM, Chris Messina wrote:</div>
<br><blockquote type="cite">I'm excite to see this proposal, as it represents something concrete to discuss and debate. I'd like to see how this strawman proposal can be used within the technical working group as a point of inspiration.<div>
<br> </div><div>I'd also point out, for completeness, that OpenID Connect does not necessarily represent what OpenID v.Next should look like, but instead is more like a profile of several technologies strung together to address the need of a "connect" API pattern with decentralization at its core (a feature that I consider absolutely essential to its success and architecture).</div>
<div><br></div><div>Looking forward to feedback on this.</div><div><br></div><div>Chris<br><br><div class="gmail_quote">On Sat, May 15, 2010 at 4:57 PM, David Recordon <span dir="ltr"><<a href="mailto:recordond@gmail.com" target="_blank">recordond@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">The past few months I've had a bunch of one on one conversations with a lot of different people – including many of folks on this list – about ways to build a future version of OpenID on top of OAuth 2.0. Back in March when I wrote a draft of OAuth 2.0 I mentioned it as one of my future goals as well (<a href="http://daveman692.livejournal.com/349384.html" target="_blank">http://daveman692.livejournal.com/349384.html</a>).<div>
<br></div><div>Basically moving us to where there's a true technology stack of TCP/IP -> HTTP -> SSL -> OAuth 2.0 -> OpenID -> (all sorts of awesome APIs). Not just modernizing the technology, but also focusing on solving a few of the key "product" issues we hear time and time again.<div>
<br></div><div>I took the past few days to write down a lot of these ideas and glue them together. Talked with Chris Messina who thought it was an interesting idea and decided to dub it "OpenID Connect" (see <a href="http://factoryjoe.com/blog/2010/01/04/openid-connect/" target="_blank">http://factoryjoe.com/blog/2010/01/04/openid-connect/</a>). And thanks to Eran Hammer-Lahav and Joseph Smarr for some help writing bits of it!</div>
<div><br></div><div>So, a modest proposal that I hope gets the conversation going again. <a href="http://openidconnect.com/" target="_blank">http://openidconnect.com/</a></div><div><div><br></div><font color="#888888"><div>
--David</div></font></div></div> <br>_______________________________________________<br> specs mailing list<br> <a href="mailto:specs@lists.openid.net" target="_blank">specs@lists.openid.net</a><br> <a href="http://lists.openid.net/mailman/listinfo/openid-specs" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Chris Messina<br>Open Web Advocate, Google<br><br>Personal: <a href="http://factoryjoe.com" target="_blank">http://factoryjoe.com</a><br>Follow me on Buzz: <a href="http://buzz.google.com/chrismessina" target="_blank">http://buzz.google.com/chrismessina</a> <br>
...or Twitter: <a href="http://twitter.com/chrismessina" target="_blank">http://twitter.com/chrismessina</a> <br><br>This email is: [ ] shareable [X] ask first [ ] private<br> </div> _______________________________________________<br>
specs mailing list<br><a href="mailto:specs@lists.openid.net" target="_blank">specs@lists.openid.net</a><br><a href="http://lists.openid.net/mailman/listinfo/openid-specs" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs</a><br>
</blockquote></div><br></div></div><br>_______________________________________________<br>
specs mailing list<br>
<a href="mailto:specs@lists.openid.net" target="_blank">specs@lists.openid.net</a><br>
<a href="http://lists.openid.net/mailman/listinfo/openid-specs" target="_blank">http://lists.openid.net/mailman/listinfo/openid-specs</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br></div></div><a href="http://hi.im/santosh" target="_blank">http://hi.im/santosh</a><br><br><br>
</blockquote></div><br><br clear="all"><br>-- <br><a href="http://hi.im/santosh">http://hi.im/santosh</a><br><br><br>
</div>