Abstract: Aspects of the present disclosure relate to a unified activity service. In one aspect, different files stored on different storage platforms may be rendered on different user interfaces. Multiple activities associated with each of the different files may be obtained from the activity service. In another aspect, activity metadata corresponding to the multiple activities may be stored in the activity service. Activities associated with the different files may include content changes in a file (e.g., edits and deletions), sharing a file, renaming a file, comments within a file, messaging, and conversations related to a file. The different storage platforms may be independent of the activity service.

Abstract: Implementations of enhanced content collaboration technology are disclosed herein. In an implementation, a collaboration service determines which collaboration commands to surface in association with each user in a list of users collaborating on a document. The collaboration commands are selected based on each user's collaboration state. The service updates local applications with information indicative of the user state, so that the local applications may surface a user-specific, collaboration state-driven selection of commands.

Abstract: Aspects of the present disclosure relate to systems and methods for providing distinct conversations within a file activity feed for display on a user interface of a client computing device. A file created with an application may be rendered on the user interface. The file may include at least a chat pane comprising a plurality of chat messages and a file activity feed including one or more activities associated with the file. It may be determined when a distinct conversation begins and ends within the chat pane. The distinct conversation may include at least some of the plurality of chat messages. In response to determining when the distinct conversation begins and ends, the distinct conversation may be recorded as a distinct conversation activity associated with the file. The distinct conversation activity may be displayed within the file activity feed.

Abstract: Aspects of the present disclosure relate to systems and methods for creating a file activity feed for display on a user interface of a client computing device. In one aspect, data comprising a plurality of activities associated with a file may be obtained. Two or more activities from the plurality of activities may be grouped into a single module of work for display within the file activity feed. The file activity feed may be displayed on the user interface of the client computing device. In some cases, the file activity feed includes one or more file activity elements including at least the single module of work. In some cases, the file activity feed includes a filter icon and a query feature. The filter icon may provide one or more filter preferences for filtering the file activity feed. The query feature may facilitate querying the file activity feed.

Abstract: Aspects of the present disclosure relate to systems and methods for extending emoji reactions into file specific content. In one aspect, a file created with an application may be rendered on a user interface. One or more activities associated with the file created with the application may be obtained. In one example, the one or more activities include corresponding activity metadata. A file activity feed including the one or more activities associated with the file may be rendered within the file. The one or more activities may include at least an emoji icon displayed within at least one of the one or more activities.

Abstract: Aspects of the present disclosure relate to a unified activity service. In one aspect, different files stored on different storage platforms may be rendered on different user interfaces. Multiple activities associated with each of the different files may be obtained from the activity service. In another aspect, activity metadata corresponding to the multiple activities may be stored in the activity service. Activities associated with the different files may include content changes in a file (e.g., edits and deletions), sharing a file, renaming a file, comments within a file, messaging, and conversations related to a file. The different storage platforms may be independent of the activity service.

Abstract: Aspects of the present disclosure relate to a unified activity service. In one aspect, different files stored on different storage platforms may be rendered on different user interfaces. Multiple activities associated with each of the different files may be obtained from the activity service. In another aspect, activity metadata corresponding to the multiple activities may be stored in the activity service. Activities associated with the different files may include content changes in a file (e.g., edits and deletions), sharing a file, renaming a file, comments within a file, messaging, and conversations related to a file. The different storage platforms may be independent of the activity service.

Abstract: Aspects of the present disclosure relate to systems and methods for creating a file activity feed for display on a user interface of a client computing device. In one aspect, data comprising a plurality of activities associated with a file may be obtained. A timestamp associated with a user identity of the file may be identified. One or more missed activities (e.g., those that occurred since a user was away from the file) may be identified from the plurality of activities based on the identified timestamp. It may be determined which missed activities of the one or more missed activities are relevant to a user associated with the user identity. The one or more missed activities determined to be relevant to the user associated with the user identity may be displayed within the file activity feed on the user interface of the client computing device.

Abstract: Aspects of the present disclosure relate to systems and methods for providing distinct conversations within a file activity feed for display on a user interface of a client computing device. A file created with an application may be rendered on the user interface. The file may include at least a chat pane comprising a plurality of chat messages and a file activity feed including one or more activities associated with the file. It may be determined when a distinct conversation begins and ends within the chat pane. The distinct conversation may include at least some of the plurality of chat messages. In response to determining when the distinct conversation begins and ends, the distinct conversation may be recorded as a distinct conversation activity associated with the file. The distinct conversation activity may be displayed within the file activity feed.

Abstract: Aspects of the present disclosure relate to systems and methods for creating a file activity feed for display on a user interface of a client computing device. In one aspect, data comprising a plurality of activities associated with a file may be obtained. A timestamp associated with a user identity of the file may be identified. One or more missed activities (e.g., those that occurred since a user was away from the file) may be identified from the plurality of activities based on the identified timestamp. It may be determined which missed activities of the one or more missed activities are relevant to a user associated with the user identity. The one or more missed activities determined to be relevant to the user associated with the user identity may be displayed within the file activity feed on the user interface of the client computing device.

Abstract: Aspects of the present disclosure relate to systems and methods for extending emoji reactions into file specific content. In one aspect, a file created with an application may be rendered on a user interface. One or more activities associated with the file created with the application may be obtained. In one example, the one or more activities include corresponding activity metadata. A file activity feed including the one or more activities associated with the file may be rendered within the file. The one or more activities may include at least an emoji icon displayed within at least one of the one or more activities.

Abstract: Aspects of the present disclosure relate to systems and methods for creating a file activity feed for display on a user interface of a client computing device. In one aspect, data comprising a plurality of activities associated with a file may be obtained. Two or more activities from the plurality of activities may be grouped into a single module of work for display within the file activity feed. The file activity feed may be displayed on the user interface of the client computing device. In some cases, the file activity feed includes one or more file activity elements including at least the single module of work. In some cases, the file activity feed includes a filter icon and a query feature. The filter icon may provide one or more filter preferences for filtering the file activity feed. The query feature may facilitate querying the file activity feed.

Abstract: Aspects of the present disclosure relate to a unified activity service. In one aspect, a first file stored on a first storage platform may be rendered on a first user interface. One or more activities associated with the first file may be obtained from the activity service. A second file stored on a second storage platform may be rendered on a second user interface. One or more activities associated with the second file may be obtained from the activity service. In another aspect, activity metadata corresponding to at least one activity associated with a first file stored on a first storage platform and activity metadata corresponding to at least one activity associated with a second file stored on a second storage platform may be received at and stored in the activity service.

Abstract: Implementations of enhanced content collaboration technology are disclosed herein. In an implementation, a collaboration service determines which collaboration commands to surface in association with each user in a list of users collaborating on a document. The collaboration commands are selected based on each user's collaboration state. The service updates local applications with information indicative of the user state, so that the local applications may surface a user-specific, collaboration state-driven selection of commands.