Today, if you want to use a card on another machine you have to move it there by exporting and importing. Alternatively, you could use a different card but associate it with the same account at the website. Our samples on http://cardspace.netfx3.com show how websites can easily allow this and it is also a very useful feature for handling revocation and different user contexts. For example, I might want to use an employer card *and* a personal card to access, say, fidelity.com. In one context I'm seeing what my employer is paying into my 401K and in the other I'm looking at my overall retirement fund (imagine I change employer). In the future we'll have support for cards and token generation on devices such as smart cards and phones - Novell and Microsoft have already demostrated prototypes. This enables secure roaming scenarios where I can login using a kiosk machine when on vacation carrying nothing more than my phone and without having to worry about key loggers since all that passes through the compromised Internet Cafe machine is an encrypted token with a limited lifetime.
This raises a few immediate questions:
The simplest ways to record CardSpace for a screencast are to use a virtual machine or terminal services (aka Remote Desktop).