Cyberduck decided they’re OK with having some invisible files, and Wasabi manager might be similar:
#6757 closed defect (wontfix) Keys with double slashes are invisible
I think this stems from the fact that there are not truly folders, but a folder simulation based on slashes.
The double slash case would (I think) not be kept on your local filesystem, e.g. Linux treats it as single:
$ mkdir -p /tmp/foo//bar
$ ls foo
bar
$
Object key and metadata places very few rules on what’s in the key beyond that size limit is 1024 bytes, however it does discuss the use of a delimiter (commonly “/”) to create the illusion that there are folders.
Folder-oriented viewers could typically break paths apart at path delimiter to see pseudo folder structure. Question for the double-slash case becomes how to display the nameless folder level implied by double slash with no “folder” name between. It could be shown as a nameless level, but easy path is to ignore it.
Their convention seems to be to not use what an OS would call an absolute path beginning with a slash, therefore a leading slash might get how’s-the-folder-before-that-slash-shown? Trailing might also double because Duplicati will probably add a slash before adding what would be a filename on any ordinary OS.
I suggested numerous ways to infer whether or not the files are on Wasabi, but for direct view you might need some lower-level viewer, preferably one that will let you see all of the keys in the bucket without any attempt to “folderize” the view. If the tool doesn’t do it, it can’t do it wrong. I mentioned Duplicati’s tool, but
Quick way to list all files in Amazon S3 bucket? seems one way to do it, and there are many other ideas.
AWS CLI User Guide.if you want to use Amazon’s tool to look around.