Hacker News new | past | comments | ask | show | jobs | submit login

I'm sure it didn't hurt them but their execution to date has been impeccable.

One thing has popped up recently: Dropbox relies on the urls to folders in 'boxes' that are shared to remain secret, nothing stops google from indexing the contents once the ___location is known, there is no 'robots.txt' that instructs google not to peek there.

This could lead to a lot of people being highly surprised that the contents of their secret stash are suddenly open to the portion of the population that uses google.

The problem is that it's not just the users that nominally own the data that control this, basically everybody that you share that url with can 'leak' it to google, either by using a toolbar or by posting it on some webpage. After that it's fair game.

To see this for yourself:

http://www.google.com/search?hl=en&safe=off&q=a+site...

According to dropbox support this is by design, but I can still see how some people might be very surprised by this.

edited for clarity, thanks thomaswmeyer.




This is only for content that's explicitly placed in your "Public" folder, not for anywhere else in your Dropbox.


Yes, hence the 'that are not shielded'


I think it seemed that you were trying to imply the dropbox's content (not just the public portion) would be visible to anyone.

I am glad this was clarified.


No, definitely not, it's only the public folders and not the rest.


'not shielded': implies that one has to do extra work to shield those. Default is not secure scenario.

'public folder': implies one has to do extra work to make those files public. Default is not public.

I was wondering which one describes Dropbox situation correctly.


Then no one should think it's such a "secret stash", should they? I think using this term is what confused people.


Indeed it works. I switched the search term to a file name present in my shared folder and there it was.




Consider applying for YC's Summer 2025 batch! Applications are open till May 13

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: