Abstract: Video is processed. Multiple raw video clips and data that describes a video project that includes the multiple raw video clips are received from a mobile device. The multiple raw video clips were captured using an integrated camera of the mobile device. The multiple raw video clips are processed to generate multiple intermediate video clips. The multiple intermediate video clips all have a same first video resolution and a same first aspect ratio. The multiple intermediate video clips are concatenated, in an order specified by the video project data, to generate a concatenated video.

Abstract: A video is produced using a mobile device that includes an integrated camera. Multiple video clips are captured using the camera. Data is generated that describes a video project. The video project includes the multiple video clips. The video project data and the multiple video clips are sent to a server. A pointer to the video project stored in a playable format is received from the server.

Abstract: Techniques for mixed-mode authentication are described. In one or more embodiments, an authentication service may be implemented to selectively configure and issue authentication tokens based upon an optional secure mode that enables enhanced security. Clients may be provided with an option to choose between an insecure mode and a secure mode for authentications. Based on this choice, tokens may be configured to include an indication of whether the secure mode is disabled or enabled. When secure mode is disabled, an insecure token valid for both secure sites and other sites is issued to a client when the client is authenticated. When the optional secure mode is enabled, both secure and insecure tokens are provided to the client. The authentication services and/or other services may be configured to reject an insecure token when secure mode is enabled to prevent unauthorized use of a stolen token to access secure resources.

Abstract: Techniques for mixed-mode authentication are described. In one or more embodiments, an authentication service may be implemented to selectively configure and issue authentication tokens based upon an optional secure mode that enables enhanced security. Clients may be provided with an option to choose between an insecure mode and a secure mode for authentications. Based on this choice, tokens may be configured to include an indication of whether the secure mode is disabled or enabled. When secure mode is disabled, an insecure token valid for both secure sites and other sites is issued to a client when the client is authenticated. When the optional secure mode is enabled, both secure and insecure tokens are provided to the client. The authentication services and/or other services may be configured to reject an insecure token when secure mode is enabled to prevent unauthorized use of a stolen token to access secure resources.

Abstract: A schema-based service for Internet access to per-user services data, wherein access to data is based on each user's identity. The service includes a schema that defines rules and a structure for each user's data, and also includes methods that provide access to the data in a defined way. The services schema thus corresponds to a logical document containing the data for each user. The user manipulates (e.g., reads or writes) data in the logical document by data access requests through defined methods. In one implementation, the services schemas are arranged as XML documents, and the services provide methods that control access to the data based on the requesting user's identification, defined role and scope for that role. In this way, data can be accessed by its owner, and shared to an extent determined by the owner.

Abstract: Errors are captured, packaged, and reported in a client application and sent to a server computer for logging and diagnosis in a distributed computing environment. Client applications may package pertinent information about the client system configuration, the state of the client application at the time of the error, and other useful information, and send the packaged information to a server computer so that developers may identify and diagnose problems and monitor an application's performance. One example includes error capturing and reporting of various scripts that are operable within a client browser application.

Abstract: A schema-based service for Internet access to per-user services data, wherein access to data is based on each user's identity. The service includes a schema that defines rules and a structure for each user's data, and also includes methods that provide access to the data in a defined way. The services schema thus corresponds to a logical document containing the data for each user. The user manipulates (e.g., reads or writes) data in the logical document by data access requests through defined methods. In one implementation, the services schemas are arranged as XML documents, and the services provide methods that control access to the data based on the requesting user's identification, defined role and scope for that role. In this way, data can be accessed by its owner, and shared to an extent determined by the owner.

Abstract: A schema-based contacts service for Internet access to per-user contact data, wherein access to data is based on each user's identity. The contacts service includes a schema that defines rules and a structure for each user's data, and also includes methods that provide access to the data in a defined way. The contacts schema thus corresponds to a logical document containing the data for each user. The user manipulates (e.g., reads or writes) data in the logical document by data access requests through defined methods. In one implementation, the contacts schemas are arranged as XML documents, and the services provide methods that control access to the data based on the requesting user's identification, defined role and scope for that role. In this way, data can be accessed by its owner, and shared to an extent determined by the owner.

Abstract: A schema-based calendar service for Internet access to per-user contact data, wherein access to data is based on each user's identity. The calendar service includes a schema that defines rules and a structure for each user's data, and also includes methods that provide access to the data in a defined way. The calendar schema thus corresponds to a logical document containing the data for each user. The user manipulates (e.g., reads or writes) data in the logical document by data access requests through defined methods. In one implementation, the calendar schemas are arranged as XML documents, and the services provide methods that control access to the data based on the requesting user's identification, defined role and scope for that role. In this way, data can be accessed by its owner, and shared to an extent determined by the owner.