Daniel Friedman

I'm not sure if this issue is only about Quads and Terms, but I'd also like to mention that I feel strongly that the Dataset, whether or not it is...

It's quite possible that one would need to use different headers on each request.

The interface you export in `solid-client` prevents the developer from "setting up the web client (including whatever custom headers) once", since it [actually injects the web client into the profile...

> Which means you can override it centrally, once, and that propagates to the various components (like the profile-related functions). No, you can't, not the way this is currently built....

> @dan-f not at all suggesting that. They can customize the web client directly from the solid-client instance, like solid.web.whatever = ... [No, they can't](https://github.com/solid/solid-client/blob/master/src/index.js#L69-L80). The closures you set up...

Good idea! Could you help me by providing two details? 1) From what I can tell, all the necessary interfaces that the exported `fetch` makes use of are available in...

Ah I see, the problem is `localStorage`. Odd that indexedDB is available, but not local/session storage. > Exactly, and this also involves fetching that data. > ... > Not for...

So after discussing, it looks like the smoothest way of accomplishing this (minimizing API changes) would be to swap out localStorage for IndexedDB. That way this lib can be easily...

More catchup from offline discussions - we're moving towards augmenting the `storage` API within this library to return promises, rather than immediate values, in order to allow implementations of the...

@RubenVerborgh I think this should be supported with the changes that landed in #24 (by constructing an async storage interface on top of postMessage). At some point, would you be...