Add .dropboxignore directory to exclude folders without using selective sync

Ok, it seems this thread isn't going anywhere. Dropbox started with an Ideabox (do you remember it?) when it was really interested to their customers' opinion. Now it's not as such anymore.

But... but we are developers, so... why don't we do ourself this service? A "developer oriented" Dropbox with the thing we need (and more).

I can imagine it as such:

• The server would be Docker (or Chef, Vagrant, etc…) encapsulated so you can push it on AWS, Azure, etc…
• The storage can be directly attached (a local disk), an ethernet storage or a cloud storage like S3, Google Docs, etc…
• Possibility to keep timely offsite backups on remote disk, Amazon Glacier or low cost storage options for increased security.
• The server would have a web interface for configuring and managing the projects.
• The server can have an “emergency” web editor for coding on the go.
• You will have a native sync tool on your computer or device (of course).
• Everything will be encrypted with a key you decide.
• This tool will read .gitignore files and Git (or SVN) remotes in folders. You can override .gitignore using a .somethingignore file.
• Can be told to follow symlinks or not (sometimes it’s useful)
• You will have infinite versions of file, with git pushes visible as milestones between directly from the webinterface/interface (a better reference than “2 days ago” file).
• You can connect to Github (or your git remote) and push/pull actual synced folders to/from remotes from the web interface (you can push/pull on mobility)
• Your sync client will give remote ssh access to your computers (if they are on) so you can run your Node (or anything you can run in console) on the go and debug from the web editor.
• The server will born “API oriented”, so can be consumed by editors (Atom, Sublime, Textmate) that can offer revisions in the interface, and from web services like ITTT.
• You can download a “patch” file between revisions, so you can apply (and distribute) this instead of the whole file.
• You can invite remote Github collaborators to your server, or anyone (readonly, write, etc… access) via mail.
• This would be a “self managed” solution that can be offered as a Cloud solution for a modest fee (for business). Dev folders are normally very light, so it will require less space than other solutions, so cheaper plans.

This could be considered as a “niche Dev Dropbox” you can have along Dropbox if you want (until Dropbox understand that developing the “.dropboxignore” feature would require a day of work and would make a bunch of customers happy) or replace it totally.

We could do it together as an open source project, and, after that, scream "screw Dropbox" for not listening to us.