Kevin: I raise with an XPCOM interface; Chuck: I Call.
Chuck just dropped me a line, he's taken the XPCOM interface that Kevin defined in his FireFox extension for CardSpace and implemented the interface to allow his code to work in the same vein. He's also added the code for a configuration dialog, which Kevin hadn't done yet, so now you can switch between the different Card Selectors in FireFox from a configuration dialog.
One word describes this: SWEET.
Chuck says it just perfectly:
The great news is that people implementing selectors will no longer need to worry about augmenting the browser. Now hopefully we can all quickly agree on a preferences structure to allow any implementation to easily add itself to the list.
If you're interested in writing you're own plugin, it's pretty simple...here's the basics of an XPCOM component that implements the plugin interface:
http://openinfocard.googlecode.com/svn/trunk/firefox/components/Identityselector.js
I was recently asked about this idea that there should be multiple card selectors, and doesn't that somehow break rule #7 "Consistent Experience Across Contexts" ?
The answer is, No, not really. It's important that each user is given a consistent experience across each context, not that different users experience the same thing. As a matter of fact this impairs phishing attempts due to the phisher not really knowing what Identity selector they would have to fake out to dupe the user.
This is just more Good News on the Identity Frontier.
Labels: CardSpace
![]() |
|

Links to this post:
Create a Link
<< Home