58
edits
Labs/PAC/Contacts: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 12: | Line 12: | ||
This feature will provide such a repository and access point. Through interaction with a user's activity streams manager (Delta), the Contact Manager will also be able to know which of a user's contacts are already on sites which are requesting access to the graph, and only let the site know the relevant pieces of their social graph. | This feature will provide such a repository and access point. Through interaction with a user's activity streams manager (Delta), the Contact Manager will also be able to know which of a user's contacts are already on sites which are requesting access to the graph, and only let the site know the relevant pieces of their social graph. | ||
|Feature users and use cases | |Feature users and use cases=* Provide a centralized access point for a user's contacts across various sites | ||
* Empower users to control sites' knowledge of their social graph | * Empower users to control sites' knowledge of their social graph | ||
* Through increased control, sites will gain increased user trust, and this in turn will promote social activity to permeate apps and the web | * Through increased control, sites will gain increased user trust, and this in turn will promote social activity to permeate apps and the web | ||
|Feature dependencies=* Revive the old Contacts add-on | |||
* Merge with F1's current contacts backend | |||
* Delta (for scoping return values) | |||
|Feature requirements=* Define API | |||
* Storage server | |||
* Support for friend, follow, and private profile follow models | |||
|Feature ux design=* coming soon | |Feature ux design=* coming soon | ||