The end goal for BrowserID involves naitve browser support for authentication, using public-key crypto with the keys generated and stored by the browser. browserid.org exists as a compatibility shim to make BrowserID universally available *before* browsers have naitve support for it; they really need to document that plan better on the site.(Also, you could implement BrowserID server-side without JavaScript; browserid.org implements it client-side using JavaScript to avoid the need for specialized server-side code on each site adopting it, which greatly simplifies adoption.)OpenID requires a webpage supporting a specialized authentication protocol which websites don't normally implement. You can't use OpenID with an arbitrary homepage URL without either hosting an OpenID implementation yourself or delegating to a third-party authentication provider. More importantly, having a personal OpenID that doesn't depend on a third-party account requires hosting a personal homepage, which not every Internet user has or needs. As a result, in practice, the vast majority of OpenID users rely on a third-party identity provider such as the dozen whose icons you show at the top of this form, and that seems unlikely to ever change.BrowserID specifically ties identity to an email address, which everyone with Internet access already has. People can easily obtain an email address in their own name and at their own domain, and use that as their BrowserID, *without* having to seek out additional support for a specialized protocol as in OpenID. Also, almost all sites already want an email address when signing up, so using BrowserID avoids the need to deal with other pieces of information. BrowserID supports changing that email address, so that you don't get stuck with a pile of accounts using when you've migrated to . BrowserID also pre-validates the email address, which means you don't have to redo the usual email-a-link verification with every single site.You mentioned that you have three email addresses and only one homepage. That case actually works *better* with BrowserID, which offers you the choice of which email address you want to use to authenticate to any given site. So, you can easily maintain accounts for , , or , without needing to host three homepages or rely on third-party authentication providers.As for using multiple browsers, BrowserID supports migrating from browserid.org to in-browser authentication without changing anything visible to sites, and browsers which support in-browser authentication will almost certainly support migrating or sharing identities between themselves.So, I personally prefer BrowserID because it gives me more control over my own identity, lets me maintain multiple identities as easily as having multiple email addresses, avoids tying my account with a site to an account I currently have with a third party (and may want to drop in the future), reduces the number of pieces of information I need to provide to sites to one, eliminates the per-site email verification, and provides a path leading to in-browser crypto-based authentication.Does that help answer your question?