This is what was really confusing me, but am I right @Sascha that such a
Skogsmard.html webpage was published before the alpha2 data reset a couple of weeks ago? is that what you meant when you said you had such a webpage? otherwise, it doesn’t make any sense to me as I don’t see any old entry in that public name (‘sascha’) that would have linked to such a file.
The public name ‘sascha1’, and both subdomains ‘nature’ and ‘test’ are correctly published, and I can see the websites published there without isues, i.e. safe://nature.sascha1 and safe://test.sascha, so that’s fine.
This is just as I mentioned before, when you created your WebID with the “WebID Manager” web application, that’s when the public name ‘sascha’ was taken (by you) to publish your WebID profile document. This is because you entered
nature.sascha in the “WebID URI” field, as you can see in the “WebID Profile Manager” screenshot you shared.
This application registered the public name
sascha and published your WebID profile at the subdomain
nature, and when you enter the complete WebID URL in the browser it fetches it, and it renders it using one of the standard serialisation formats (Turtle format) for WebIDs, as per the specification we are following: https://dvcs.w3.org/hg/WebID/raw-file/tip/spec/identity-respec.html#publishing-a-webid-profile-using-turtle
So, here everything is as expected, you published your WebID profile at safe://nature.sascha1 and when you query that URL with the browser you get the raw content of the profile in Turtle format (the WebID Manager webapp renders this content in a nicer way as you can see).
Now, the Web Hosting Manager won’t show you the public name
sascha for you to publish a website on it because we still didn’t make the WHM app compatible with the data format (RDF) used by the WebID Manager app, so eventually you will be able to publish a website on the same public name where you published a WebID but not just yet as we didn’t have the chance to implement it, that’s it.
This is the incorrect path to your webpages, the websites you uploaded with the WHM are at safe://test.sascha1 and safe://nature.sascha1
As I explained what you get is the content of you WebID profile since that’s all you have published at that URL, the other websites are at the other URLs I mentioned above.
The issue with the loading indicator is a known issue which has already been solved and it will be fixed in next version of SAFE Browser to be released. You can see more info about it here and here.
As per the these concepts of Public Name and WebID, considering what @happybeing already explained, what you basically did was the following:
- You used the “WebID Manager” web application to generate a WebID profile document, i.e. a document which contains your name, nickname, picture/avatar, etc.
- When you submitted that with the “WebID Manager” app, it stored the profile document on the network and published it at the Public Name
sascha, under the subdomain
nature, therefore it can be fetched using the human readable URL
I hope all this starts making sense to you