<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Feb 15, 2012, at 3:23 PM, Francisco Corella wrote:</div><div><br></div><blockquote type="cite"><div><div style="color: rgb(0, 0, 0); background-color: rgb(255, 255, 255); position: static; z-index: auto; "><font class="Apple-style-span" face="'times new roman', 'new york', times, serif"><span class="Apple-style-span" style="font-size: 12pt;">It's not a good idea to detect an OP automatically, as you seem to say</span></font><br><font class="Apple-style-span" face="'times new roman', 'new york', times, serif"><span class="Apple-style-span" style="font-size: 12pt;">Sxipper used to do, whether the OP is detected using a heuristic or</span></font><br><font class="Apple-style-span" face="'times new roman', 'new york', times, serif"><span class="Apple-style-span" style="font-size: 12pt;">using explicit markup in the OP's site. </span></font></div></div></blockquote><div><br></div><div>We did not add the OP automatically, but we detected that a site supported OpenID as an OP, and then gave the user a choice to add the OP.</div><div><br></div><blockquote type="cite"><div><div style="color: rgb(0, 0, 0); background-color: rgb(255, 255, 255); font-family: 'times new roman', 'new york', times, serif; font-size: 12pt; position: static; z-index: auto; "><br>As I said before in response to your earlier statement, the relying<br>party can easily detect whether the browser is enhanced or not, and<br>fall back on an ordinary OpenID interface if it isn't.<br></div></div></blockquote><div><br></div></div>Well, I would say that Sxipper worked better, as the RP did not need to detect anything.<div><br></div><div>The problem at hand is how to solve the NASCAR problem for un-enhanced browsers. Your title states that you have solved it. Solving it by enhancing the browse is not new.</div><div><br></div><div><br></div></body></html>