Please consider this really as a very, very early alpha-stage. It works for me from a technical point of view (I tried for instance authenticating with StackExchange but also run some tests from http://test-id.org/), but a lot of stuff needs to be addressed before it can really be considered usable:
- The page layout is non-existent. It would be great if someone is interested to help me out with graphical design and working on a logo, since I'm not talented in that respect. (Also, I'll probably split the lots of information on the start page into different pages to make it more digestable.)
- The connection is not yet TLS-encrypted. This will definitely come in the future, but I have to get around some problems with my hosting to make it work. (In particular I need a second IP for my server (or a separate VPS for nameid) because I already use TLS for some other site on the same IP.)
- There's not yet a .bit domain set up. I already own nameid.bit and myid.bit (id.bit and openid.bit would be nice, too, but both are already taken by someone else), yet have to update the name to point to the correct IP. However, the OpenID identifier will still be nameid.org since the relaying party connects to it directly and this will probably fail for .bit domains.
- To actually log in, you have to manually sign a challenge message at the moment - which means using namecoin-qt's "signmessage" on the commandline, and before that, figuring out the address connected to your name. I plan to implement a browser plugin to do that for you (but you still need namecoin-qt installed).
- I plan to separate the key used to sign into NameID from the key that owns your id/-name so that you don't have to use that "more precious" key all the time and can instead store it safely away. The idea is to provide a specification for how to link public keys (another namecoin address or maybe even a GnuPG key) to your id/ which will then be recognized by NameID in addition to the real private key of the name.
- You have to register your id/ somewhere else, I don't provide that service (and don't plan on doing it). After all, you and only you should own the private key. So it will still be probably quite hard for someone new to namecoin to use it, even when the browser plugin will be there. But maybe namecoin-qt could add a feature to easily register identities (or is it already there?).