Abstract: An interface of a content management system manages storage and access of content on the system. For example, after receiving, from a client, a request to download a content item, the interface determines whether the request includes a valid token. If so, the interface sends a content item request to a storage service, retrieves the content item, and sends the content item to the client. Otherwise, the interface sends an authorization request to an authorization service, an authentication request to an authentication service, and a content item request to the storage service. Based on the requests, the interface determines whether the content item is available in storage and whether the client is authorized to access the content item. When the content item is available in storage and the client is authorized to access the content item, the interface retrieves the content item and sends the content item to the client.

Abstract: In some embodiments, an interface of a content management system manages synchronized content on storage systems. For example, the interface stores, on a metadata storage structure, records of metadata associated with blocks of data stored on a storage, the records including block identifiers that uniquely identify the blocks and timestamps associated with the blocks. The interface identifies a batch of storage operations associated with the blocks, including one or more delete operations. For each delete operation, the interface queries the metadata storage structure for a timestamp corresponding to a block of data associated with the delete operation, determines whether the delete operation creates a race condition between the delete operation and an add operation associated with the block of data, and rejects the delete operation when the delete operation creates the race condition or the timestamp corresponding to the block of data is newer than a predetermined period of time.

Abstract: The disclosed technology relates to a system configured to compute a difference between a local tree data structure representing a file system state for content items associated with a user account on the computing system and a sync tree data structure representing a known synchronization state between a content management system and the computing system. The system is configured to generate, based on the difference, a set of operations that when performed update the content items stored on the content management system to converge a server state for content items associated the user account on the content management system and the file system state.

Abstract: The disclosed technology relates to a system configured to identify at least one difference between a sync tree and at least one of a remote tree and a local tree. The sync tree represents a known synced state between a server state and a file system state, the remote tree represents the server state, and the local tree represents the file system state. The system may further generate, based on the at least one difference, a set of operations configured to converge the server state and the file system state and manage the execution of the set of operations.

Abstract: The disclosed technology relates to a system configured to obtain a set of tree data structures including a remote tree representing a server state of content items associated with a user account on a content management system, a local tree representing a file system state of content items associated with the user account on a client device, and a sync tree representing a known sync state between the content management system and the client device. The system is configured to determine that the user account on the content management system includes at least one modification not synchronized to the client device by comparing the remote tree and the sync tree.

Abstract: Resynchronization of folders shared among multiple client devices over a network is provided. Metadata and hash values stored on the client device are moved from a metadata database to a resynchronization database, and the data in the metadata database is deleted. Metadata is created for locally stored synchronized files. For each file, the created metadata is compared to the metadata stored in the resynchronization database. If the metadata matches, hash values are retrieved from the resynchronization database and stored with the created metadata in the metadata database. If the metadata does not match, hashes for the file are created and stored with the created metadata in the metadata database. A synchronization operation may be performed which consists of comparing the files stored on the client to the synchronized versions on a host server and updating or adding files that are not present or not up to date.

Abstract: Resynchronization of folders shared among multiple client devices over a network is provided. Metadata and hash values stored on the client device are moved from a metadata database to a resynchronization database, and the data in the metadata database is deleted. Metadata is created for locally stored synchronized files. For each file, the created metadata is compared to the metadata stored in the resynchronization database. If the metadata matches, hash values are retrieved from the resynchronization database and stored with the created metadata in the metadata database. If the metadata does not match, hashes for the file are created and stored with the created metadata in the metadata database. A synchronization operation may be performed which consists of comparing the files stored on the client to the synchronized versions on a host server and updating or adding files that are not present or not up to date.

Abstract: Resynchronization of folders shared among multiple client devices over a network is provided. Metadata and hash values stored on the client device are moved from a metadata database to a resynchronization database, and the data in the metadata database is deleted. Metadata is created for locally stored synchronized files. For each file, the created metadata is compared to the metadata stored in the resynchronization database. If the metadata matches, hash values are retrieved from the resynchronization database and stored with the created metadata in the metadata database. If the metadata does not match, hashes for the file are created and stored with the created metadata in the metadata database. A synchronization operation may be performed which consists of comparing the files stored on the client to the synchronized versions on a host server and updating or adding files that are not present or not up to date.

Abstract: Systems, methods, and non-transitory computer-readable media can identify a content item within a social networking system for which a reminder is to be provided. A selection specifying one or more conditions for providing the reminder can be received. It can be determined that the one or more conditions are satisfied. The reminder can be provided via a notification within the social networking system when the one or more conditions are satisfied. The content item can be accessible via the reminder.

Abstract: Resynchronization of folders shared among multiple client devices over a network is provided. Metadata and hash values stored on the client device are moved from a metadata database to a resynchronization database, and the data in the metadata database is deleted. Metadata is created for locally stored synchronized files. For each file, the created metadata is compared to the metadata stored in the resynchronization database. If the metadata matches, hash values are retrieved from the resynchronization database and stored with the created metadata in the metadata database. If the metadata does not match, hashes for the file are created and stored with the created metadata in the metadata database. A synchronization operation may be performed which consists of comparing the files stored on the client to the synchronized versions on a host server and updating or adding files that are not present or not up to date.