Besides that, we really tried to implement it. The first information OpenID must give to Nabble is the email of the user. Not all providers give this information, which is pointless to Nabble because we would have to request the emails anyways in the registration page. So we cannot generally accept OpenID on Nabble. But we started looking into Google and Facebook because they provide the email of the user and this integration could possibly work. In fact, it was quite easy to integrate these services with Nabble, until we tested embedding and custom domain names. Nabble has a complex login mechanism for embedding and only Google was able to work with it. On the other hand, Facebook requires a fixed domain to send/receive requests, so custom domains don't work. In summary, Google is probably the only OpenID provider that can work smoothly with Nabble. Since you originally requested generic OpenID, I am not sure Google will satisfy your needs. Unfortunately, that's the only service we could offer for now. Please let me know what you think.
• without that simplicity, I would not have joined some of the stacks.
… almost all the responses here really *are* using third party login systems -- twitter, facebook, openid, etc. I guess what that says is that for certain lightweight-ish things, this third-party login model DOES work.
As I explained in my previous post, the problem is embedding and custom domain names. These two features don't work smoothly with third-party logins. Besides that, we are involved with new projects and we will be quite busy for several months. Third-party logins should be off until then.