Abstract: Subscriber (user) data is encrypted and stored in a service provider cloud in a manner such that the service provider is unable to decrypt and, as a consequence, to view, access or copy the data. Only the user knows a user-specific secret (e.g., a password) that is the basis of the encryption. The techniques herein enable the user to share his or her data, privately or publicly, without exposing the user-specific secret with anyone or any entity (such as the service provider).

Abstract: Subscriber (user) data is encrypted and stored in a service provider cloud in a manner such that the service provider is unable to decrypt and, as a consequence, to view, access or copy the data. Only the user knows a user-specific secret (e.g., a password) that is the basis of the encryption. The techniques herein enable the user to share his or her data, privately or publicly, without exposing the user-specific secret with anyone or any entity (such as the service provider).

Abstract: Subscriber (user) data is encrypted and stored in a service provider cloud in a manner such that the service provider is unable to decrypt and, as a consequence, to view, access or copy the data. Only the user knows a user-specific secret (e.g., a password) that is the basis of the encryption. The techniques herein enable the user to share his or her data, privately or publicly, without exposing the user-specific secret with anyone or any entity (such as the service provider).

Abstract: Subscriber (user) data is encrypted and stored in a service provider cloud in a manner such that the service provider is unable to decrypt and, as a consequence, to view, access or copy the data. Only the user knows a user-specific secret (e.g., a password) that is the basis of the encryption. The techniques herein enable the user to share his or her data, privately or publicly, without exposing the user-specific secret with anyone or any entity (such as the service provider).

Abstract: Subscriber (user) data is encrypted and stored in a service provider cloud in a manner such that the service provider is unable to decrypt and, as a consequence, to view, access or copy the data. Only the user knows a user-specific secret (e.g., a password) that is the basis of the encryption. The techniques herein enable the user to share his or her data, privately or publicly, without exposing the user-specific secret with anyone or any entity (such as the service provider).

Abstract: A method is operated at a coordinating entity to organize a set of hosts into a “synchronization” network. The coordinating entity maintains information that a particular host is online and available to be organized into the network. The coordinating entity assigns an identifier to each host that is online, and that identifier is unique within the particular network. The coordinating entity orders the node identifiers for the set of hosts. In one embodiment, the ordering organizes the synchronization network in a circle. Based on the ordering, the coordinating entity provides each host that is online with a list of K online hosts to enable each host to establish and maintain connections with K of its neighbor hosts. K is a value that is the same for all hosts within the synchronization network. For larger networks, crossover connections may be implemented to improve performance.

Abstract: Subscriber (user) data is encrypted and stored in a service provider cloud in a manner such that the service provider is unable to decrypt and, as a consequence, to view, access or copy the data. Only the user knows a user-specific secret (e.g., a password) that is the basis of the encryption. The techniques herein enable the user to share his or her data, privately or publicly, without exposing the user-specific secret with anyone or any entity (such as the service provider).

Abstract: A method is operated at a coordinating entity to organize a set of hosts into a “synchronization” network. The coordinating entity maintains information that a particular host is online and available to be organized into the network. To that end, the coordinating entity assigns an identifier (a node identifier) to each host that is online, and that identifier is unique within the particular network. The coordinating entity orders the node identifiers for the set of hosts (based on a given characteristic of the node identifiers). In one embodiment, the ordering organizes the synchronization network in a circle. Based on the ordering, the coordinating entity provides each host that is online with a list of K online hosts to enable each host to establish and maintain connections with K of its neighbor hosts. In this scheme, K is a value that is the same for all hosts within the synchronization network. For larger networks, crossover connections may be implemented to improve performance.