







We want users to have access to their data, in particular the data that forms their web-browsing context (bookmarks, tabs, web apps, passwords, etc.) from all of their devices. This data should be tied to their identity, so that logging into a device is sufficient to connect to all the services the user has previously set up, whether those services are provided by Mozilla or third parties. These are Identity-Attached Services, which, as a whole, we're code-naming PICL (Profile In the Cloud).
Identity/Firefox Accounts - MozillaWiki
Mozilla Accounts (formerly Firefox Accounts) is the account system for users to access hosted services provided by Mozilla.
Identity - MozillaWiki
For the latest status on identity-related projects, see the CloudServices page.
Identity/Roadmap - MozillaWiki
Keeping Data Private | Web Browser Engineering
Our browser has grown up and now runs (small) web applications. With one final step—user identity via cookies—it will be able to run all sorts of personalized online services. But capability demands responsibility: our browser must now secure cookies against adversaries interested in stealing them. Luckily, browsers have sophisticated systems for controlling access to cookies and preventing their misuse.
Open Social Web ID - in commons
Approaching a shared method of single sign-on for the entire open social web.
Transitioning Legacy Sync users to Firefox Accounts
It has been almost a year since the release of Firefox Accounts and the new Firefox Sync service, and the response from users has been ...

Portable Identity for ActivityPub
It is actually possible. And it's not as complicated as you might think.

Lightbeam - Illuminating Online Tracking
Lightbeam - Illuminating Online Tracking
Four "Digital Identity" lessons every Web3 builder should know - blog.boscolo.co
This article was originally published on Mirror.xyz May 17, 2022
@Rich_Harris @tcurdt @huntabyte I think auth should be handled by a middleware. The framework gets signed request headers injected by this middleware, which gives it all the info (userid, role, username, picture) it needs. Sandstorm by @KentonVarda uses this approach: https:/
I think auth should be handled by a middleware. The framework gets signed request headers injected by this middleware, which gives it all the info (userid, role, username, picture) it needs.Sandstorm by @KentonVarda uses this approach: https://t.co/xCk1KRIgcw— Nilesh Trivedi (@nileshtrivedi) February 21, 2023
Introducing Firefox Send, Providing Free File Transfers while Keeping your Personal Information Private | The Mozilla Blog
At Mozilla, we are always committed to people’s security and privacy. It’s part of our long-standing Mozilla Manifesto. We are continually looking for

Digital Credentials · Issue #1003 · mozilla/standards-positions
Request for Mozilla Position on an Emerging Web Specification Specification title: Digital Credentials Specification or proposal URL (if available): https://wicg.github.io/digital-identities/ Expla...