Labs/PAC/Psync: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 7: Line 7:
{{FeatureTeam}}
{{FeatureTeam}}
{{FeaturePageBody
{{FeaturePageBody
|Feature overview=It's helpful to be able to control your online identity from a central, secure location. By offering Mozilla users a Profile Server, they can take control of their online presence, licensing different aspects of their identity to different sites as they see fit through a single UI.
|Feature overview=It's helpful to be able to control your online identity from a central, secure location. By offering Mozilla users a Profile Mediator, they can take control of their online presence, licensing different aspects of their identity to different sites as they see fit through a single UI.


This feature will provide such a repository, storing basic profile information such as name, picture, bio, online accounts, and more. In addition to the core aspects of their profile which can be managed through this feature, the profile server will also house pointers to a user's various activity streams, contacts, sync data, installed apps, installed add ons, and other firefox preferences.
This feature will provide such an access point, allowing sites to request basic profile information such as name, picture, bio, online accounts, and more.
|Feature users and use cases=* Provide a centralized personal identity repository
 
We will likely want to provide our own example Profile Server, which in addition to the core aspects of their profile will also house pointers to a user's various activity streams, contacts, sync data, installed apps, installed add ons, and other firefox preferences.
|Feature users and use cases=* Provide a centralized personal identity access point for users and apps
* Empower users to define personal information sharing relationships with various sites
* Empower users to define personal information sharing relationships with various sites
* Provide a secure, non-spoofable way to set these access preferences
* Provide a secure, non-spoofable way to set these access preferences
* Assure users of the security of their personal data
* Assure users of the security of their personal data
|Feature dependencies=* Extend Sync?
|Feature dependencies=* Extend Sync for our own implementation?
* Build off of [[Privacy/Features/Site-based_data_management_UI|Site-based data mangement]]
* Build off of [[Privacy/Features/Site-based_data_management_UI|Site-based data mangement]]
|Feature requirements=* Refine a good set of profile data to store
|Feature requirements=* Refine a good set of profile data to store
* Figure out a licensing structure
* Figure out a licensing structure
* Figure out an API
|Feature functional spec=profile.get(field[, onsuccess, onfailure])
profile.set(field, value[, onsuccess, onfailure])
|Feature ux design=* coming soon
|Feature ux design=* coming soon


The site-based prefs will be implemented in content at an about page (<code>about:profile</code>).  It will be in-content (much like [about:addons]), and is intended to build off of the mechanisms of the [[Privacy/Features/Site-based_data_management_UI|Site-based data management UI]] as appropriate.
The site-based prefs will be implemented in content at an about page (<code>about:profile</code>).  It will be in-content (much like [about:addons]), and is intended to build off of the mechanisms of the [[Privacy/Features/Site-based_data_management_UI|Site-based data management UI]] as appropriate.
|Feature implementation notes=* no implementation yet.
|Feature implementation plan=* Refine the API
* should build off of Sync?
* Build the mediator
* Build our server/service provider
}}
}}
{{FeatureInfo
{{FeatureInfo
58

edits