You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Author: antoineturmel[at]gmail.com [Added to the original trac issue at 11.23pm, Tuesday, 22nd November 2011]
It's the ability to login with a BrowserID account that rely only email+password, no more information is stocked on the BrowserID server instead of Google/Facebook connect, plus it's quite easy to implement if you look at the documentation.
Author: TomH [Added to the original trac issue at 12.04am, Wednesday, 23rd November 2011]
Yes I know what it is, but I didn't think the server part was working yet.
I still think it's unlikely that we'd do anything until it has more traction, unless somebody was to come along and offer us a reasonable patch that wasn't going to have a high maintenance overhead.
Author: amm [Added to the original trac issue at 12.27am, Wednesday, 23rd November 2011]
It would be nice if people could come up with one standard and then just stick with it,instead of constantly coming up with new and incompatible standards that each need support. OpenID seems like a reasonable standard to me.
Given its penetration, I'd probably rather prefer to support Facebook and Twitter through their (misused) OAuth authentication than browserID for now, even though that would unfortunately require some special code for each site.
Reporter: antoineturmel[at]gmail.com
[Submitted to the original trac issue database at 6.44pm, Tuesday, 22nd November 2011]
It would be great for OSM to support BrowserID login system recently introduced by Mozilla.
https://browserid.org/
The text was updated successfully, but these errors were encountered: