+1. If you don't want to be correlated, use a different OpenId. Your OpenId provider should be able to provide you with more than one. I think this discussion should be more directed at how the OP can help us avoid the problem of correlation, rather than the RP.
<br><br>david<br><br><div><span class="gmail_quote">On 5/14/07, <b class="gmail_sendername">Martin Atkins</b> <<a href="mailto:mart@degeneration.co.uk">mart@degeneration.co.uk</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Simon Willison wrote:<br>> One of the benefits of OpenID is that it lets accounts on different<br>> sites be linked together. This has plenty of exciting implications,<br>> but also introduces new privacy concerns. If a site publishes a user's
<br>> OpenID anywhere it is enabling cross-site correlation whether or not<br>> the user (or site) wants it to happen.<br>><br><br>Im afraid that my view on this problem has always been that if you don't<br>want to be correlated, you should use a different identifier. The beauty
<br>of OpenID is that you don't have one identifier for many sites, or one<br>identifier for one site... you have many identifiers for many sites. You<br>can use the same single identifier for all sites, or you could use a
<br>different identifier for each site, or a combination of the two.<br><br>This is already possible today. It's even easier with the help of<br>"directed identity".<br><br>_______________________________________________
<br>general mailing list<br><a href="mailto:general@openid.net">general@openid.net</a><br><a href="http://openid.net/mailman/listinfo/general">http://openid.net/mailman/listinfo/general</a><br></blockquote></div><br>