9837c06 created the issue

Since S3 has no notion of directories, Cyberduck seems to be creating an empty file when you use the "new folder" command. Using the AWS-CLI (can install with homebrew, run "aws configure" after you install), I've verified that there is indeed a zero-byte file that seems to have a space character as its name. This is fine/needed when the directory is empty but once the directory has been populated then this "empty" file should be removed automatically. An alternative is to allow the user to see/delete this file since the user can do neither with Cyberduck at the moment.

Empty file that Cyberduck creates when creating new folders:

~ ❯❯❯ aws s3 ls s3://foo/bar
2015-03-05 17:02:01          0
2015-03-05 17:05:11          0 hello.world

Should be easily reproduced by the following steps:

1. Create an new folder in S3
2. Place a file in that folder that you just created
3. Use some other means of displaying that directory (Cyberduck won't show it as far as I can tell)
4. Note the empty placeholder file that was created along with the file you place in that new directory