<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Agreed with Chris here. I don't inherently have a problem with using RPX since it does provide value, but the trust root needs to be fixed and far more transparency added by the Foundation when choosing to use a vendor's product.<div><br></div><div>I'm also concerned about some of the optics when it comes to JanRain. As far as I can tell JanRain has started a consulting engagement when one of the developers the OpenID Foundation retained to build the membership and elections tool. The elections tool now has JanRain's solution in it.</div><div><br></div><div>Given Brian Kissel's growing involvement in the Foundation the past few months I would have expected him to disclose this as the CEO of JanRain especially as he's currently running for a *community* board seat in the election.</div><div><br></div><div>As to the developer himself, I have no idea if he has a NDA with JanRain that might have prevented this, if he did disclose it to the committee of the Foundation that engaged him, or what. I'm much less concerned about his role in all of this as I'm sure in both engagements he's just doing what he's being paid to do.</div><div><br></div><div>--David<br><div><br><div><div>On Dec 5, 2008, at 11:08 AM, Chris Messina wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div class="gmail_quote">On Fri, Dec 5, 2008 at 11:00 AM, Steven Livingstone-Perez <span dir="ltr"><<a href="mailto:weblivz@hotmail.com">weblivz@hotmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> I don't really have much of a say on this (other than being a new member)<br> and you may 100% disagree with me, but IMHO there *is* an argument that in<br> using best of breed products we can demonstrate the power of OpenID to users<br> ... compared with the cost/effort to implement something that already does a<br> really good job.</blockquote><div><br></div><div>No argument there. Making OpenID seem awesome (or live up to its promised awesomeness) isn't really something that I'm questioning.</div><div><br></div><div>This kind of experience can be done without the use of a vendor product, though, but requires quite a bit more work and time.</div> <div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">I do understand the endorsement aspect, but on the other hand the UX is the<br> biggest issue OpenID seems to have at the moment and it seems to me that<br> using such products (so long as they are donated as such and not specific<br> long term to any one company) can only be a positive thing.<br></blockquote></div><br clear="all">Therein lies the rub. I'm not arguing against using RPX, but for concealing it in the trust root (since currently people end up trusting *.<a href="http://rpxnow.com">rpxnow.com</a> rather than <a href="http://openid.net">openid.net</a> — thereby creating a long term situation that's hard to switch from (without users having to *reassociate*)) and for getting some transparency into how the decision to use RPX was made.<div> <br></div><div>I agree with Eran that the experience is better -- but let's not set a poor precedent in the interest of expediency.<br><div><br></div><div>Chris</div><div><br>-- <br>Chris Messina<br>Citizen-Participant &<br> Open Technology Advocate-at-Large<br><a href="http://factoryjoe.com">factoryjoe.com</a> # <a href="http://diso-project.org">diso-project.org</a><br><a href="http://citizenagency.com">citizenagency.com</a> # <a href="http://vidoop.com">vidoop.com</a><br> This email is: [ ] bloggable [X] ask first [ ] private<br> </div></div> _______________________________________________<br>general mailing list<br><a href="mailto:general@openid.net">general@openid.net</a><br>http://openid.net/mailman/listinfo/general<br></blockquote></div><br></div></div></body></html>