Hey! I've watched some of the videos on all of dropbox's other apis and think I have a pretty good understanding about how developers would use them. I'm a little fuzzy on this one and was wondering if you could give an example or two of how a developer might leverage this.
There are a bunch of different use cases we have thought about.
Perhaps my favorite is a mirrored workspace. An app like Asana could use the Shared Folder API to create a Dropbox shared folder that mirrors an Asana project. As you add or subtract users, those changes affect both. Similarly files added via the Dropbox folder appear in Asana and files added in Asana are instantly put into your Dropbox. A video conference has similar concepts.
But there are tons more and we'd love to hear ideas from other folks!
I am not sure if this is a share API feature, but it is a problem I am struggling with.
We have an app using sandbox app folder(we don't want to mess with user's full dropbox file system), but then problem is that users can not cooperate within a share folder.
Here is what I'd like to have: A user shares a folder within app folder, then when another user accepts the request, then 1) keep the same name and same path strictly, create intermediary paths if necessary; 2) don't proceed if conflicts happen.
Please let me know if it is already doable in current state.
Unfortunately, as you noticed, it is not possible to share folders within a sandboxed app folder. We plan to remove this restriction in the coming months.
- You can't share an arbitrary folder with someone, only a top-level one
- You can't share app folders
- App folders are buried in the Apps folder (duh). So, you can't use an arbitrary one with an app
Does this address any of these? I think all three issues could be really elegantly solved like this: do away with the concept of an app folder, and similarly with the top-level sharing restriction. Instead, give me an access control dialog for any folder. This would let me share with both apps and other users.
> - You can't share an arbitrary folder with someone, only a top-level one
You can share any folder arbitrarily deep. What we do not allow is sharing subfolders of already-shared folders.
> You can't share app folders
We plan to remove this restriction in the coming months.
> App folders are buried in the Apps folder
We are exploring how to better handle App folders, but the sharing API will not address this.
> This would let me share with both apps and other users.
Great point. Note that apps with full Dropbox or file type access already can share data with each other, just not two apps with only App Folder permission.
Are there specific (App Folder) apps you wish to share content between?
I'm a huge fan of Braces (http://braces.io/). It solves the how-do-I-get-my-site-files served problem perfectly. But I'm also a huge fan of Dropbox sharing, and it's sad that I can't collaborate on my Braces sites with my friends.
Brace.io dev here. We're working on Brace Teams which provides collaboration features (and currently requires full dropbox access). We would be happy to let you try it out. I'll send you an email.
Also you linked to our not-so-secret staging site. We'll be putting up access restriction there soon. Please use http://brace.io.
Yep. The only thing required for the form is an email so we can get in touch with more stuff. For folks who already have apps we are curious what they are. Also we'll eventually use the App Key to grant access to folks for the beta.
I wanted this natively supported for ever. For now, I use Hazel* to sync every change inside an dropbox folder into an app folder. It works, but you know...
May I ask what app you are using? It seems that the app has been set up to use App Folders, when, for your use case, it could be using the more liberal Full Dropbox or File Types permissions.
This is supported while someone is an in the invited state, but the initial version likely won't support full auditing to answer the question "How did user X become a member of this folder?", though this is in our plans. Could you explain your use case?
> Who updated something shared?
Yes. And each revision in the revision history will include information on who updated the file.
Thanks, I think your second answers covers my use cases. Let me explain them:
Currently, file's metadata has no ownership information. If I see it in my files or my deltas, it could be because either I created or somebody else created them in a shared folder or somebody else shared a folder with me and i accepted.
In other words, if user X adds a file to a shared a folder with user Y, when User Y requests for deltas from the API, I cant tell if the User Y is the creater of these files.
It looks like Id be able navigate the revision to figure out who created the file. or who placed it in the shared folder, so this api is certainly a welcome addition
That's great news, especially the answer to the second question. I would use this information to give give users a better to see what happened to their shared folders (who changed what etc.)
Do you have any plans on extending the /revisions call so that developers can determine whether the file was restored/added/edited/deleted?
This is quite difficult or impossible (edited or restored) at the moment.
