Add .dropboxignore directory to exclude folders without using selective sync

The problem with selective sync is that the workflow is a bit backwards, where once you create the folder, you then have to go to selective sync and disable it, then delete what was uploaded via the web app.

It seems that selective sync is designed so that you have all folders uploaded to the cloud but don't want to download certain folders on certain systems. As opposed to having folders on a system that is not on the cloud at all.

Also another annoying thing is that it requires much more work if you have many projects (for example) each with the same kind of folders in them that you want to exclude. This would require that you repeat the same process I mentioned in the first paragraph for each project with no automation possible (without an unofficial extension).

Basically what we (or at least I'm assuming most of us) would like to have is a clone of the git .gitignore file or something to that effect.

You know..... I really want to be positive, say something encouraging here on this lovely forum.  I really do, it's just, I can't think of anything nice to say.  So I will just be positive.

I am positive that:

- Ed (Dropbox) hasn't posted anything even remotely close to a decent response on this thread, ever.

- Caleb (Dropbox) obviously is playing from the same rulebook and that response is just beyond disappointing.

- This forum is not a place for good ideas, it is simply a place where "support" peddles out non-answers and attempts to teach you how to make due with their product.  The "improvements and enhancements" are not to the product, they are to your brain so you shut up and just use the product the way it is.

So... that was kind of positive, right?

Pinged Dropbox Support asking for an update on this post. Here is what I got back.
---
This is Caleb with Dropbox support, and thanks for this feedback! We are always looking for user input when adding improvements to Dropbox, so I will make sure your comments are passed along to our development team.

Also, as mentioned in the forum post, we have a feature called Selective Sync which allows you to choose what folders on your account you would like to have synced to your computer. We have more information about Selective Sync here:

https://help.dropbox.com/syncing-uploads/selective-sync-overview

I hope this helps!

Regards,
Caleb

Btw, Mats, thank you for sync.com link. Seems good, if it has pattern "exclude" of folders and files I'm gonna move too (after so many years as a Dropbox paying customer and my entire company migration to it after my positive experience it's a pity though).

Thank you Ed.

Any news on this matter?

I know Project Infinite is keeping you all busy, and it's cool, but this little patch would make Dropbox useful again for a lot of developers all around the world, and relieve us of sudden "sync screw-ups" after "npm install" and similar.

Hi all,

Thanks again for voicing your thoughts.

While we may not respond to all feedback you share, our team constantly reads it and uses it as valuable information when they’re tracking down bugs, enhancements and continually improving Dropbox.

George H. and many others,

I think it's painfully obvious that Dropbox management have their focus on other things, and not on responding to customer concerns and dealing with customer satisfaction issues.

The key question I'm wondering about is:

Why would Dropbox have these forums, clearly presented with their corporate branding, with links to their stuff only, without advertising, and then totally ignore what their customers are telling them?

To me it seems weird and fundamentally flawed. But I guess it's a cultural thing within the Dropbox organisation, or else the top management is asleep while being fed a bunch of BS from the staff supposed to monitor and report on these issues.

Anyway, I have given up on Dropbox and moved my key stuff to Sync.com these days without much issues. And customer support is prompt, courteous and helpful.  

I tell ya', them Canadian's sure can do things differently and better ;)

+1

Wow, almost two years and no new information on this xD
Just had to wait for 84k node dependencies to sync. At what point would you feel like this is detrimental to the user experience, especially considering your syncing client chows practically 100% of my CPU while syncing?

Analogies to git ignoring files through a .gitignore file is perfect for the power user of this feature.

Similar to git, a global .dropboxignore file in the root of the Dropbox folder could define default policies; then, any descendent folder that specifies a .dropboxignore file would override those policies.

Working with LaTeX in a group project is infuriating for the other guys, unless they turn off notifications. 

Please implement a .dropboxignore marker, preferably with the same syntax as .gitignore.