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.
Please say yes, please say yes :)