Abstract: Systems and methods are provided for determining the likelihood of a user's attendance at an event. For example, the systems and methods can be used to determine that a particular user is attending, is planning to attend, has already attended, or is about to attend a particular event, such as a movie, concert, tour, etc. Further, upon determining that a user is attending, has already attended, or is about to attend an event, systems and methods can be used to serve to a device, associated with the user, content that is related to the event. For example, the content may include invites that invite the user to provide a review of the event and to join a discussion about the event. Further, for example, the content may include links to websites that provide reviews and other information about the event, provide information about related events, or that offer related items for sale.

Abstract: Technologies are described herein for collecting client-side performance metrics and latencies. A web page received by a web browser application executing on a user computing device includes markup or scripting code that instructs the browser to collect performance measures during the rendering of the content of the web page. The performance measures may include operation timings that measure the time it takes for a particular operation to complete during the rendering of the content and/or event counters that count the number of times that a specific event occurs during the rendering of the content. The web browser application sends an event report containing the collected performance measures to a reporting module executing on a server computer. The reporting module receives the event report, validates the content of the event report, and adds the event report to a database or other data storage system.

Abstract: Disclosed are various embodiments for presenting a timeline interface in association with video content features. A video content feature may be rendered on a display. A current scene in the video content feature is determined. A user interface is rendered on the display, where the user interface includes a timeline component. The timeline component represents the video content feature and visually segments the video content feature into scenes. The current scene may be visually indicated on the timeline component.

Abstract: Disclosed are various embodiments for providing extrinsic data relevant to a video content feature. A request for a video content feature is obtained from a client. The video content feature and relevant extrinsic data is sent to the client in response to the request. The extrinsic data indicates cast members who perform in the video content feature, a division of the video content feature into scenes, and a corresponding subset of the cast members who perform in each of the scenes.

Abstract: A collaborative chat room media player may enable a user to create or join a virtual lounge for a group of remotely located members to share a media experience. The virtual lounge may include a media player, an interactive communication component (e.g., instant messaging, comment board, blog, etc.), and a collaborative music queue and/or playlist. The media player may provide and/or make available recommendations to the members of the group. For example, the members may populate a playlist with media content from their media library. The media player may then add recommendations to the playlist based on the groups interests (media content selection, media content ownership, etc.). The members may vote on the content in the playlist and influence, via collaboration, when (or if) a piece of media content is played to the group.

Abstract: Disclosed are various embodiments for providing extrinsic data relevant to a video content feature. A request for a video content feature is obtained from a client. The video content feature and relevant extrinsic data is sent to the client in response to the request. The extrinsic data indicates cast members who perform in the video content feature, a division of the video content feature into scenes, and a corresponding subset of the cast members who perform in each of the scenes.

Abstract: Disclosed are various embodiments for enhancing video content with extrinsic data. A video content feature is rendered on a display. A user interface is rendered on top of the video content feature on the display. The user interface presents cast member images, each of which corresponds to a cast member in the video content feature. A selection of a cast member image is obtained through the user interface. The user interface is updated to present additional information regarding the respective cast member corresponding to the selected image.

Abstract: Supplemental content such as electronic advertisements may be previewed in situ. That is, supplemental content may be previewed in a context of a live and/or production environment along with the primary content available in that environment. In particular, electronic advertising that is still under development, that still requires testing and/or quality control, and/or electronic advertising that is unpublished may be incorporated into electronic pages by live and/or production electronic page generation computer systems. Furthermore, electronic advertising may be previewed in situ in a controlled and/or restricted manner.

Abstract: Disclosed are various embodiments for enhancing video content with extrinsic data. A video content feature is rendered on a display. A user interface is rendered on top of the video content feature on the display. The user interface presents cast member images, each of which corresponds to a cast member in the video content feature. A selection of a cast member image is obtained through the user interface. The user interface is updated to present additional information regarding the respective cast member corresponding to the selected image.

Abstract: Feedback received from users regarding potential problems with an application, service, or other source of electronic content can be configured to include additional information that help triangulate the source of the problem. Content provided by third parties can be combined with content from a primary provider, but the primary provider often will be unable to determine the precise instance of third party content that a user received that might have posed a problem for the user, as may relate to malware or another such issue. By configuring feedback submissions from users to automatically include identifying information, and by logging session data for various users, a content provider can analyze and filter the data to determine likely sources of the problem, and deactivate or otherwise address those sources. Further, the content provider can analyze the information to locate any users likely to have been exposed to the same third party content.

Abstract: Techniques, including systems and methods, for providing content utilize templates. As part of providing content to clients, templates and arguments for the templates are provided to clients. The clients themselves receive the templates and arguments for the templates and instantiate the templates. Templates and arguments for templates may each be cached by clients and/or servers for efficient future use.

Abstract: Technologies are described herein for collecting client-side performance metrics and latencies. A web page received by a web browser application executing on a user computing device includes markup or scripting code that instructs the browser to collect performance measures during the rendering of the content of the web page. The performance measures may include operation timings that measure the time it takes for a particular operation to complete during the rendering of the content and/or event counters that count the number of times that a specific event occurs during the rendering of the content. The web browser application sends an event report containing the collected performance measures to a reporting module executing on a server computer. The reporting module receives the event report, validates the content of the event report, and adds the event report to a database or other data storage system.

Abstract: Technologies are described herein for collecting client-side performance metrics and latencies. A web page received by a web browser application executing on a user computing device includes markup or scripting code that instructs the browser to collect performance measures during the rendering of the content of the web page. The performance measures may include operation timings that measure the time it takes for a particular operation to complete during the rendering of the content and/or event counters that count the number of times that a specific event occurs during the rendering of the content. The web browser application sends an event report containing the collected performance measures to a reporting module executing on a server computer. The reporting module receives the event report, validates the content of the event report, and adds the event report to a database or other data storage system.

Abstract: Feedback received from users regarding potential problems with an application, service, or other source of electronic content can be configured to include additional information that help triangulate the source of the problem. Content provided by third parties can be combined with content from a primary provider, but the primary provider often will be unable to determine the precise instance of third party content that a user received that might have posed a problem for the user, as may relate to malware or another such issue. By configuring feedback submissions from users to automatically include identifying information, and by logging session data for various users, a content provider can analyze and filter the data to determine likely sources of the problem, and deactivate or otherwise address those sources. Further, the content provider can analyze the information to locate any users likely to have been exposed to the same third party content.

Abstract: Third parties are prevented from obtaining proprietary information that a content provider might not want to expose. Targeting data used to enable a selection service to select targeted or supplemental content can be passed as an anchor in a uniform resource locator or stored in a parent file for a page. A second file can reside in an inline frame (iFrame) on the page that is able to pull the targeting data from the parent page, if in the same domain, or parse the parameters from the data in the anchor. The targeting data can be submitted to a selection service, which can return parameters specifying content or a type of supplemental content to be displayed. The request submitted to a supplemental content provider can come from a nested iFrame in a separate domain, such that the targeting data or source of the parent file cannot be obtained through the nested iFrame.