Dropbox, Inc.

Parker Timmerman

Sourabh Yerfule

Kelson Reiss

Nipunn Koorapati

Pranav Vishnu Ramabhadran

Adam Arbree

Zihao Yang

Geoffry Song

Lisa Fan

Jordi Paris Ferrer

Sabrina Weschler

Royce Ausburn

Gautam Gupta

Yuyang Guo

Jonathan Chien

Rishabh Jain

David Aeschlimann

Yannis Liapis

Hongyi Shen

Tate Song

Michael Nilsson

Stanimir Pehlivanov

Nicholas Morris

Benjamin Blum

Bryan Guillemette

Techniques and systems are provided for utilizing an ignore file in a content management system. For example, a process can detect an ignore file stored in a synchronized directory of a client device. The process can access the ignore file and interpret rules stored therein that prohibit any objects matching the rule from being synchronized with a content management server. During indexing of a synchronized directory, the process can apply the rules from the ignore file and mark objects that match a rule in the ignore file by writing an attribute to the object that identifies it as an ignored object that is exempt from synchronization with the content management server.

Ignore objects from synchronizing to content management system

The present technology is directed to providing a multi-root architecture for managing devices associated with their own root namespaces. The system can include backing up multiple computing devices to a single user account such that the content items from each computing device are stored in their own respective root namespace at the user account. With each user account having multiple root namespaces, the system can identify which root namespace is receiving changes, identify which changes are necessary to synchronize the system, and then communicate those changes to the content management system. This process is facilitated by running a synchronization engine for each root namespace, thereby controlling synchronization for each root namespace. Each synchronization engine is able to retain its own parameters of operation, which provides the ability to tailor synchronization modes on each synchronization engine.

Multi-root content management system

Implementing different synchronization processes using a multi-root system

Technologies for implementing customized behaviors for content items are provided. An example method can include receiving, from a user account registered with a content management system, a request to access a content item managed by the content management system for the user account, the content item having one or more behaviors configured for an attribute associated with the content item and/or the content item associated with the attribute; obtaining, from a representation of a remote state of content items associated with the user account, metadata defining the attribute associated with the content item; based on the metadata, determining the one or more behaviors configured for the attribute and/or the content item associated with the attribute; and applying the one or more behaviors to the content item.

Per-node metadata for custom node behaviors across platforms

The present disclosure is directed toward systems, methods, and non-transitory computer-readable media for generating, managing, and restoring data backups for user account data at network-based third-party systems. For example, the disclosed systems generate data backups within a content management system to store user account data from third-party systems such as social media systems, photo library systems, video sharing systems, and others. In some cases, the disclosed systems detect changes to data a third-party system and further updates a stored data backup corresponding to the third-party system based on the detected changes.

Storing and restoring user account data backups across online platforms

The present technology pertains to synchronizing contents of a directory external to a synchronized directory by a content management system. The content management system is configured to synchronize only objects in the synchronized directory. Accordingly, the present technology creates an anchor object that represents the directory external to the synchronized directory within the synchronized directory. The anchor object includes special attributes that indicate to the synchronization client that the anchor object represents an external directory, and allows the contents of that directory to be synchronized directly to a server on the content management system without first storing the contents of the external directory on the hard drive of the client device.

Synchronizing an external location

Growing community of inventors

Jersey City, NJ, United States of America

Parker Timmerman