A_A

> Good point. I absolutely agree that untrusted agents should not be permitted to write HTML/executable code to a pod. This not something that solidos can solve alone, so an...

Yes I think this feature case is clear. I also think that tackling this iframe issue is not the priority for now, it's rather one thing to consider in the...

Would it be possible to create a proxy where the url is inserted at one specific place in the proxy rather than the end? I don't have a particular use...

Documentation is pretty good, seems like I've just skipped this part -_- Nonetheless, what do you think about a warning in such a case? Or is this something that is...

And is client.disconnect() mandatory or can I just let the program exit without calling it?

Using `with client` seems hard to do, as I store it in the config file so it can be shared across main.py and message_handler.py I can do it with `atexit.register(clean_up)`...

Regarding putFile: I think it depends on how much custom logic you want. If `updateFile` would only forward to `putFile`, then why not directly use `putFile` and remove the alias?...

The reason for this suggestion is mainly, that #140 and similar features would be easier to add once solid-file-client supports a common traversal method

I've looked at it again, and realized that AggregateError is conceptually different than our implementation. When we throw in `copy`, we provide information on what requests failed and what requests...

I think the submitFile and submitFolder methods are a good solution for this. Maybe also add in the documentation the required permissions for each method/option. You could also consider, that...