Re:Why Dropbox Succeeded and Syncplicity Didn’t
by jacquesm on Friday January 28, 2011 @04:17PM
(#2153569)
Yes, hence the 'that are not shielded'
[ Parent
| on HN ]
Re:Why Dropbox Succeeded and Syncplicity Didn’t
by sfphotoarts on Friday January 28, 2011 @04:27PM
(#2153600)
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.
Re:Why Dropbox Succeeded and Syncplicity Didn’t
by jacquesm on Friday January 28, 2011 @04:29PM
(#2153604)
No, definitely not, it's only the public folders and not the rest.
Re:Why Dropbox Succeeded and Syncplicity Didn’t
by z92 on Saturday January 29, 2011 @11:42AM
(#2155704)
'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.