4 ms·
Go to https://eyedee.me https://eyedee.me and create an DASD account Go to http://crossword.thetimes.co.uk/ http://crossword.thetimes.co.uk/ - this is a non-Mo
by ozten 14y ago
Go to https://eyedee.me https://eyedee.me and create an DASD account
Go to http://crossword.thetimes.co.uk/ http://crossword.thetimes.co.uk/ - this is a non-Mozilla RP
Enter DASD@eyedee.com - This is a Primary Identity provider, source at [1]
So you see there is no BrowserID provider choosing screen, it's naturally part of the flow. you enter DASD@eyedee.com and the system checks for support and delegates to eyedee.com.
[1] https://github.com/mozilla/eyedee.me https://github.com/mozilla/eyedee.me
- DASD 14y agoThanks for posting the process flow. So (https://login.persona.org/sign_in https://login.persona.org/sign_in) will always be shown? If so, then how is this truly decentralized with my privacy concerns mentioned above?
- ozten 14y agoIf you had a browser, say Opera, with native support for the BrowserID protocol, then you would not see login.persona.org. No requests would be made to a Mozilla server. login.persona.org is two things: 1) A JavaScript shim for cross platform support (Opera + BrowserID support would avoid this) 2) A Fallback Identity provider (eyedee.me avoids this)