After logging in on a server (let's say https://localhost:8443/), the user is presented with this page:

This can be confusing, as there is nothing the user can do here.
I propose to either:
The answer depends on where you log in. There are actually very few use cases for "arriving on pod.com" and then logging in. I mean, those cases exist now, but I don't envision them in the future.
While I like the idea of a link to the user's homepage, what exactly is that? Because you might be signing in on pod.com, but your homepage is my.com鈥攚hy did you sign in on pod.com in the first place? People should be directed to the page that aligns with what they wanted to do.
Right, but then I suppose we should have a few links on the page by default, so that there are some breadcrumbs they can follow?
While I like the idea of a link to the user's homepage, what exactly is that?
My proposal is to add a 'My Pod' link to the index page, in cases where people navigated to for example solid.community, and logged in from there. The target of this link would be the solid:account value of the user's profile. (We would need client-side RDF parsing for this though)
Since there are no further comments, I say go for it :-)
Most helpful comment
My proposal is to add a 'My Pod' link to the index page, in cases where people navigated to for example solid.community, and logged in from there. The target of this link would be the
solid:accountvalue of the user's profile. (We would need client-side RDF parsing for this though)