A_A

solid-file-client is basically a wrapper for solid-auth-client which makes working with files on pods easier. It doesn't handle authentication (login, sending authentication headers, etc) itself, but forwards this to solid-auth-client....

The problem is, that `deleteFile` is currently defined like this: ```javascript async deleteFile (url) { return super._deleteItemWithLinks(url) } async _deleteItemWithLinks (itemUrl) { const links = await this.getItemLinks(itemUrl, { links: LINKS.INCLUDE...

@jeff-zucker @bourgeoa The `deleteFile` method currently doesn't accept an option parameter, while [the docs](https://github.com/jeff-zucker/solid-file-client#deletefile-fileurl-options-) say that it has one. So either the docs, or the method should be changed.

> So, you are telling me that the deleteFile() method is guaranteed to fail if the user does not have Control over what they are deleting even if no .acl...

> So itemExists(foo.acl) will error with 403 if the user doesn't have Control? That's the general behavior in NSS: If I wouldn't have the permissions to view* a file, I...

> This means that I’m with Jeff and Otto-A option 3. This is actually my least favourite option, because the method then depends on some user settings and therefore is...

> Also, whatever is decided about deleteFile(), I will write a description of how Control/Write permissions are handled to add to the README. This is definitely a good idea. And...

> your examples are not to the point [...] Again - under what circumstance would someone create foo.acl for a file foo and give Write but not Control specifically over...

Regarding your wac-allow solution, my initial hesitation with it was, because I'm not clear about the status of it. I've created an issue about it one year ago, apparently it's...

> This is not true as you can in the following picture. I've recently started my Inrupt POD and by default these are my permissions (never changed them): I think...