Sorry, I don’t have time to look at your app right now. The only thing I’m pointing out is that, since the spec doesn’t say anything about specific paths on the server, the only way to reliably know what “their base URL is”, is to look for the pim:Storage link. see Solid Protocol and Solid Application Interoperability.
I took a look at those, links, thanks. Have to say I’m a little confused. Those linked docs are not really clear to me. I’m not sure of the series of operations I need to take to generally establish the base URL to use.
From what I can tell, this comes back to the title of my question about the URL to use when making a request. My approach so far had been to take the host component of the the user’s webid, and use that as the base URL when making requests. It sounds like that’s not general?
No, unfortunately it is not general. The ESS server run on inrupt.com uses URI’s of the form https://pod.inrupt.com/username/ … so the host component root container does not belong to any username and is not writable.
OK-- thanks for making this clear. Hoping to learn more about how to make progress with this.
Currently, it’s a lot of work writing Solid apps :-). But don’t get discouraged. Here and the app-developers chatroom are good places to ask for help.
I’m not discouraged, thanks :). I’m very excited about Solid. I’ve been working on concepts of user owned data for years, and to finally see some broader community embracing these concepts is incredibly exciting 
1 Like
Great! I look forward to having time to check out your app.