58
edits
Changes
no edit summary
{{FeatureTeam}}
{{FeaturePageBody
|Feature open issues and risks=* Do we provide our own Activity Stream server?
* How is caching handled?
|Feature overview=It's helpful to be able to control your site-based communications from a single location and allow different sites to access the activities from other sites.
This feature will provide a way to read from user's various activity streams. Posting (posting is already covered by F1, although small modifications may be required to make the two features work well together). For reading, it It will provide an API much like F1, adding options for filtering by source site, destination site, author, recipients, content type, priority, time, tags, and possibly others.
While the intended use of this feature will primarily be application-to-application, it will also trivially allow for a centralized, multi-channel "inbox" of a user's various activity streams (although significant UX work will need to be done to complete this feature if it is desired, as centralized inboxes and aggregators have consistently failed in the market).
The site-based prefs will be implemented in content at an about page (<code>about:streams</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 notesplan=* no implementation yet.Define API* should build off of F1 for communication with social servicesBuild mediator* Build caching protocol* Build our server
}}
{{FeatureInfo
