Replying with "bullshit" isn't going to welcome anyone new into this community. Please stop doing this; you've been asked many times.<div><br></div><div>Yes, we should increase the involvement of browser vendors and it's great seeing the work that's happening around FireFox. I plan to track down that team tomorrow and get a better understanding of what browser-based APIs they're proposing and what information websites need to advertise to browsers.</div>
<div><br></div><div>--David</div><div><br><br><div class="gmail_quote">On Wed, May 19, 2010 at 1:12 AM, 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;">
HA! BullShit!<div><br></div><div>You know what?. I am beginning to believe that we need get the browser vendors to the OpenID community. Yes Google and Microsoft are already here, but i don't think they are here in the capacity of "browser vendors". We also need the mozilla, opera, safari guys.</div>
<div><br></div><div>And Mozilla has really been doing some good work in this area. Here is a link.</div><div><a href="https://wiki.mozilla.org/Labs/Weave/Identity/Account_Manager/Spec/Latest" target="_blank">https://wiki.mozilla.org/Labs/Weave/Identity/Account_Manager/Spec/Latest</a></div>
<div><br></div><div><a href="https://wiki.mozilla.org/Labs/Weave/Identity/Account_Manager/Spec/Latest" target="_blank"></a><br><br><div class="gmail_quote"><div><div></div><div class="h5">On Wed, May 19, 2010 at 1:25 PM, David Recordon <span dir="ltr"><<a href="mailto:recordond@gmail.com" target="_blank">recordond@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div></div><div class="h5">Coming out of some conversations at IIW today I've made some changes to the proposal. Patch is attached, but they are:<div>
- Allow passing in `user_id` as a hint when not using immediate mode in the request. </div><div>
<div> - Continue to allow users to enter URLs, email addresses, and click buttons but the returned user identifier must be a HTTPS URI.</div></div><div> - Include the expiration time within the signature.</div><div> - Clarify how you verify if the token endpoint is authoritative for a given user identifier.</div>
<div> - Simplify discovery by removing LRDD and using host-meta to determine the server token endpoint on a per domain (or sub-domain) basis. We're having a hard time finding use cases of running multiple different OpenID servers per domain.</div>
<div> - Remove the separate user info API endpoint and instead make the user identifiers a protected resource. Fetch the user identifier with an access token and it returns basic profile information as well as if the access token was issued by that specific user.</div>
<div><br></div><div>Thanks for all of the feedback and support both virtually and in person! I'm planning to move this proposal into GitHub next week (and work with Eran to actually format it like a spec) so that changes are easier to keep track of.</div>
<div><br></div><font color="#888888"><div>--David</div>
</font><br></div></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>
<br></blockquote></div><br><br clear="all"><br>-- <br><a href="http://hi.im/santosh" target="_blank">http://hi.im/santosh</a><br><br><br>
</div>
</blockquote></div><br></div>