A complete file listing.... you mean just a dump of the DIR command?
Who cares if anyone has the file names and file sizes of your stuff?
The service itself is pretty secure. And they offer an encrypted file
transfer.
As far as I can tell all the file transferring is done peer to peer.
Because when my laptop is on the same network as my network, the file
transfer speeds jump up to 4-5megabytes (not bits) per second.... while
across the internet they are about 70-80kbytes per second (max of my
upload)....
"John" wrote:
| Quote: |  | |
|
> "Richi Jennings" wrote: | Quote: | | | |
> > I'd say you'd better figure out how you feel about it!
| | | | | >
> Well I'm pretty sure that I wouldnt be too happy about Microsoft storing a
> complete file listing on their end. If that were the case I would not use the
> service.
> | Quote: | | | |
> > A reasonable assumption is that Microsoft stores file metadata for all
> > shared files -- at a minimum file names, paths, and a hashed summary of
> > the contents (but not the contents themselves).
> >
> > My assumption is based on observing how FS behaves when changes are
> > pending, but the "donor" PC isn't connected.
| | | | | >
> Obviously they would need that much information, but it would be simple
> enough to have it only available when the PC is connected to the system. For
> the sake of user-defined shared and private libraries, clearly information
> about those files needs to be stored on the servers in order to maintain sync
> information between multiple computers. But those libraries are voluntarily
> set up and configured by the user, and they can select which folders and
> files to put in the libraries. The part that worries me is the fact that when
> one of my computers is connected, from the web interface I can browse *every
> single* file and folder and drive on that computer, and it would definitely
> bother me if THAT information is saved on the Microsoft servers. | |
| | |