Abstract: Implementing people as operating system level objects. A method includes, for a user logged in to an operating system, identifying a person with a relationship to the user. For the person, the method further includes identifying information, including information that can be used to communication with the person. The method further includes storing the information related to the person in a data store that is a global data store with respect to the operating system such that the information related to the person can be accessed at the operating system level. The method further includes using the information related to the person stored in the data store to identify applications or services that can be used to communicate with the person. The method further includes displaying in a user interface for the person an enumeration of applications or services that can be used to communicate with the person.

Abstract: Implementing people as operating system level objects. A method includes, for a user logged in to an operating system, identifying a person with a relationship to the user. For the person, the method further includes identifying information, including information that can be used to communication with the person. The method further includes storing the information related to the person in a data store that is a global data store with respect to the operating system such that the information related to the person can be accessed at the operating system level. The method further includes using the information related to the person stored in the data store to identify applications or services that can be used to communicate with the person. The method further includes displaying in a user interface for the person an enumeration of applications or services that can be used to communicate with the person.

Abstract: One or more techniques and/or systems are disclosed for providing a client application with access to a file based upon a local offline version of the file and/or web online version of the file. That is, a file may be shared/synchronized from a remote source, such as a web storage service. A web online version of the file may be maintained by the web storage service, while local offline versions of the file may be stored at client devices. A sync module comprising knowledge of the local and/or web versions of the file may provide a client application with access to the file based upon the local and/or web version of the file. The sync module may also delegate synchronization authorization to the client application given that the client application may comprise sophisticated file handling functionality.

Abstract: A user may operate many devices, each of which may provide a set of actions, such as installing firmware or software or viewing the contents of the device. However, in order to perform these actions, the user may have to interact with each device using a different user interface, resulting in an inconsistent user experience. Instead, a device action service may allow a user to identify his or her devices, may identify the actions available for each device (e.g., by interacting with a device source of each device, such as a manufacturer); and upon the request of the user, may present a list of the user's devices and the actions available for each device. The actions may comprise hyperlinks to various portions of the website of the device source (e.g., a driver page and a service registration page), or controls invoking the requested action upon the device.

Abstract: A user may operate many devices, each of which may provide a set of actions, such as installing firmware or software or viewing the contents of the device. However, in order to perform these actions, the user may have to interact with each device using a different user interface, resulting in an inconsistent user experience. Instead, a device action service may allow a user to identify his or her devices, may identify the actions available for each device (e.g., by interacting with a device source of each device, such as a manufacturer); and upon the request of the user, may present a list of the user's devices and the actions available for each device. The actions may comprise hyperlinks to various portions of the website of the device source (e.g., a driver page and a service registration page), or controls invoking the requested action upon the device.

Abstract: One or more techniques and/or systems are disclosed for providing a client application with access to a file based upon a local offline version of the file and/or web online version of the file. That is, a file may be shared/synchronized from a remote source, such as a web storage service. A web online version of the file may be maintained by the web storage service, while local offline versions of the file may be stored at client devices. A sync module comprising knowledge of the local and/or web versions of the file may provide a client application with access to the file based upon the local and/or web version of the file. The sync module may also delegate synchronization authorization to the client application given that the client application may comprise sophisticated file handling functionality.

Abstract: A content user experience is described. In one or more implementations, a user interface is displayed that has selectable representations of content sources, at least one of which is available via a network. Responsive to selection of one or more of the content sources via the user interface, representations of content are displayed in the user interface using metadata obtained from the selected one or more content sources, the representations arranged according to a hierarchy used at a respective content source to arrange access to the content. Responsive to selection of one or more of the representations via the user interface; the content is obtained that corresponds to the selected representations and the obtained content is displayed in the user interface.

Abstract: A user of a set of devices may wish to view the availability statuses of respective devices (e.g., an indication of connectivity, and optionally associated information such as battery power and processor availability). However, users are often familiar with availability statuses (and the indicators representing such statuses) of contacts in a chat environment, such as “available,” “busy,” and “unavailable.” Therefore, device availability statuses may be presented using the same semantics and aesthetics of contact availability statuses, e.g., using the statuses and indicators of a chat environment, including an “available” (available and ready to provide services), “busy” (reachable but unable to provide services), and “unavailable” (unreachable). This user interface design may result in a more easily understandable semantics and a more visually consistent user experience.

Abstract: A user may operate many devices, each of which may provide a set of actions, such as installing firmware or software or viewing the contents of the device. However, in order to perform these actions, the user may have to interact with each device using a different user interface, resulting in an inconsistent user experience. Instead, a device action service may allow a user to identify his or her devices, may identify the actions available for each device (e.g., by interacting with a device source of each device, such as a manufacturer); and upon the request of the user, may present a list of the user's devices and the actions available for each device. The actions may comprise hyperlinks to various portions of the website of the device source (e.g., a driver page and a service registration page), or controls invoking the requested action upon the device.

Abstract: Multipersona creation and management is described. In one of a variety of examples, a system provides creation and management of multiple personas of a single user. Each of the personas, for instance, may have an associated external representation of the user, such as user tile, alias, email address, and so on. These personas may then be managed, both automatically and manually, to provide different external representations of the user as desired.

Abstract: Mechanisms to assist a user in obtaining content may be integrated with the tools that allow the user to author an e-mail message or any other type of document. For example, an e-mail composition system may offer various buttons that allow users to obtain certain types of content—e.g., movie times, restaurant menus, etc. When the user clicks the button, the requested type of content may be obtained, and the user may be offered the opportunity to insert the obtained content into the document that is being authored. The content that is obtained may follow a particular structure. For example, a system might be configured to respond to a request for movie-related content by returning a list of show-times and theaters for a particular movie.

Abstract: A customizable service provider user interface is described. In an implementation, a user is logged onto a suite a web services, to which, the user has not previously logged on. A user interface is output having a plurality of portions, one or more of which are customizable by the user through use of one or more overlays to customize interaction with the suite of web services.

Abstract: The techniques and technologies described herein enable real-time user identity information to be maintained by a network server architecture such that the user identity information can be provided across multiple client devices and/or across multiple collaborative applications supported by the client devices. The client devices and the collaborative applications can be designed to receive and process the network-based user identity information for presentation in a consistent display format regardless of the client device type and in the context of different collaborative applications.

Abstract: User persona content targeting is described. In an embodiment, a targeted content system includes a client account that corresponds to a user of computing-based client device(s), and the client account is associated with multiple personas that are each a different on-line representation of the user. A persona system initiates content being targeted to the user via a computing-based client device when the user is represented on-line as a first persona, and then initiates different content being targeted to the user via the computing-based client device when the user is represented on-line as a second persona.

Abstract: A customizable service provider user interface is described. In an implementation, a user is logged onto a suite a web services, to which, the user has not previously logged on. A user interface is output having a plurality of portions, one or more of which are customizable by the user through use of one or more overlays to customize interaction with the suite of web services.

Abstract: Embodiments of persona creation and management techniques are described herein.