<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">
<div>Allen,</div><div><br></div><div>Very interesting -- I didn't know this. I guess that your applications were already well-experienced with pseudonyms through your proprietary SSO, so you've had no problems with the opaque URL's. If only we had trained our apps so well long ago.</div><div><br></div><div>Thanks a lot for the details on the history and rationale,</div><div>Nate.</div><br><div><div>On 6 Nov 2008, at 00:06, Allen Tom wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; ">Prior to launching our OpenID service, Yahoo's policy with our proprietary SSO service was to issue RP-specific identifiers to prevent RPs from sharing data about the user and correlating user behavior across different sites.</span></blockquote></div><br></body></html>