Perhaps your concern is slightly distinct, but the article addresses the discovery concerns you have given. Specifically, a LANSync peer can only request block

Perhaps your concern is slightly distinct, but the article addresses the discovery concerns you have given. Specifically, a LANSync peer can only request blocks for which it shares namespace authorization. Each distinct shared folder context (e.g. a folder shared between users, a whole Dropbox folder authorized for a single user on multiple computers) has a different namespace, and that namespace is associated with a keypair, issued by Dropbox. Block discovery and exchange is conducted over HTTPS, with each client and server having to use the key associated with the namespace of the block they wish to exchange. Since Dropbox clients/peers use SNI to identify the namespace, an eavesdropper on the network could know that two computers have access to the same namespace/folder (it is not clear from the post if the namespace contains any specific identifying information beyond its uniqueness), but not which files (or, more accurately, blocks) that namespace contained. A user who knew the key for a namespace could identify blocks being exchanged, but such a user would already have owned the Dropbox installation enough to have access not just to the list of files but to the files themselves.