Posted
8 days
ago
A new feature landed in Persona last month that promises to make the sign-in process even smoother by asking users to consent to site-specific Terms of Service and Privacy Policies as a native part of the login flow.
This means that sites
... [More]
using Persona can easily present their own terms of service and privacy policy to users in an obvious, seamless, and uniform location. Moving user consent into the sign-in dialog also lets websites get rid of their “I agree” checkboxes, while still being certain that users were informed of and consented to the site’s terms on every sign-in.
Supporting this API is dead simple, saves users a click, and means one less form for websites to manage. We think it makes sign-in easier for everyone, and we’d love to see more sites using this new, optional feature. To lean more, check out our documentation and let us know what you think via our mailing list, IRC channel, or by tweeting with the #mozpersona hash-tag. [Less]
Posted
8 days
ago
A new feature landed in Persona last month that promises to make the sign-in process even smoother by asking users to consent to site-specific Terms of Service and Privacy Policies as a native part of the login flow.
This means that sites
... [More]
using Persona can easily present their own terms of service and privacy policy to users in an obvious, seamless, and uniform location. Moving user consent into the sign-in dialog also lets websites get rid of their “I agree” checkboxes, while still being certain that users were informed of and consented to the site’s terms on every sign-in.
Supporting this API is dead simple, saves users a click, and means one less form for websites to manage. We think it makes sign-in easier for everyone, and we’d love to see more sites using this new, optional feature. To lean more, check out our documentation and let us know what you think via our mailing list, IRC channel, or by tweeting with the #mozpersona hash-tag. [Less]
Posted
3 months
ago
This past year we’ve been building the core of a Web-scale identity system. We’ve been calling it BrowserID: our name both for the technology1 and the Mozilla service that implements the technology. Today we’d like to introduce Mozilla Persona
... [More]
, our new name for the complete Identity offering from Mozilla: a collection of components and experiences we’re designing to manage the whole of a user’s online identity with our core values of user control, safety, and convenience.
The Persona name resonates with the idea of personhood as well as online identity as a facet of our lives, and therefore strongly tied to user identity. We’re very excited about this new name and the new features our identity system will offer. Some of the things we’re planning: an identity dashboard, user data interconnect features, and more.
What about “BrowserID?”
BrowserID remains the developer-facing name of the protocol. Websites, email providers, and browser implementors will continue to refer to the BrowserID protocol.
Over the next few months, we will begin to transition the Mozilla Web-based implementation of the BrowserID pop-up over to the new name. But don’t worry, we’ll work hard to make sure the transition is completely seamless for everyone.
Wait, what about Firefox’s Personas?
For the past few years, many Firefox users have enjoyed “Personas”—a quick and fun way to theme the background of the Firefox toolbar. The Addons team blogged about changing their name a couple of weeks ago. No doubt there will be some confusion during this transition, so if you have ideas for how to make the transition smoother, definitely let us know! We believe the long-term value of the Persona name will far outlast the short-term discomfort of change.
We hope you’re as excited about this change as we are. We look forward to an action-packed 2012 for our distributed Identity system under the Mozilla Persona umbrella!
As always, feedback and questions are always welcome on our mailing list, or by tweeting with the #browserid or #mozpersona hash-tag.
1: Some of you may remember that BrowserID came from the Verified Email Protocol. We haven’t forgotten, of course—but BrowserID has become the name of the technology nonetheless. [Less]
Posted
3 months
ago
We’re proud to announce that with the latest update to BrowserID the sign-in flow is available in 28 languages, in addition to English.
Like many of our previous updates, users and sites automatically benefit from the added feature without
... [More]
having to change anything. Users will see BrowserID in their preferred language, based on their browser’s settings.
Here’s what BrowserID looks like in traditional Chinese:
This change has been possible because of our amazing community of volunteers. Firefox ships in over 70 languages and that energy also powers our vision for a cross-platform identity management.
Along with ID provider support, shipping our service in multiple languages are two big milestones for BrowserID maturity.
Users of your websites can now have a native language experience in the following locales:
Afrikaans (af)
català (ca)
Čeština (cs)
Dansk (da)
Deutsch (de)
Ελληνικά (el)
Español (es)
Eesti keel (et)
Euskara (eu)
suomi (fi)
Français (fr)
Frysk (fy)
Gaeilge (ga)
Hrvatski (hr)
Italiano (it)
Ligurian (lij)
Nederlands (nl)
ਪੰਜਾਬੀ (pa)
Polski (pl)
Русский (ru)
slovenčina (sk)
slovenščina (sl)
Shqip (sq)
Српски (sr)
Svenska (sv)
Türkçe (tr)
中文 (简体)
(zh-CN)
正體中文 (繁體)
(zh-TW)Dig Deeper
How the Node Based BrowserID Service Shipped 28 New Languages
BrowserID for the rest of the world [Less]
Posted
3 months
ago
Last week we pushed out a BrowserID feature that gets us closer to the decentralized identity system we envision for the Web. But more than that, it enables a truly awesome user experience—registration flows go from 8 screens to one simple sign-in.
... [More]
Seriously!
See for yourself:
Chicken or egg
Some context: Building a distributed system is a chicken and egg problem
- you have to design a system that can demonstrate the power of your idea and the advantages of a distributed architecture while you bring in participants who will become actual nodes in the system. That’s why, so far, BrowserID has operated with scaffolding that uses the BrowserID service itself to vouch for email addresses.
With our latest update, however, we’re setting aside some of that scaffolding and allowing a fully decentralized system to emerge: Identity providers can become full-fledged participants in BrowserID and directly vouch for their users’ email addresses.
What’s changed and what you need to know
If you’re a website that’s already implemented BrowserID, you don’t have to do a thing: BrowserID is just better for you! Up to this point, Browser ID has been vouching for users’ email addresses on behalf of participating websites. Now email providers can directly vouch for their users, eliminating the need for an email confirmation step or a BrowserID password.
Note that this change only takes effect when the email provider for a given address implements BrowserID support. Other email addresses continue to work in the same way they do today, with an email confirmation and password from the BrowserID service.
With ID provider support, users will have a better, faster, smoother registration experience.
Give it a spin.
Attention email providers large or small: whether you’re an enterprise, an ISP, a university or institution, you owe it to your users to check out this key new feature of BrowserID. Now it’s easy and incredibly simple for any email provider to become an identity provider for their users.
Try out our demo ID provider at eyedee.me and your @eyedee.me address on any BrowserID site. Take a look at our code and documentation. Let us know what you think via our mailing list, IRC channel, or via the Twitter hashtag #browserid. [Less]
Tagged as
cheapid
Clipperz Community Edition
jwcrypto
Libravatar
OpenLDAP