|
|
|
|
|
|
by rkudeshi
5173 days ago
|
|
|
Being able to link to a folder is a godsend. I hated having to share a folder (editable) when I needed to send someone many files. However, does this now deprecate the Public folder? I thought that was one of Dropbox's best features: knowing only things in the Public folder were publicly-accessible (with a link)—and more importantly, that files located anywhere else were completely private and NOT web-accessible at all—was easy to grok and explain. I worry that as Dropbox moves toward its stated goal of becoming the "file system for the Internet" that they will give up the focus on syncing our private files in exchange for the allure of allowing every site and app to read and write from one's Dropbox. That's a worrisome future, indeed. |
|
|
What would be really great is to have an easy view for all files that are not private (or all files that are link-shared, etc., since there are three tiers of privacy in the Dropbox world). On the web interface, this would be easy, but I do most of my work on the command-line, so it seems the easiest way for them (or anyone) to implement this would be through links.
However, I know that Dropbox has had (still has?) issues with treating symlinks properly, so I'm very hesitant to write a script to handle this myself.
As it stands, though, I'm very concerned about this. I've used Dropbox for years, and I've accumulated so many files and folders there - I could do some spring cleaning, but most of it is actually stuff that I want to be able to access remotely. Right now, I know that everything is private, except for the shared folders, which I always name "shared_" by convention. Pretty soon, that won't be the case, and not having a clear system for this makes me really* uneasy, because I know that human error is the number one cause of security/privacy breaches.