Dropbox, Inc.

Alex Sydell

Kyle Consalus

Nils Milton Bunger

Thomas Kleinpeter

Aaron Staley

Tony Xu

Sam Jau

Sara Lin

Will Stockwell

Tony Grue

Brian E Smith

Benjamin Zeis Newhouse

Rian Hunter

Tina Wen

Aston Motes

David Euresti

Alicia Chen

Jie Tang

Shi Cong

Sujay Jaswa

Albert Ni

Aseem Sood

Lars Fjeldsoe-Nielsen

Jeff Bartelma

Anthony (Tony) Grue

Lars Fjeldsoe Nielsen

The present technology pertains to a organization directory hosted by a synchronized content management system. The corporate directory can provide access to user accounts for all members of the organization to all content items in the organization directory on the respective file systems of the members' client devices. Members can reach any content item at the same path as other members relative to the organization directory root on their respective client device. In some embodiments novel access permissions are granted to maintain path consistency.

Forced mount points / duplicate mounts

The present technology operates in an application layer of an operating system on a client device of a content management system to monitor for changes to shared content items that are likely unintentional&#x2014;for example the change might move a content item out of a shared space, or otherwise remove the shared content item from access by other users. The present technology can detect a content item change event on a client device, compare a source file system path for the content item change event with a destination file system path for the content item change event to determine a canonical move causing the content item change event, determine that the canonical move was likely unintentional; and display a notification informing the user that a content item change that was likely unintentional was detected and then allow the user to either confirm or deny (undo) the detected change.

File system warnings for moves of shared content items

Traversal rights

Restrictive access control list

Disclosed are systems, methods, and non-transitory computer-readable storage media for prioritizing structural operations and distributing changes in a synced online content management system. An exemplary method can include receiving, from a first client device, a first structural operation for a particular content item and an account within the online content management system. The method can also include receiving, from a second client device, a competing structural operation for the particular content item and the account. The method can then include prioritizing the first structural operation from the first client device over the competing structural operation from the second client device based on predetermined factors. The method can then include executing the first structural operation for the particular content item and the account. The exemplary method can then include distributing the prioritized first structural operation to all synced devices for execution.

Prioritizing structural operations and distributing changes in a synced online content management system

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.

System and method for regulating the upload of files for a mobile device

A portable computing device with methodologies for client-side analytic data collection are described. In one embodiment, for example, a method performed by a portable computing device having non-volatile memory includes the steps of obtaining event information reflecting runtime behavior of an application executing on the portable computing device; cryptographically encrypting the event information; storing the encrypted event information in the non-volatile memory; decrypting the encrypted event information; and sending the decrypted event information to a server over a data network, the decrypted event information encapsulated in a cryptographically secured network data stream when sent over the data network to the server.

System and method for client-side analytic data collection

A system for predictively caching digital content in which the system is configured to: (1) receive, from a user of a client device, a request to access at least one particular digital file stored on a remote server; (2) select at least one other digital file to cache locally on the client device based on at least one file-accessing tendency of the user; (3) download the at least one other digital file from the remote server to the client device; and (4) save the downloaded digital file to memory associated with the client device for later access by the user. A file-accessing tendency of the user may include the manner in which the user typically scrolls or otherwise cycles through images or other files. The system may determine the user's file-accessing tendencies based on, for example, the user's location, native language, past content-accessing practices, and/or specified user preferences.

Systems and methods for predictive caching of digital content

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.

Automatic content item upload

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.

Associating a particular account configuration during the out of box experience for a mobile device

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.

Ordering content items

A portable computing device with methodologies for client-side analytic data collection are described. In one embodiment, for example, a method performed by a portable computing device having volatile and non-volatile memory includes obtaining a plurality of events to be logged; serializing the events to be logged; storing the serialized events in the volatile memory; encrypting the serialized events to produce serialized and encrypted events; storing the serialized and encrypted events in the non-volatile memory; decrypting the serialized and encrypted events to produce serialized and decrypted events; storing the serialized and decrypted events in the volatile memory; compressing the serialized and decrypted events to produce compressed, serialized, and decrypted events; encrypting the compressed, serialized, and decrypted events to produce encrypted, compressed, and serialized events and storing the encrypted, compressed, and serialized events in the non-volatile memory.

Growing community of inventors

San Francisco, CA, United States of America

Alex Sydell