3 ms·
I don't follow you, what's invasive/interfering about it? You & your browser can decide whether any of the steps of this process actually happen.
by bct 15y ago
I don't follow you, what's invasive/interfering about it? You & your browser can decide whether any of the steps of this process actually happen.
- JoshTriplett 15y agoThe proposed BrowserID standard specifically suggests that the browser should ask the email provider to validate the email, and only fall back to the usual email-me-a-link validation if the email provider doesn't "natively" support BrowserID. I'd prefer to always go through email-me-a-link verification (ideally with some kind of crypto involved), rather than involving the email provider in any way other than SMTP and IMAP.
- bct 15y agoCan you link me to where you're reading that? I don't see anything like that (but I've only skimmed the documentation).
- JoshTriplett 15y agoSee the teaser at https://browserid.org/primaries https://browserid.org/primaries , and the documentation at http://lloyd.io/how-browserid-works http://lloyd.io/how-browserid-works .
- bct 15y agoI've read it more thoroughly now, but I'm still not sure where you're coming from. You'd rather use a secondary identity authority, even when a primary is available? Or are you saying you'd like to require a full send-me-an-email-and-i'll-click-on-a-link verification every time you log in to a relying party?