Document and content feed

BACKGROUND

Information workers/users have become accustomed to generating, editing and receiving large numbers of electronic documents and other information (e.g., electronic communications, images, data, etc.). In a given enterprise situation, for example, a company, school, social network, etc., a given information worker/user may encounter hundreds (or more) of documents or other content items, each with varying degrees of relevance or importance to the information worker. For example, the information worker may generate a document for a rush work project that may be of the highest relevance at the time of the project. For another example, the information worker may receive a document generated by his/her manager that similarly is of very high relevance to the information worker. On the other hand, he/she may receive a document or may have access to a document or other information via his/her enterprise dealing with a project he/she is no longer involved with, and thus, the document may be of low relevance or importance to the information worker. The typical information worker/user needs to know about those documents or other content or information items that are relevant, important or interesting to him/her, but he/she does not necessarily need to have all documents and/or other content items surfaced to him/her regardless of their relevance. Thus, a need exists for methods, systems, and articles of manufacture for surfacing documents and other information to a given user that might be important to the user without surfacing to the user documents or other information that are not particularly interesting or relevant to the user. It is with respect to these and other considerations that the present invention has been made.

SUMMARY

This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended as an aid in determining the scope of the claimed subject matter.

Embodiments of the present invention solve the above and other problems by providing a document and content feed that surfaces to a user documents and other information items that are determined to be interesting or relevant to the user. Surfaced documents and other information may be displayed in an information feed that may be updated each time the feed is accessed by the user. Information not surfaced to the user in the feed may be accessed by the user via one or more other means, but only those items having a sufficient relevance to the user are surfaced in the feed.

According to embodiments, each user in a given enterprise has his/her own information feed. The feed is a sequence of items like documents, electronic mail items, images, other communications items and the like that are determined to be of sufficient interest or relevance to the user. The user may access the information feed through different front end applications operable for accessing the feed and for displaying its information to the user. When a user accesses his/her feed, a set of new items may be added to the feed based on their determined interest or relevance to the user. Such new items include information that an underlying ranking algorithm determines currently are the most interesting or relevant to the user and that are not currently included in the user's information feed. The new items that are added to the information feed are sorted in the feed based on a determined probability that they are interesting or relevant to the user.

When an item has been added to the information feed and is seen by the user, it will stay in the user's information feed at the same position in a persistent manner unless manually removed by the user. According to one embodiment, information items contained in the feed may be reposted to a different ordering position in the feed if their importance/relevance to the user changes significantly. That is, an item that is reposted may be moved to a different location in the feed as required based on a newly determined interest or relevance to the user.

The details of one or more embodiments are set forth in the accompanying drawings and description below. Other features and advantages will be apparent from a reading of the following detailed description and a review of the associated drawings. It is to be understood that the following detailed description is explanatory only and is not restrictive of the invention as claimed.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings which are incorporated in and constitute a part of this disclosure, illustrate various embodiments of the present invention.

<figref idref="DRAWINGS">FIG. 1</figref> illustrates an information feed showing a number of information items surfaced to a user.

<figref idref="DRAWINGS">FIG. 2</figref> illustrates a system for surfacing information to a user in an information feed.

<figref idref="DRAWINGS">FIG. 3</figref> illustrates one system for determining interest or relevance of an information item for surfacing the information item in an information feed.

<figref idref="DRAWINGS">FIG. 4</figref> illustrates a system for gathering and aggregating information across a variety of information sources that may be surfaced in an information feed.

<figref idref="DRAWINGS">FIGS. 5A through 5F</figref> illustrate information items of varying relevance to a user surfaced in an information feed for the user.

<figref idref="DRAWINGS">FIG. 6</figref> is a flow chart illustrating a method for surfacing information to a user in an information feed.

<figref idref="DRAWINGS">FIG. 7</figref> is a block diagram illustrating example physical components of a computing device with which embodiments of the invention may be practiced.

<figref idref="DRAWINGS">FIGS. 8A and 8B</figref> are simplified block diagrams illustrating components of a mobile computing device with which embodiments of the invention may be practiced.

<figref idref="DRAWINGS">FIG. 9</figref> is a simplified block diagram of a distributed computing system in which embodiments of the invention may be practiced.

DETAILED DESCRIPTION

The following detailed description refers to the accompanying drawings. Wherever possible, the same reference numbers are used in the drawing and the following description to refer to the same or similar elements. While embodiments of the invention may be described, modifications, adaptations, and other implementations are possible. For example, substitutions, additions, or modifications may be made to the elements illustrated in the drawings, and the methods described herein may be modified by substituting, reordering, or adding stages to the disclosed methods. Accordingly, the following detailed description does not limit the invention, but instead, the proper scope of the invention is defined by the appended claims.

<figref idref="DRAWINGS">FIG. 1</figref> illustrates an information feed showing a number of information items surfaced to a user. As illustrated in <figref idref="DRAWINGS">FIG. 1</figref>, a number of documents or other information items <b>110</b>, <b>115</b>, <b>120</b>, <b>125</b>, <b>130</b>, <b>135</b> are displayed in an information feed <b>105</b> on the display surface of a computing device <b>100</b>. According to embodiments, while a number of documents are illustrated in <figref idref="DRAWINGS">FIG. 1</figref>, items that may be displayed in the information feed may include any electronic item of sufficient interest or relevance to the user, for example, documents, images, photographs, electronic mail messages, text messages, telephone call messages, and the like. The computing device <b>100</b> illustrated in <figref idref="DRAWINGS">FIG. 1</figref> is a tablet-style computing device, but as should be appreciated, the information feed <b>105</b> may be displayed on a display surface of any suitable computing device such as a desktop computer, laptop computer, tablet-style computer, handheld computing device, mobile telephone, and the like.

The information items illustrated in the information feed <b>105</b> are graphical representations of information items determined to be interesting or relevant to the user. As should be appreciated, and as described below, the information feed <b>105</b> may include many different information items that are updated each time the user accesses the information feed <b>105</b>. According to embodiments, while new information items may be added to the information feed <b>105</b>, those items presently contained in the information feed <b>105</b> are persisted in the feed indefinitely unless they are manually removed by the user at a subsequent time. The individual documents or other information items displayed in the feed <b>105</b> are displayed according to an order of interest, importance or relevance to the user. As new information items are added to the information feed, the new information items may be added to the front or top of the information feed, and the new information items may be displayed in the feed relative to each other according to the interest, importance or relevance to the user. According to embodiments, individual information items may be reposted to different positions in the ordering of displayed information items, and according to one embodiment, individual information items may be manually removed from the information feed by the user, if desired.

The information feed may be provided by a software application containing sufficient computer executable instructions for generating the information feed and for displaying the information items making up the information feed, as illustrated in <figref idref="DRAWINGS">FIG. 1</figref>. The information feed <b>105</b> may be accessed from a variety of different access points. For example, the information feed application may operate as a stand alone application, or may operate as a module of any of a variety of other applications, for example, word processing applications, spreadsheet applications, slide presentation applications, notes taking applications, desktop publishing applications, and the like for allowing a user to access and display his/her information feed, as desired. For example, if a user is operating a word processing application, the information feed application may operate as a module of the word processing application to allow the user to launch the information feed <b>105</b> in a display presentation provided by the word processing application for allowing the user to review those information items that have been added to his/her information feed.

<figref idref="DRAWINGS">FIG. 2</figref> illustrates a system <b>200</b> for surfacing information to a user in an information feed. Information items making up the information feed <b>105</b> for a given user may come from a variety of sources <b>205</b>, <b>210</b>, <b>215</b>. Such information sources may include client side information storage, remote storage (e.g. a remote server, local or remote databases, local or remote shared resources repositories, and the like). For example, a first source <b>205</b> may be a local client side memory containing documents, images, data files, communications items, such as electronic mail items, text messages, telephone messages, and the like. Similarly, the source <b>205</b> may represent a remote cloud-based storage medium that may be accessed by one or more client applications. As should be appreciated, each information type, for example, documents, may be stored in association with applications responsible for generating the information types, for example, word processing applications, spreadsheet applications, slide presentation applications, spreadsheet applications, and the like. Communications messages, for example, electronic mail messages may be associated with an electronic mail application, or an Internet-based mail service.

The second source <b>210</b> may be illustrative of a variety of other information sources that may contain information that may be placed in an information feed <b>105</b> such as social networking sites. For example, the source <b>210</b> may be a remotely based server system containing information of interest or relevant to a given user maintained for a social networking service accessed by the user. The third source <b>215</b> may be illustrative of any other information source from which information items as described herein may be collected and analyzed for their interest or relevance to a given user and for potential surfacing to the user in an information feed <b>105</b>. As should be appreciated, the information sources <b>205</b>, <b>210</b>, <b>215</b> are for purposes of illustration only and are not limiting of the vast numbers of local and networked information sources from which documents and other content and information items may be retrieved for analysis and for inclusion in an information feed <b>105</b>, as described herein.

As will be described in further detail below with reference to <figref idref="DRAWINGS">FIG. 4</figref>, information from the various sources may be retrieved and aggregated for ultimate analysis at the analysis processing engine (APE) <b>220</b>, as illustrated in <figref idref="DRAWINGS">FIG. 2</figref>. That is, after information is retrieved and aggregated from the various information sources, the information may be passed to the analysis processing engine <b>220</b> for a determination of the importance or relevance of each information item to a given user for possible inclusion in the user's individualized information feed <b>105</b>. That is, as will be described below, each information feed <b>105</b> is analyzed with respect to each individual user so that the information items surfaced to the user in his/her personalized information feed <b>105</b> will be those items that are determined to be interesting, important or relevant to the individual user. A more detailed discussion of the analysis of individual information items for possible inclusion in the information feed <b>105</b> is provided below with reference to <figref idref="DRAWINGS">FIG. 3</figref>.

Referring still to <figref idref="DRAWINGS">FIG. 2</figref>, information items analyzed by the APE <b>220</b> that are determined to be relevant to a particular user may be built into an infeed graph <b>225</b>. Nodes <b>227</b>, <b>230</b>, <b>235</b>, <b>240</b> of the infeed graph may represent different persons/users and may represent relations between the users in the form of edges where the edges may be representative of documents or other information items that form relationships between the users. For example, if a given document is created by one user, and is edited by another user, then two nodes of the infeed graph may represent the two users, and the document that is generated by a first user and is edited by a second user may be represented by an edge between the two user nodes with which relevance of the document to each user may be determined. As will be described in detail below, such relationships between users and information items may be used for determining the relevance of a given document or information item to a particular user. For example, if a user receives a document that was generated by the user's manager, the relationship between the user and his manager may be used for determining that the document generated by the manager for review by his/her direct report may be used for determining that the document is of high relevance to the direct report and is a good candidate for inclusion in an information feed <b>105</b> for the direct report.

Referring still to <figref idref="DRAWINGS">FIG. 2</figref>, after an infeed graph is generated for a particular user by analysis of various documents and other information sources, the infeed graph may be stored in a graph index <b>245</b> from which documents having sufficiently high rankings/scores as feed candidates may be pulled for generating an information feed <b>105</b>. As should be appreciated, the graph index <b>245</b> may be illustrative of an index that points to storage locations where each item that will populate the feed <b>105</b> are located, or the graph index <b>245</b> may be illustrative of a storage location at which each item that will populate the feed <b>105</b> may be stored after being identified for inclusion in the feed <b>105</b>.

As should be appreciated, the process of retrieving information from various information sources, analysis of the information, building an infeed graph for a particular user, and storing the graph in the graph index <b>245</b> is an iterative process that is updated as new information sources become available. That is, as will be described below, when an individual user accesses his/her information feed <b>105</b> his information feed <b>105</b> will be comprised of those documents or other information items having sufficient ranking for inclusion in the feed <b>105</b> at the time of access to the feed. Upon a subsequent access to the information feed, documents or other information items that have been subsequently added to the infeed graph through analysis of additional documents or other information may be added to the feed <b>105</b>.

Referring still to <figref idref="DRAWINGS">FIG. 2</figref>, the feed application <b>255</b> is an application operable for extracting the documents or other information items from the graph index <b>245</b> for generating the information feed <b>105</b> and for displaying the documents or other information items comprising the present instance of the information feed <b>105</b> in a user interface, as illustrated above with reference to <figref idref="DRAWINGS">FIG. 1</figref>. The feed access applications <b>250</b>, <b>260</b> are illustrative of one or more applications that may be operable for accessing the functionality of the feed application <b>255</b>. As described above with reference to <figref idref="DRAWINGS">FIG. 1</figref>, functionality for accessing the feed application <b>255</b> may be operated as a software module of other applications, for example, word processing applications, spreadsheet applications, slide presentation applications, and the like such that a user may access and display his/her information feed <b>105</b> from any of these types of software applications. Alternatively, the feed application <b>255</b> may operate as a stand alone application for creating and displaying a given information feed <b>105</b>.

According to embodiments, the components of the system <b>200</b> illustrated in <figref idref="DRAWINGS">FIG. 2</figref> for generating and displaying an information feed <b>105</b> may operate as a collection of software modules and data sources operating at a single client side computing device, or components of the system <b>200</b> may operate at locations remote to each other such that the system <b>200</b> is operated over a distributed computing network, such as the Internet. For example, the information sources <b>205</b>, <b>210</b>, <b>215</b> may be maintained at various local or remote memory storage areas, the APE <b>220</b> may operate at a location remote from the graph index <b>245</b>, and the feed application <b>255</b> and the various feed access applications <b>250</b>, <b>260</b> may operate as client side applications or as remotely housed applications accessible at a client computing device.

As described above with reference to <figref idref="DRAWINGS">FIGS. 1 and 2</figref>, documents and other information items that may be included in a particular user's information feed <b>105</b> are analyzed to determine their importance or relevance to a particular user. As will be described below, each document or other information item, when analyzed, is provided with a ranking or score, for example, on a scale of zero to one, and the ranking or score is used for deciding the top X number of documents or other information items that may be used for generating a given instance of the information feed <b>105</b>. According to one embodiment, all items having a score at or above a given threshold (e.g., a threshold score of 0.7) may be added to the feed <b>105</b>. As will be described below with reference to <figref idref="DRAWINGS">FIGS. 5A through 5F</figref>, when the information feed <b>105</b> is generated, the documents or other information items contained in the information feed may be ordered based on the rankings or scores determined for each document or information item. For example, a document receiving a score/ranking of 0.90 may be ordered first, a document receiving a score/ranking of 0.80 may be ordered second, a document receiving a score/ranking of 0.70 may be ordered next, and so on. The number of documents or other information items that may be included in an initial instance of the information feed <b>105</b> may be a top X scored or ranked items, for example, the top ten scored or ranked items. As will be described below, each time a user accesses his/her information feed, a next top X number of newly analyzed documents or information items may be added to the information feed based on their scores or rankings.

As described above, information items that may be analyzed for possible inclusion in an information feed <b>105</b> may include documents, images, electronic communications, datasets, and the like. When analyzing an individual information item for ranking or scoring the individual information item for possible inclusion in the information feed, various attributes of an information item and relationships between people associated with the information item may be used for determining a particular ranking or score for the information item. Factors that may be used for ranking or scoring an individual item may include whether the document is generated by the user for which the information feed is being created. Other factors include whether the document has been viewed by colleagues of the user for which the information feed is being generated and which colleagues have viewed the document. For example, scoring/ranking may be different depending on whether a colleague is the user's manager, direct report, peer, or is unrelated to the user according to any particular enterprise structure.

Other scoring/ranking factors include a number of times the given information item has been viewed by one or more persons, and the frequency of viewings of the information item. Other factors include whether the information item has been sent to the user for which the feed is being generated and, if so, by whom. Other factors include an analysis of topics included in a given information item. For example, text strings from a document or other information item may be extracted and may be compared against text strings contained in other documents or information items already contained in the information feed <b>105</b> for the user, or contained in or associated with other documents that have been previously ranked or scored sufficiently for inclusion in an information feed <b>105</b>. Additional information that may be utilized for determining a scoring or ranking for a given information item may include social interaction with the information item. For example, information showing that a given information item has been commented on, liked, viewed, or otherwise utilized in a social network may be utilized in determining a scoring or ranking for a given information item.

According to an embodiment, back-end or client side ranking modules may at frequent, regular intervals monitor activities in a given enterprise including a monitoring of various information items generated, received by or sent from the enterprise for determining a set of information items that should be added to the information feed <b>105</b> of a given user when the user next accesses the information feed. Referring now to <figref idref="DRAWINGS">FIG. 3</figref>, one embodiment of a back-end or client side ranking module or system <b>300</b> is illustrated. The system <b>300</b> is illustrated as operating as a part of the analysis processing engine <b>220</b>, illustrated in <figref idref="DRAWINGS">FIG. 2</figref>. As should be appreciated, however, the ranking system <b>300</b> may be operated remotely from the APE <b>220</b>, and the results of the system <b>300</b> may be passed to or commanded by the APE <b>220</b>, as required.

Referring still to <figref idref="DRAWINGS">FIG. 3</figref>, the PIMC module <b>310</b> is illustrative of those documents or information items that are “popular in my circle” (PIMC). According to embodiments, the module <b>310</b> is a ranking module which estimates importance of documents or other information items based on how popular each document or information item is among the colleagues of the user or other persons associated with the user in any other manner. For example, a document from the user's manager may receive a higher score/ranking than a document from the user's direct report or peer.

The vanity module <b>315</b> is a ranking module which estimates the importance of the user's own documents or information items based on the number of recent views, edits or other interactions of the user with a given document or information item. For example, a document the user views every day, for example, a department spreadsheet may receive a higher ranking than a document the user views once per quarter.

The other module <b>320</b> is a ranking module which estimates the importance of each document or information item based on some other factor, for example, whether the document or information item is part of a collaborative work group with which the user is associated and/or statistical information associated with the document or other information item, for example, how often the document is viewed, or otherwise utilized by members of the user's collaborative work group. As should be appreciated, any number of ranking modules may be utilized for assisting in the generation of a ranking or scoring for a given document or information item, as described herein.

Referring still to <figref idref="DRAWINGS">FIG. 3</figref>, after each of the ranking modules <b>310</b>, <b>315</b>, <b>320</b> provide a ranking or scoring for each document or other information item, the rankings or scorings of each of those modules with respect to each document or other information item may be passed to a feed manager which may generate an overall ranking or score for each document or information item that may be placed in an infeed graph <b>225</b> and that may be ultimately stored in the graph index <b>245</b> for retrieval and population into an information feed <b>105</b>. For example, the feed manager may simply average the scores or rankings provided by each of the ranking modules <b>310</b>, <b>315</b>, <b>320</b>, or the feed manager may be tuned to place more emphasis on the ranking/score of any individual ranking module. For example, a given composite ranking or score for a document or other information item may be comprised of 50% of the score from the module <b>310</b>, 25% of the score from the module <b>315</b> and 25% of the score from the module <b>320</b>.

As should be appreciated, this example is for purposes of illustration only as the portions of the given rankings or scores from any individual module may be modified from time to time in order to generate an information feed <b>105</b> that is most relevant for a given user or class of users. For example, in a given enterprise, it may be determined that the scoring associated with the importance of a document based on its popularity among the colleagues of a given user is more valuable than the scoring associated with a document based on its viewing by the user for which the information feed is being generated.

According to one embodiment, the system <b>300</b> is comprised of only the PIMC module <b>310</b> and the vanity module <b>315</b> for providing scorings or rankings to the feed manager <b>325</b> for generating the infeed graph <b>225</b>. According to this embodiment, the PIMC analysis may continue to calculate a top X candidates (e.g., top 100 documents per user). These should be added as edges to the graph <b>225</b> and should be given to the Feed Manager as a list of candidates for the feed <b>105</b>. The Vanity analysis may look at all documents or other information items created or modified by the user, and it may create a list of the items (e.g., list of 5 documents) with a highest event rate (i.e., access and/or use by the user).

According to this embodiment, each time the Feed Manager <b>325</b> is run, it creates a new “Future” for the user. As described more below, the “Future” includes one or more information items that may be added to the information feed <b>105</b> when the user next accesses it. The algorithm below describes how the Feed Manager creates the “Future” based on the two categories of items that are available according to this embodiment: PIMC and Vanity. As should be appreciated, the algorithm set out below is only one example operation of the Feed Manager and is for purposes of illustration only.

First, the Feed Manager creates an initial list of documents or other information items to post to the feed graph. Next, the Feed Manager reviews a top X items (e.g., top 40) of the PIMC list and adds to the list any of these items that are not in the “Past” (“Past” being items already added to the feed <b>105</b> previously). Next, the Feed Manager reviews a top X items (e.g., top 5) of the Vanity list and adds to the list any of these which are not in the “Past.” If the user does not have as many as the top X Vanity list items with activity the last X days (e.g., last 14 days), the list may be reduced accordingly. According to one embodiment, any of the top 2 items in the Vanity list which is in the “Past,” but not in the top 20 also may be added to the list.

According to the present example operation, the Feed Manager may require at least k (with default value of 8) new documents or other information items per week up to a maximum of D_max(also with default value of 8) items. To do this, the Feed Manager may check how long ago the last item was added to the feed. Assuming T hours since the last item was added, the Feed Manager may calculate the number

<maths id="MATH-US-00001" num="00001"><math overflow="scroll"><mrow><mi>D</mi><mo>=</mo><mrow><mrow><mi>min</mi><mo>⁡</mo><mrow><mo>(</mo><mrow><mrow><mo>⌊</mo><mrow><mfrac><mi>τ</mi><mrow><mn>24</mn><mo>*</mo><mn>7</mn></mrow></mfrac><mo>⁢</mo><mi>k</mi></mrow><mo>⌋</mo></mrow><mo>,</mo><msub><mi>D</mi><mi>max</mi></msub></mrow><mo>)</mo></mrow></mrow><mo>.</mo></mrow></mrow></math></maths>&lt;br /&gt; If the number of documents in the list to post is less than D, the Feed Manager may traverse the PIMC list beyond position of the top X items reviewed from the PIMC (e.g., beyond 40 items). It may then add items not yet in the “Past” until the total count of the post list reaches D.

Continuing with the present example, the list of documents or other items to post to the feed is now ready, and is separated into two categories: PIMC items and Vanity items. Within each of the categories, the list is sorted by relevance score. The following algorithm may be used for merging the category lists. Assume there are p PIMC items and v Vanity items. Generate a random variable r between 0 and 1. If r&lt;p/(p+v), post the best PIMC item on top. Otherwise, post the best Vanity item on top. Update the values of p and v, create a new random variable, and repeat until all items are posted. The random variables must be chosen so that for the same lists of documents, the posting order is the same each time the Feed Manager runs. For example, this may be obtained by using an identification number/code (e.g., “docid”) for the first PIMC item as the seed for the random variable.

According to this embodiment, the PIMC cutoff of X items (e.g., 40 items) and the Vanity cutoff of X items (e.g., 5 items) may be modified from time to time to change the nature of the items being added to the feed <b>105</b>. Lower numbers may improve precision, but may result in too few items being added to the feed <b>105</b>. Likewise, higher numbers may allow too many items to be added to the feed, and some of such items may not be particularly interesting or important to the user for which the feed is being generated. In addition, more items categories, for example, the other category/module <b>320</b>, illustrated in <figref idref="DRAWINGS">FIG. 3</figref>, and a similar analysis of those items may be performed for considering those items for inclusion in the feed <b>105</b>.

As briefly described above, with reference to <figref idref="DRAWINGS">FIG. 2</figref>, as information is gathered from the various sources <b>205</b>, <b>210</b>, <b>215</b> for presentation to a ranking system <b>300</b> as part of the analysis processing engine <b>220</b>, the information may be aggregated, and determinations of such information as the number of viewings of a given user for a given document or information item, the popularity of a given document or information item among colleagues of a user, comments or interactions with a document or information item via social networks, and the like may be determined. Such information for each document or information item may be aggregated for use by the ranking systems <b>300</b> as part of the analysis and processing engine <b>220</b>, as described above with reference to <figref idref="DRAWINGS">FIG. 3</figref>.

<figref idref="DRAWINGS">FIG. 4</figref> is a block diagram illustrating a system architecture <b>400</b> for aggregating information items and for providing an activity stream across multiple information sources that may be built into a knowledge graph from which information items may be pulled by the system <b>300</b> for analysis and potential inclusion in the feed <b>105</b>, as discussed above. According to embodiments, the system <b>400</b> may lie between the information sources <b>205</b>, <b>210</b>, <b>215</b> and the APE <b>220</b> for gathering information on various information items needed by the APE for feed analysis and generation. The system architecture <b>400</b> includes an aggregator <b>408</b> operable to collect activity data <b>404</b>, <b>405</b>, <b>406</b> for an individual <b>402</b> or group of individuals from a plurality of information sources <b>205</b>, <b>210</b>, <b>215</b> and store the activity data in a graph <b>414</b>. The information sources may include any number of sources from which items may be pulled as feed candidates, as described above with reference to <figref idref="DRAWINGS">FIG. 2</figref>.

Activity data <b>404</b>, <b>405</b>, <b>406</b> may comprise various types of information such as, but not limited to, presence data, data associated with authoring or modification of an information item (e.g., document), trending data, feedback data (e.g., like, comment, follow, share, etc.), data associated with organizational structure (e.g., who an individual works with, works for, interacts with, is a peer to, directs, manages, is managed by, has in common with another individual, etc.). As mentioned above, the activity data may be stored in a graph <b>414</b>. Actions may be stored as edges <b>412</b>A-H (collectively <b>412</b>), and entities that are acted upon may be stored as nodes <b>410</b>A-G (collectively <b>410</b>). For example, a node <b>410</b> may include an individual <b>402</b> (nodes <b>410</b>A,B,E,F), a group of individuals, a document (node <b>410</b>C), an email or other communication type (node <b>410</b>D), a webpage (node <b>410</b>G), etc. An edge <b>412</b> may include various types of actions (e.g., like, comment, follow, share, authoring, modifying, organizational relationship, communication, participation, etc.). Consider for example that an individual <b>402</b> “likes” a certain document (i.e., selects a “like” option associated with the document). The individual and the document may be stored as nodes <b>410</b> and the “like” selection may be stored as an edge <b>412</b>.

The APE <b>220</b> may view/retrieve enterprise activity for an individual <b>402</b> or group. According to embodiments, a group may be a formalized set of individuals according to an organizational hierarchy or project structure, or may be a less formally coupled set of individuals such as a group of individuals who are common attendees of a particular meeting, a project group, a group of individuals who share a common interest in a particular topic, etc. An individual <b>402</b> may be a part of a plurality of groups. As illustrated in <figref idref="DRAWINGS">FIG. 4</figref>, the APE <b>220</b> may request an activity stream <b>416</b> for retrieving information items and for categorizing information items (e.g., PIMC or Vanity) as described above. According to one embodiment, a request may be triggered by the Feed Manager <b>325</b> in an iterative process for analyzing new candidates from the various information sources <b>205</b>, <b>210</b>, <b>215</b> for inclusion in the feed <b>105</b>.

As described above with reference to <figref idref="DRAWINGS">FIGS. 1 through 4</figref>, when a user accesses the information feed <b>105</b> either as a first access of the information feed <b>105</b>, or as a subsequent access of the information feed, the information feed <b>105</b> is built by placing those documents and/or information items in the information feed in the order of the ranking or scoring that has been applied to each document. The resulting information feed is stored in the graph index <b>245</b>, and is retrieved by the feed application <b>255</b> upon command for presenting the documents in an information feed user interface, as illustrated in <figref idref="DRAWINGS">FIG. 1</figref>. <figref idref="DRAWINGS">FIGS. 5A through 5F</figref> illustrate information items of varying importance or relevance to a user surfaced in an information feed for the user. As described above, each user has an individual information feed <b>105</b>, and the information feed <b>105</b> is a stream of information items that has been important to the user at some point and that has been ranked for inclusion in the information feed, as described above. The user's information feed <b>105</b> is updated when, and only when, the user opens or refreshes the feed in a user interface, as illustrated above with reference to <figref idref="DRAWINGS">FIG. 1</figref>. Once an information item is added to the user's feed, it stays in the user's feed persistently, unless the user manually removes the item from the information feed, as described below. Alternatively, the information feed may have a fixed upper limit S to its size, so that an item may be removed from the feed when there are S items before it in the feed. The feed is ordered, and the order never changes (with some exceptions, as described below).

Referring now to <figref idref="DRAWINGS">FIG. 5A</figref>, an instance of an information feed <b>105</b> is illustrated containing information items <b>505</b>, <b>510</b>, <b>515</b>, <b>520</b>, <b>525</b>. As illustrated, each of the information items are displayed in the information feed according to a ranking/scoring applied to each individual item. For example, item A has a score or ranking of 0.9 and thus is in a first position in the information feed, whereas item E has the lowest score of the grouping of information items with a score of 0.77 and is placed at the end of the string of information items. According to one embodiment, the first time a user opens the information feed illustrated in <figref idref="DRAWINGS">FIG. 5A</figref>, the top X ranked items (e.g., top ten items) are surfaced in the information feed and are sorted according to the scoring or ranking, as illustrated in <figref idref="DRAWINGS">FIG. 5A</figref>.

Referring now to <figref idref="DRAWINGS">FIG. 5B</figref>, the next time the user opens the information feed, additional documents or information items <b>530</b>, <b>535</b>, <b>540</b> are added to the information feed where those additional information items were analyzed by the APE <b>220</b> and received scorings or rankings sufficiently high enough for inclusion in the information feed <b>105</b>. For example, the information item H received a score of 0.91, the item I received a score of 0.88, and the item J received a score of 0.81. Thus, the information feed presented to the user as illustrated in <figref idref="DRAWINGS">FIG. 5B</figref> now contains the new information items added to the top or front of the feed in importance or relevance order based on scores or rankings applied to each of the new items.

Referring still to <figref idref="DRAWINGS">FIG. 5B</figref>, note that the scores for some of the information items are different from the scores for the same items as illustrated in <figref idref="DRAWINGS">FIG. 5A</figref>. That is, item B (<b>510</b>) had a score of 0.85 in the first instance of the feed illustrated in <figref idref="DRAWINGS">FIG. 5A</figref>, but has a score of 0.89 in the second instance of the feed illustrated in <figref idref="DRAWINGS">FIG. 5B</figref>. Likewise, item A (<b>505</b>) had a score of 0.9 in the first instance of the feed but has a score of 0.75 in the second instance of the feed, illustrated in <figref idref="DRAWINGS">FIG. 5B</figref>. According to one embodiment, once the documents or other information items are surfaced in the information feed according to a particular order, the order is maintained even if the scoring or rankings for individual items change with each subsequent access to the information feed. That is, when the second instance of the information feed is generated as illustrated in <figref idref="DRAWINGS">FIG. 5B</figref>, the scores of some of the previously surfaced documents or information items may change when ranked in association with new documents or information items <b>530</b>, <b>535</b>, <b>540</b> added to the information feed.

In order to avoid confusing the user as to the nature of the documents or other information items contained in his/her information feed, the displayed ordering of the documents or information items is maintained with each subsequent instance of the information feed, with exceptions described below. That is, the first five documents or information items A-E are maintained in the same relative order with each instance of the information feed, and new items, for example, items H, I, J are surfaced in order of their rankings or scorings, and the orderings of the two sets of documents or information items relative to each other will be maintained in subsequent instances of the information feed.

Referring now to <figref idref="DRAWINGS">FIG. 5C</figref>, each consecutive time the user opens the information feed, new documents may be added to the feed. However, the number of documents or information items is not a fixed number. It depends on the availability of new documents or other content items for the user and on any personalized settings applied to the feed by the user, for example, a total number of documents or information items that may be surfaced in the user's feed according to the user's desire, or a bottom threshold ranking or score for a document or content item that may be surfaced in the information feed, and the like. However, referring to <figref idref="DRAWINGS">FIG. 5C</figref>, as should be appreciated, even if no new documents or information items are received by the APE <b>220</b>, new documents or information items may nonetheless be added to the information feed by selecting documents or information items previously analyzed that did not have sufficient scores or rankings for inclusion in the information feed but that now may be added if the scoring or ranking for those documents relative to other documents or information items that have been added to the information feed changes the determination of the importance of those documents or information items to the overall feed.

Notwithstanding, a lower scoring or ranking boundary may be applied to prevent including items in the information feed that clearly are not relevant enough for inclusion in the user's feed. As illustrated in <figref idref="DRAWINGS">FIG. 5C</figref>, two additional information items <b>545</b>, <b>550</b> have been added in order to provide new information to the information feed, but as illustrated in <figref idref="DRAWINGS">FIG. 5C</figref>, the scoring or rankings for the information items may be relatively low compared to the scorings or rankings of other information items, but are added to ensure the feed is updated when the user accesses the feed. As should be appreciated, when the user refreshes the feed application <b>255</b>, new documents or information items may be added in the same way as if the user reopens the application to generate a new instance of the information feed <b>105</b>.

Referring now to <figref idref="DRAWINGS">FIG. 5D</figref>, according to one embodiment, when a user opens the feed application <b>255</b>, or refreshes the feed application <b>255</b>, information items may be reposted to a different location in the information feed if the scoring or ranking for one or more information items has increased or decreased significantly relative to other items in the information feed or relative to new items being added to the information feed. As illustrated in <figref idref="DRAWINGS">FIG. 5D</figref>, information item B (<b>510</b>) has received a new scoring or ranking of 0.93 relative to each of the information items contained in this instance of the information feed, and therefore, according to this embodiment, item B may be reposted to the top or front of the information feed <b>105</b> to a new position <b>555</b>, as illustrated in <figref idref="DRAWINGS">FIG. 5D</figref>. This is an alternative to the previously described embodiment where each item is displayed in the information feed in the same position relative to other items. According to this embodiment, if the scoring or ranking of an individual item grows so significantly that it should be placed in front of other items, or if its importance to the user decreases so significantly relative to other items that it should be moved to a lower position in the information feed, then such changes may be made.

Referring now to <figref idref="DRAWINGS">FIG. 5E</figref>, according to another embodiment, an information item may be manually removed from the information feed by the user upon command. For example, referring to <figref idref="DRAWINGS">FIG. 5</figref>, the user may determine that item L (<b>550</b>) is no longer important to the user notwithstanding a score or ranking applied to the item by the APE <b>220</b>, and thus, the user may decide to manually remove that information item from the information feed. For example, if the information feed illustrated in <figref idref="DRAWINGS">FIG. 5E</figref> is comprised of documents that have been generated as part of the user's collaborative work group, and the document L (<b>550</b>) while receiving a ranking or score sufficient for inclusion in the information feed is no longer important to the user because the subject of the document or information item has been completed or has otherwise been dispensed with by the user's work group, the user may decide to manually remove that document or information item from the information feed in order to make room for additional information items or in order to remove unnecessary information items from his/her feed.

Referring now to <figref idref="DRAWINGS">FIG. 5F</figref>, as discussed above, the APE <b>220</b> and/or feed application <b>225</b> tracks the most recent instance of the feed that has been seen by the user. According to one embodiment, documents or information items contained in an instance of the feed that has been viewed by the user may be referred to as the “Past” <b>575</b>. However, as described above, the APE <b>220</b> is from time to time scoring documents and information items that are being analyzed for inclusion in a future instance of the information feed for when the user next accesses a next instance of the information feed. Those items that have been placed in the graph index <b>245</b> for inclusion in a future instance of the information feed are referred to as the “Future” <b>570</b>. According to one embodiment, as long as documents or information items are characterized as “Future” documents or information items that will be surfaced to the user in a future instance of the information feed, those documents or information items may be changed, including re-ranking or re-scoring those items which may result in removing one or more of those items from the future instance of the information feed <b>105</b>. Once the user actually opens a future instance of the feed <b>105</b> and views new documents or information items, those viewed documents or information items will now be part of the information feed characterized as the “Past” and will stay in the feed unless removed as described above.

Having described an operating environment and various aspects of embodiments of the invention with respect to <figref idref="DRAWINGS">FIGS. 1-5</figref>, <figref idref="DRAWINGS">FIG. 6</figref> is a flow chart illustrating a method for surfacing information to a user in an information feed. The routine <b>600</b> begins at start operation <b>605</b> and proceeds to operation <b>610</b> where documents and information items are retrieved from various information sources <b>205</b>, <b>210</b>, <b>215</b> by the APE <b>220</b> for analysis as candidates for inclusion in a user's information feed <b>105</b>. As described above with reference to <figref idref="DRAWINGS">FIG. 4</figref>, information items retrieved from the various information sources may first be analyzed, and an activity stream may be generated for the information items for assisting in a determination of the importance or relevance of each item to a given user.

At operation <b>615</b>, the ranking or scoring system <b>300</b> operating in association with the APE <b>220</b> scores or ranks each document or information item as feed candidates, as described above with reference to <figref idref="DRAWINGS">FIG. 3</figref>. Documents or information items receiving a scoring or ranking sufficient for inclusion in an information feed <b>105</b> are placed in an infeed graph and are stored in the graph index <b>245</b> for retrieval by the feed application <b>255</b> when a user first or next accesses his information feed <b>105</b>. As should be appreciated, any documents or information items not included in the infeed graph owing to the lack of a sufficient scoring or ranking are not discarded but are maintained for subsequent analysis relative to other items that subsequently may be considered as feed candidates.

At operation <b>620</b>, a user accesses his information feed via the feed application <b>255</b> or via a feed access application <b>250</b>, <b>260</b>, illustrated and described above with reference to <figref idref="DRAWINGS">FIG. 2</figref>. At operation <b>625</b>, the documents or other information items grouped together in the infeed graph <b>225</b> are displayed as an information feed <b>105</b> in an information feed user interface in order of the ranking or scoring applied to each document or information item, as illustrated in <figref idref="DRAWINGS">FIG. 1</figref> and <figref idref="DRAWINGS">FIGS. 5A through 5F</figref>. At operation <b>630</b>, operations <b>610</b> and <b>615</b> may be repeated as additional documents and information items are received by the APE <b>220</b> from the sources <b>205</b>, <b>210</b>, <b>215</b>.

As new items are received and analyzed and scoring or rankings are applied, new instances of the information feed may be generated and the new instances of the information feed will be characterized as “Future” instances of the information feed until accessed by the user. At operation <b>635</b>, a subsequent feed access is received by the user, and at operation <b>640</b>, the “Future” documents or information items are displayed in the feed <b>105</b> in order of ranking/scoring, as illustrated and described above with reference to <figref idref="DRAWINGS">FIG. 5B</figref>.

At operation <b>645</b>, reposting of documents or information items contained in the information feed may be allowed, if one or more documents or information items receives a new scoring or ranking relative to other items sufficient for moving the document or information item to a new location in the information feed <b>105</b>. At operation <b>650</b>, removal of a given document or information item from the information feed may be enabled, if a user determines that a given document or information item is no longer important to the user notwithstanding a scoring or ranking applied to the document or information item sufficient for maintaining it in the information feed. At operation <b>655</b>, changes to items characterized as “Future” items may be enabled, as illustrated and described above with reference to <figref idref="DRAWINGS">FIG. 5F</figref>, if scoring or ranking for such items has changed relative to other items such that maintenance of those items in the information feed as “Future” items is no longer warranted. The routine ends at operation <b>695</b>.

While the invention has been described in the general context of program modules that execute in conjunction with an application program that runs on an operating system on a computer, those skilled in the art will recognize that the invention may also be implemented in combination with other program modules. Generally, program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types.

The embodiments and functionalities described herein may operate via a multitude of computing systems including, without limitation, desktop computer systems, wired and wireless computing systems, mobile computing systems (e.g., mobile telephones, netbooks, tablet or slate type computers, notebook computers, and laptop computers), hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, and mainframe computers.

In addition, the embodiments and functionalities described herein may operate over distributed systems (e.g., cloud-based computing systems), where application functionality, memory, data storage and retrieval and various processing functions may be operated remotely from each other over a distributed computing network, such as the Internet or an intranet. User interfaces and information of various types may be displayed via on-board computing device displays or via remote display units associated with one or more computing devices. For example user interfaces and information of various types may be displayed and interacted with on a wall surface onto which user interfaces and information of various types are projected. Interaction with the multitude of computing systems with which embodiments of the invention may be practiced include, keystroke entry, touch screen entry, voice or other audio entry, gesture entry where an associated computing device is equipped with detection (e.g., camera) functionality for capturing and interpreting user gestures for controlling the functionality of the computing device, and the like.

<figref idref="DRAWINGS">FIGS. 7-9</figref> and the associated descriptions provide a discussion of a variety of operating environments in which embodiments of the invention may be practiced. However, the devices and systems illustrated and discussed with respect to <figref idref="DRAWINGS">FIGS. 7-9</figref> are for purposes of example and illustration and are not limiting of a vast number of computing device configurations that may be utilized for practicing embodiments of the invention, described herein.

<figref idref="DRAWINGS">FIG. 7</figref> is a block diagram illustrating physical components (i.e., hardware) of a computing device <b>700</b> with which embodiments of the invention may be practiced. The computing device components described below may be suitable for the client device <b>118</b> described above. In a basic configuration, the computing device <b>700</b> may include at least one processing unit <b>702</b> and a system memory <b>704</b>. Depending on the configuration and type of computing device, the system memory <b>704</b> may comprise, but is not limited to, volatile storage (e.g., random access memory), non-volatile storage (e.g., read-only memory), flash memory, or any combination of such memories. The system memory <b>704</b> may include an operating system <b>705</b> and one or more program modules <b>706</b> suitable for running software applications <b>750</b> such as the Feed Application <b>255</b> or client application <b>120</b>. The operating system <b>705</b>, for example, may be suitable for controlling the operation of the computing device <b>700</b>. Furthermore, embodiments of the invention may be practiced in conjunction with a graphics library, other operating systems, or any other application program and is not limited to any particular application or system. This basic configuration is illustrated in <figref idref="DRAWINGS">FIG. 7</figref> by those components within a dashed line <b>708</b>. The computing device <b>700</b> may have additional features or functionality. For example, the computing device <b>700</b> may also include additional data storage devices (removable and/or non-removable) such as, for example, magnetic disks, optical disks, or tape. Such additional storage is illustrated in <figref idref="DRAWINGS">FIG. 7</figref> by a removable storage device <b>709</b> and a non-removable storage device <b>710</b>.

As stated above, a number of program modules and data files may be stored in the system memory <b>704</b>. While executing on the processing unit <b>702</b>, the program modules <b>706</b> may perform processes including, but not limited to, one or more of the stages of the method <b>600</b> illustrated in <figref idref="DRAWINGS">FIG. 6</figref>. Other program modules that may be used in accordance with embodiments of the present invention and may include applications such as electronic mail and contacts applications, word processing applications, spreadsheet applications, database applications, slide presentation applications, drawing or computer-aided application programs, etc.

Furthermore, embodiments of the invention may be practiced in an electrical circuit comprising discrete electronic elements, packaged or integrated electronic chips containing logic gates, a circuit utilizing a microprocessor, or on a single chip containing electronic elements or microprocessors. For example, embodiments of the invention may be practiced via a system-on-a-chip (SOC) where each or many of the components illustrated in <figref idref="DRAWINGS">FIG. 7</figref> may be integrated onto a single integrated circuit. Such an SOC device may include one or more processing units, graphics units, communications units, system virtualization units and various application functionality all of which are integrated (or “burned”) onto the chip substrate as a single integrated circuit. When operating via an SOC, the functionality, described herein, with respect to providing an activity stream across multiple workloads may be operated via application-specific logic integrated with other components of the computing device <b>700</b> on the single integrated circuit (chip). Embodiments of the invention may also be practiced using other technologies capable of performing logical operations such as, for example, AND, OR, and NOT, including but not limited to mechanical, optical, fluidic, and quantum technologies. In addition, embodiments of the invention may be practiced within a general purpose computer or in any other circuits or systems.

The computing device <b>700</b> may also have one or more input device(s) <b>712</b> such as a keyboard, a mouse, a pen, a sound input device, a touch input device, etc. The output device(s) <b>714</b> such as a display, speakers, a printer, etc. may also be included. The aforementioned devices are examples and others may be used. The computing device <b>700</b> may include one or more communication connections <b>716</b> allowing communications with other computing devices <b>718</b>. Examples of suitable communication connections <b>716</b> include, but are not limited to, RF transmitter, receiver, and/or transceiver circuitry; universal serial bus (USB), parallel, and/or serial ports.

The term computer readable media as used herein may include computer storage media. Computer storage media may include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, or program modules. The system memory <b>704</b>, the removable storage device <b>709</b>, and the non-removable storage device <b>710</b> are all computer storage media examples (i.e., memory storage.) Computer storage media may include RAM, ROM, electrically erasable read-only memory (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other article of manufacture which can be used to store information and which can be accessed by the computing device <b>700</b>. Any such computer storage media may be part of the computing device <b>700</b>. Computer storage media does not include a carrier wave or other propagated or modulated data signal.

Communication media may be embodied by computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and includes any information delivery media. The term “modulated data signal” may describe a signal that has one or more characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media may include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, radio frequency (RF), infrared, and other wireless media.

<figref idref="DRAWINGS">FIGS. 8A and 8B</figref> illustrate a mobile computing device <b>800</b>, for example, a mobile telephone, a smart phone, a tablet personal computer, a laptop computer, and the like, with which embodiments of the invention may be practiced. With reference to <figref idref="DRAWINGS">FIG. 8A</figref>, one embodiment of a mobile computing device <b>800</b> for implementing the embodiments is illustrated. In a basic configuration, the mobile computing device <b>800</b> is a handheld computer having both input elements and output elements. The mobile computing device <b>800</b> typically includes a display <b>805</b> and one or more input buttons <b>810</b> that allow the user to enter information into the mobile computing device <b>800</b>. The display <b>805</b> of the mobile computing device <b>800</b> may also function as an input device (e.g., a touch screen display). If included, an optional side input element <b>815</b> allows further user input. The side input element <b>815</b> may be a rotary switch, a button, or any other type of manual input element. In alternative embodiments, mobile computing device <b>800</b> may incorporate more or less input elements. For example, the display <b>805</b> may not be a touch screen in some embodiments. In yet another alternative embodiment, the mobile computing device <b>800</b> is a portable phone system, such as a cellular phone. The mobile computing device <b>800</b> may also include an optional keypad <b>835</b>. Optional keypad <b>835</b> may be a physical keypad or a “soft” keypad generated on the touch screen display. In various embodiments, the output elements include the display <b>805</b> for showing a graphical user interface (GUI), a visual indicator <b>820</b> (e.g., a light emitting diode), and/or an audio transducer <b>825</b> (e.g., a speaker). In some embodiments, the mobile computing device <b>800</b> incorporates a vibration transducer for providing the user with tactile feedback. In yet another embodiment, the mobile computing device <b>800</b> incorporates input and/or output ports, such as an audio input (e.g., a microphone jack), an audio output (e.g., a headphone jack), and a video output (e.g., a HDMI port) for sending signals to or receiving signals from an external device.

<figref idref="DRAWINGS">FIG. 8B</figref> is a block diagram illustrating the architecture of one embodiment of a mobile computing device. That is, the mobile computing device <b>800</b> can incorporate a system (i.e., an architecture) <b>802</b> to implement some embodiments. In one embodiment, the system <b>802</b> is implemented as a “smart phone” capable of running one or more applications (e.g., browser, e-mail, calendaring, contact managers, messaging clients, games, and media clients/players). In some embodiments, the system <b>802</b> is integrated as a computing device, such as an integrated personal digital assistant (PDA) and wireless phone.

One or more application programs <b>850</b> may be loaded into the memory <b>862</b> and run on or in association with the operating system <b>864</b>. Examples of the application programs include phone dialer programs, e-mail programs, personal information management (PIM) programs, word processing programs, spreadsheet programs, Internet browser programs, messaging programs, and so forth. The system <b>802</b> also includes a non-volatile storage area <b>868</b> within the memory <b>862</b>. The non-volatile storage area <b>868</b> may be used to store persistent information that should not be lost if the system <b>802</b> is powered down. The application programs <b>150</b> may use and store information in the non-volatile storage area <b>868</b>, such as e-mail or other messages used by an e-mail application, and the like. A synchronization application (not shown) also resides on the system <b>802</b> and is programmed to interact with a corresponding synchronization application resident on a host computer to keep the information stored in the non-volatile storage area <b>868</b> synchronized with corresponding information stored at the host computer. As should be appreciated, other applications may be loaded into the memory <b>862</b> and run on the mobile computing device <b>800</b>.

The system <b>802</b> has a power supply <b>870</b>, which may be implemented as one or more batteries. The power supply <b>870</b> might further include an external power source, such as an AC adapter or a powered docking cradle that supplements or recharges the batteries.

The system <b>802</b> may also include a radio <b>872</b> that performs the function of transmitting and receiving radio frequency communications. The radio <b>872</b> facilitates wireless connectivity between the system <b>802</b> and the “outside world,” via a communications carrier or service provider. Transmissions to and from the radio <b>872</b> are conducted under control of the operating system <b>864</b>. In other words, communications received by the radio <b>872</b> may be disseminated to the application programs <b>150</b> via the operating system <b>864</b>, and vice versa.

The visual indicator <b>820</b> may be used to provide visual notifications and/or an audio interface <b>874</b> may be used for producing audible notifications via the audio transducer <b>825</b>. In the illustrated embodiment, the visual indicator <b>820</b> is a light emitting diode (LED) and the audio transducer <b>825</b> is a speaker. These devices may be directly coupled to the power supply <b>870</b> so that when activated, they remain on for a duration dictated by the notification mechanism even though the processor <b>860</b> and other components might shut down for conserving battery power. The LED may be programmed to remain on indefinitely until the user takes action to indicate the powered-on status of the device. The audio interface <b>874</b> is used to provide audible signals to and receive audible signals from the user. For example, in addition to being coupled to the audio transducer <b>825</b>, the audio interface <b>874</b> may also be coupled to a microphone to receive audible input, such as to facilitate a telephone conversation. In accordance with embodiments of the present invention, the microphone may also serve as an audio sensor to facilitate control of notifications, as will be described below. The system <b>802</b> may further include a video interface <b>876</b> that enables an operation of an on-board camera <b>830</b> to record still images, video stream, and the like.

A mobile computing device <b>800</b> implementing the system <b>802</b> may have additional features or functionality. For example, the mobile computing device <b>800</b> may also include additional data storage devices (removable and/or non-removable) such as, magnetic disks, optical disks, or tape. Such additional storage is illustrated in <figref idref="DRAWINGS">FIG. 8B</figref> by the non-volatile storage area <b>868</b>.

Data/information generated or captured by the mobile computing device <b>800</b> and stored via the system <b>802</b> may be stored locally on the mobile computing device <b>800</b>, as described above, or the data may be stored on any number of storage media that may be accessed by the device via the radio <b>872</b> or via a wired connection between the mobile computing device <b>800</b> and a separate computing device associated with the mobile computing device <b>800</b>, for example, a server computer in a distributed computing network, such as the Internet. As should be appreciated such data/information may be accessed via the mobile computing device <b>800</b> via the radio <b>872</b> or via a distributed computing network. Similarly, such data/information may be readily transferred between computing devices for storage and use according to well-known data/information transfer and storage means, including electronic mail and collaborative data/information sharing systems.

<figref idref="DRAWINGS">FIG. 9</figref> illustrates one embodiment of the architecture of a system for providing an activity stream across multiple workloads, as described above. Content developed, interacted with, or edited in association with the feed system <b>200</b> may be stored in different communication channels or other storage types. For example, various documents may be stored using a directory service <b>922</b>, a web portal <b>924</b>, a mailbox service <b>926</b>, an instant messaging store <b>928</b>, or a social networking site <b>930</b>. The feed application <b>255</b> may use any of these types of systems or the like for providing a user information feed <b>105</b>, as described herein. A server <b>130</b> may provide the application <b>120</b> to clients <b>125</b>. As one example, the server <b>130</b> may be a web server providing the application <b>120</b> over the web. The server <b>130</b> may provide the application <b>120</b> over the web to clients <b>125</b> through a network <b>140</b>. By way of example, the client computing device <b>125</b> may be implemented and embodied in a personal computer <b>905</b>A, a tablet computing device <b>905</b>B and/or a mobile computing device <b>905</b>C (e.g., a smart phone), or other computing device. Any of these embodiments of the client computing device may obtain content from the store <b>916</b>.

Embodiments of the present invention, for example, are described above with reference to block diagrams and/or operational illustrations of methods, systems, and computer program products according to embodiments of the invention. The functions/acts noted in the blocks may occur out of the order as shown in any flowchart. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality/acts involved.

The description and illustration of one or more embodiments provided in this application are not intended to limit or restrict the scope of the invention as claimed in any way. The embodiments, examples, and details provided in this application are considered sufficient to convey possession and enable others to make and use the best mode of claimed invention. The claimed invention should not be construed as being limited to any embodiment, example, or detail provided in this application. Regardless of whether shown and described in combination or separately, the various features (both structural and methodological) are intended to be selectively included or omitted to produce an embodiment with a particular set of features. Having been provided with the description and illustration of the present application, one skilled in the art may envision variations, modifications, and alternate embodiments falling within the spirit of the broader aspects of the general inventive concept embodied in this application that do not depart from the broader scope of the claimed invention.