Abstract:
A method of providing particular account configurations to a user of a mobile device based on a predetermined account configuration offering between a mobile device manufacturer and a third-party service provider based on a code stored on the mobile device. During the out-of-box experience (OOBE) when the user is initially configuring the mobile device, the third-party provider receives user information, a code, and a mobile device identification number. The third-party service provider confirms that the mobile device is eligible for the particular account configuration by using the code and mobile device identification number. Once account configuration eligibility is confirmed, the third-party service provider associates the particular account configuration with either an existing user account or with a new user account established during the OOBE.
Abstract:
A client device can be configured to perform a local index search and a server index search to automatically identify and upload content items on the client device that have not been uploaded to an online content management system. A local index search can include creating a unique local identifier of a content item and searching a local upload index that includes the unique local identifier of each content item that has been uploaded. A server index search can include creating a unique server identifier of the content item and searching a server upload index that includes the unique server identifier of each content item stored on the online content management system. Content items that are determined to have not been uploaded to the online content management system based on the results of the two searches, can be uploaded to the content management system by the client device.
Abstract:
A creation order of content items can generally be determined by a metadata creation time associated with the content items. In some instances, multiple content items can be associated with the same metadata creation time. To determine the order of content items associated with the same metadata creation time, a files system modification time for the content items can be accessed. The file system modification time may indicate time in a smaller time increment than the metadata creation time. If the creation order of the content items cannot be determined from the file system modification time, the names of the content items can be analyzed to determine if they indicate a creation order. Alternatively the order the content items are placed in memory can be used to determine the creation order. Metadata identifying the determined creation order of the content items can be appended to the content items.
Abstract:
Disclosed are systems, methods, and non-transitory computer-readable storage media for uploading a content item to a content management system in fixed size data blocks. A client device can split a content item into fixed size data blocks and create a unique identifier for each of the fixed size data blocks. The unique identifiers can be and transmitted to the content management system to determine which fixed size data blocks are already stored on the content management system. The client device can create a unique identifier for a fixed size data block by using at least a portion of the fixed size data block as input in a hashing algorithm. The resulting hash output can be the unique identifier. The content management system can search for the unique identifiers in a content item index that lists the unique identifier for each fixed size data block stored on the content management system.
Abstract:
A creation order of content items can generally be determined by a metadata creation time associated with the content items. In some instances, multiple content items can be associated with the same metadata creation time. To determine the order of content items associated with the same metadata creation time, a files system modification time for the content items can be accessed. The file system modification time may indicate time in a smaller time increment than the metadata creation time. If the creation order of the content items cannot be determined from the file system modification time, the names of the content items can be analyzed to determine if they indicate a creation order. Alternatively the order the content items are placed in memory can be used to determine the creation order. Metadata identifying the determined creation order of the content items can be appended to the content items.
Abstract:
A method of providing particular account configurations to a user of a mobile device based on a predetermined account configuration offering between a mobile device manufacturer and a third-party service provider based on a code stored on the mobile device. During the out-of-box experience (OOBE) when the user is initially configuring the mobile device, the third-party provider receives user information, a code, and a mobile device identification number. The third-party service provider confirms that the mobile device is eligible for the particular account configuration by using the code and mobile device identification number. Once account configuration eligibility is confirmed, the third-party service provider associates the particular account configuration with either an existing user account or with a new user account established during the OOBE.
Abstract:
A system and method for detecting and accounting for the improper use of a deal code on a mobile device. When the user initially configures the mobile device, the third-party provider receives information from the mobile device that includes user information, mobile device information, a deal code associated with a third-party service, information about an application program preloaded on the mobile device associated with the service, and a hash value that is at least partially calculated based on the foregoing. The third-party service provider calculates a second hash value at least partially based on the received information and based on other predetermined information and compares the first hash value to the second hash value. Based on the comparison, the system determines if use of the deal code is improper and, if so, tracks the user and mobile device information to prevent improper use of the deal code.
Abstract:
A content management server that uploads files from a mobile device to a cloud-based storage location based on a battery level associated with the mobile device. The content management system receives mobile device operating information and regulates the upload of files based on the mobile device operating information. In various embodiments, the mobile device operating information includes battery information. If the mobile device battery level drops below a first predetermined level, the content management system regulates the upload of files. Once the upload of files is regulated, the content management system continues to monitor the mobile device operating information. If the content management system determines that the mobile device battery level exceeds a second predetermined level, the content management system resumes the file upload process.
Abstract:
Disclosed are systems, methods, and computer-readable storage media for enhancing event summaries of synced online content management system interactions. Users can identify one or more of the collapsed events markers that have pointers to the original, uncondensed, event markers. Upon identifying the one or more collapsed event markers, users can add additional data, via the pointers, to the original, uncondensed, event markers that were used to generate the collapsed event marker. The content management system can then perform a new analysis of the shared dataspace, analyzing the event markers using pre-existing data and the newly added data to create additional collapsed event markers, modify previously generated collapsed event markers, or remove/replace collapsed event markers. These enriched collapsed event markers can then newly presented to the user.
Abstract:
Disclosed are systems, methods, and computer-readable storage media for enhancing event summaries of synced online content management system interactions. Users can identify one or more of the collapsed events markers that have pointers to the original, uncondensed, event markers. Upon identifying the one or more collapsed event markers, users can add additional data, via the pointers, to the original, uncondensed, event markers that were used to generate the collapsed event marker. The content management system can then perform a new analysis of the shared dataspace, analyzing the event markers using pre-existing data and the newly added data to create additional collapsed event markers, modify previously generated collapsed event markers, or remove/replace collapsed event markers. These enriched collapsed event markers can then newly presented to the user.