Hacker News new | ask | show | jobs
by chimeracoder 5173 days ago
I agree. I actually read your comment an hour ago, thought nothing of it, then just now tried to send a file to someone, and realized immediately how important this is.

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.

2 comments

Wonder why this reply is dead?

---

ivankirigin 19 minutes ago | link [dead] You can view all the links you've made here: http://dropbox.com/links Also, when something is linked, there is a link icon on the right side of the file browser on http://dropbox.com/home

I posted the comment twice because the parent was posted twice. http://news.ycombinator.com/item?id=3879016

My guess is a bot killed it thinking the duplicate post was spam. No big deal

You can view all the links you've made here: http://dropbox.com/links

Also, when something is linked, there is a link icon on the right side of the file browser on http://dropbox.com/home

Right now that's empty for me, though maybe it doesn't list files in Public/ (though why that would be the case, I'm not sure....)

Still, if that works, that's good and takes care of #1, but I'd still like to see something like #2. The sad part is that it wouldn't be that hard for a 3rd party to implement (assuming that they support the /links endpoint in the API), but I'd be too afraid to do it myself, given Dropbox's history with broken symbolic links.