Abstract: An application that is running on a first computing device can receive personal information from a personal information manager that is running on a second computing device. The first computing device can operate using a first platform and the second computing device can operate using a second platform that is different from the first platform. The first computing device can include a first broker, and the second computing device can include a second broker. The first broker and the second broker can be configured to establish a trusted connection between the first computing device and the second computing device. The first broker can additionally be configured to request personal information from the personal information manager via the second broker. The first broker can be configured to automatically request the personal information in response to determining that the application on the first computing device has requested the personal information.

Abstract: In non-limiting examples of the present disclosure, systems, methods and devices for providing a unified cross-platform experience are provided. A connection between a first device and a second device may be established, wherein the first device operates on a first platform and the second device operates on a second platform. A plurality of executable actions that are specific to the second device may be identified by the first device. Execution of at least one of the plurality of executable actions by the second device may be requested by the an application executed on the first device. Information obtained via execution of the at least one executable action may be received by the first device and the first device may present and/or display that information.

Abstract: In server/client architectures, the server application and client applications are often developed in different languages and execute in different environments specialized for the different contexts of each application (e.g., low-level, performant, platform-specialized, and stateless instructions on the server, and high-level, flexible, platform-agnostic, and stateful languages on the client) and are often executed on different devices. Convergence of these environments (e.g., server-side JavaScript using Node.js) enables the provision of a server that services client applications executing on the same device. The local server may monitor local events occurring on the device, and may execute one or more server scripts associated with particular local events on behalf of local clients subscribing to the local event (e.g., via a subscription model).

Abstract: An application that is running on a first computing device can receive personal information from a personal information manager that is running on a second computing device. The first computing device can operate using a first platform and the second computing device can operate using a second platform that is different from the first platform. The first computing device can include a first broker, and the second computing device can include a second broker. The first broker and the second broker can be configured to establish a trusted connection between the first computing device and the second computing device. The first broker can additionally be configured to request personal information from the personal information manager via the second broker. The first broker can be configured to automatically request the personal information in response to determining that the application on the first computing device has requested the personal information.

Abstract: In non-limiting examples of the present disclosure, systems, methods and devices for providing collaborative use of computing resources in videogame execution are provided. A list comprising an identity of a plurality of mobile games executable on a mobile computing device (e.g., smart phone, tablet) and controllable, on the mobile computing device, by one or more input devices for a primary computing device (e.g., personal computer, game console) may be surfaced. A selection of one of the plurality of mobile games may be received. The mobile computing device and the primary computing device may be paired. A video data stream of the selected game being executed on the mobile computing device may be received. The video data stream may be displayed on a display device associated with the primary computing device.

Abstract: In non-limiting examples of the present disclosure, systems, methods and devices for providing collaborative use of computing resources in videogame execution are provided. A list comprising an identity of a plurality of mobile games executable on a mobile computing device (e.g., smart phone, tablet) and controllable, on the mobile computing device, by one or more input devices for a primary computing device (e.g., personal computer, game console) may be surfaced. A selection of one of the plurality of mobile games may be received. The mobile computing device and the primary computing device may be paired. A video data stream of the selected game being executed on the mobile computing device may be received. The video data stream may be displayed on a display device associated with the primary computing device.

Abstract: In non-limiting examples of the present disclosure, systems, methods and devices for providing a unified cross-platform experience are provided. A connection between a first device and a second device may be established, wherein the first device operates on a first platform and the second device operates on a second platform. A plurality of executable actions that are specific to the second device may be identified by the first device. Execution of at least one of the plurality of executable actions by the second device may be requested by the an application executed on the first device. Information obtained via execution of the at least one executable action may be received by the first device and the first device may present and/or display that information.

Abstract: In server/client architectures, the server application and client applications are often developed in different languages and execute in different environments specialized for the different contexts of each application (e.g., low-level, performant, platform-specialized, and stateless instructions on the server, and high-level, flexible, platform-agnostic, and stateful languages on the client) and are often executed on different devices. Convergence of these environments (e.g., server-side JavaScript using Node.js) enables the provision of a server that services client applications executing on the same device. The local server may monitor local events occurring on the device, and may execute one or more server scripts associated with particular local events on behalf of local clients subscribing to the local event (e.g., via a subscription model).

Abstract: In server/client architectures, the server application and client applications are often developed in different languages and execute in different environments specialized for the different contexts of each application (e.g., low-level, performant, platform-specialized, and stateless instructions on the server, and high-level, flexible, platform-agnostic, and stateful languages on the client) and are often executed on different devices. Convergence of these environments (e.g., server-side JavaScript using Node.js) enables the provision of a server that services client applications executing on the same device. The local server may monitor local events occurring on the device, and may execute one or more server scripts associated with particular local events on behalf of local clients subscribing to the local event (e.g., via a subscription model).

Abstract: In server/client architectures, the server application and client applications are often developed in different languages and execute in different environments specialized for the different contexts of each application (e.g., low-level, performant, platform-specialized, and stateless instructions on the server, and high-level, flexible, platform-agnostic, and stateful languages on the client) and are often executed on different devices. Convergence of these environments (e.g., server-side JavaScript using Node.js) enables the provision of a server that services client applications executing on the same device. The local server may monitor local events occurring on the device, and may execute one or more server scripts associated with particular local events on behalf of local clients subscribing to the local event (e.g., via a subscription model).

Abstract: In server/client architectures, the server application and client applications are often developed in different languages and execute in different environments specialized for the different contexts of each application (e.g., low-level, performant, platform-specialized, and stateless instructions on the server, and high-level, flexible, platform-agnostic, and stateful languages on the client) and are often executed on different devices. Convergence of these environments (e.g., server-side JavaScript using Node.js) enables the provision of a server that services client applications executing on the same device. The local server may monitor local events occurring on the device, and may execute one or more server scripts associated with particular local events on behalf of local clients subscribing to the local event (e.g., via a subscription model).

Abstract: One or more techniques and/or systems are provided for identifying a location interest inference for a first user. A first set of user signals (e.g., search history, social network posts, etc.) associated with the first user may be evaluated to identify a first user location interest pattern indicative of location interests of the first user. Social signals (e.g., phone calls, emails, photo tags, shared content, etc.) between the first user and other users may be evaluated to identify a second user having a social activity relevance score above a relationship threshold with respect to the first user. A second user location interest pattern may be generated for the second user based upon user signals associated with the second user. The first user location interest pattern and the second user location interest pattern may be aggregated to create the location interest inference indicative of refined locational interests of the first user.

Abstract: Systems, methods, and computer-readable media for responding to a search query with search results ranked according to interest circles of a plurality of computer users are presented. Interest circles are formed from a computer user's navigation data, including the computer user's navigation history. A search query is received from a requesting computer user. The search query is directed to a query topic or set of query topics. A set of search results responsive to the search query are obtained. A plurality of computer users, each of the plurality of computer users having an established interest circle corresponding to the query topic, is identified. The set of search results are then ordered according to the interest circles of the identified plurality of computer users. Thereafter, the higher ordered search results are returned to the requesting computer user in response to the search query.

Abstract: Among other things, one or more techniques and/or systems are provided for configuring a route-planning module using one or more configuration plug-ins. The route-planning module may be configured to create a driving route, an internet packet route, a social event route, and/or a variety of other routes. A graph used by the route-planning module to create a route may be modified by a graph configuration plug-in, which may add, remove, and/or modify nodes and/or edges within the graph. Attributes associated with edges and/or nodes within the graph may be added, removed, and/or modified by an attribute configuration plug-in. Costs associated with edges and/or turns from a first edge to a second edge at a node may be modified by a cost configuration plug-in. In this way, the route-planning module may be customized using one or more configuration plug-ins (e.g., to accommodate user preferences).

Abstract: Among other things, one or more techniques and/or systems are provided for configuring a route-planning module using one or more configuration plug-ins. The route-planning module may be configured to create a driving route, an internet packet route, a social event route, and/or a variety of other routes. A graph used by the route-planning module to create a route may be modified by a graph configuration plug-in, which may add, remove, and/or modify nodes and/or edges within the graph. Attributes associated with edges and/or nodes within the graph may be added, removed, and/or modified by an attribute configuration plug-in. Costs associated with edges and/or turns from a first edge to a second edge at a node may be modified by a cost configuration plug-in. In this way, the route-planning module may be customized using one or more configuration plug-ins (e.g., to accommodate user preferences).

Abstract: Systems, methods, and computer-readable media for responding to a search query with search results where the search query includes a social source operation are presented. Upon receiving a search query directed to a query topic, and including a social source operation, the search engine identifies search results corresponding to the query topic, and further obtains social data necessary to satisfy the social source operation of the search query. The search results are modified in light of the social source operation according to the obtained social data. One or more search results pages are generated according to the modified search results and at least one of the search results pages is returned to the requesting computer user.

Abstract: Among other things, one or more techniques and/or systems are provided for configuring a route-planning module using one or more configuration plug-ins. The route-planning module may be configured to create a driving route, an internet packet route, a social event route, and/or a variety of other routes. A graph used by the route-planning module to create a route may be modified by a graph configuration plug-in, which may add, remove, and/or modify nodes and/or edges within the graph. Attributes associated with edges and/or nodes within the graph may be added, removed, and/or modified by an attribute configuration plug-in. Costs associated with edges and/or turns from a first edge to a second edge at a node may be modified by a cost configuration plug-in. In this way, the route-planning module may be customized using one or more configuration plug-ins (e.g., to accommodate user preferences).

Abstract: Architecture that embeds a server (a local server) inside a mobile device operating system (OS) close to the data (but under the OS services) such that the server has access to native capabilities, and offers an Internet-like frontend with which a browser or application can communicate. The local server appears as a web server, and small programs can be pushed into the local server from the browser or a remote server such that the local server can be made to perform work more effectively. Local and remote events can be triggered such as launching a browser (or other application(s)), initiating remote server calls, triggering battery save mode, locking the phone, etc. The local server can run a script execution environment such as node.js, an event driven I/O model where callbacks are invoked to handle emergent conditions (e.g., explicit requests, state changes, etc.).