It would be better to say "I'd like OP1, but only for PCs, and OP2
for iPhones, ..." all somehow expressed in the XRDS file so the RP
could do the redirect to the right OP based on which device I'm
using, all while using the same identifier.
On a related note, I'd like it if the XRDS file could (optionally)
have multiple OP's identified in such a way that the RP *should* take
its cue to (if offering that feature) ask the user which OP they want
to use rather than redirecting them right away. I'm not sure but I
*think* XRDS would be the right place to start with this; the idea
being that, if I had an OP that used one-time-only passwords for
authentication, I'd want to save those pre-readied passwords for the
situations when I *really* wanted them, and otherwise use a "weaker"
OP.
I could also exert some control over my privacy by electing to use
OP#1 for my work-related logins, OP#2 for my personal logins, OP#3
for my recreational logins, OP#4 for sites I wasn't sure about yet,
and so on. Any visitor to my site could determine which OP's were
*possible*, but would have no guarantee that I actually *used* any
particular one of them, and compromising the data stored by any
single OP would not yield *all* my online activities.
-Shade
27 messages in net.openid.general[OpenID] XRDS multi-OP listing?
.gif, .gif
