Why did you have to build yourself? You can use one of the old builds of WHM to create public id and upload an app built for old or new API. The only thing that won’t work with that is the WebID PoC because it needs to use a different structure for public names.
I did indeed not build the WHM.
But I did build the web API playground 3.0 to be able to test/get familiar with (in mock mode) the web API changes, introduced in Peruse v0.6. So that I could port safe://todo, not WHM.
We’ve been talking about all this in the last few days as we noticed it was becoming confusing, and we are already preparing the new release of WHM v0.5.0 and Peruse v0.7.0 (they are in QA/release stage already), they both will be the suggested versions.
In the meantime, the suggested versions should be:
- Peruse v0.6 which contains the new DOM API, and the Peruse WebID-PoC version which contains new DOM API plus the WebID switcher needed to play with Patter and WebID Manager.
- WHM WebID-PoC version, and v0.5 when available hopefully in the next few days.
Beaker browser v0.10.2 should be discouraged for new development of apps.
Thanks Gabriel, you don’t say it so I think it needs clarifying: WebID PoC WHM for WebID PoC Peruse, but doing so will create public names that are not compatible with the other WHM, or with apps which create their own public names. So best to use different accounts for one or the other.
Correct?
Not exactly like that. The WebID PoC WHM doesn’t create public names or web sites with new format (RDF), it just deals with it to ignore those type of entries (RDF entries) in the MDs. Thus you should see any new public names you create with it using previous version of WHM.
As per other apps that read the public names, they need to handle/ignore the RDF entries (like the WebID PoC WHM does) otherwise it’s likely they won’t work, e.g. the email app was not yet adapted to support this, and I guess some app/s created by the community fall into this group as well.
Thanks, I now know what i need to do.
Will or can the WebID replace the Email ID?
I think it can, I personally think it should, and I personally hope it will
The way I see it as ideal is that everything is linked form the webid (or “safeid” we should have our own name for it), you share a webid with your contacts, and that’s what they use to discover everything about you, inbox, coin wallet addresses, blog urls, websites you reference, friends, etc. You can update that at your will, they never realise or need to know when you do it, apps automatically discover it when fetching your webid. Plus, you can have several webids, one for your business, another for sharing with friends you make, maybe another for only close friends and family/relatives, perhaps anonymous webids you use for trolling
…etc.
Once I gave you a webid, I can then simply ask you to send a payment to me, check my blog, or to send me an email or Patter message, without needing to give you any more info, you already have my webid in your contacts list, that’s it.
I’ll change in the OP my (lonely) Email ID with a WebID (SafeID) then
I’m getting this when opening the Peruse WebId PoC
Ubuntu 18.04
@mods feel free to move this if there is a better place for it
I think here is fine. Further questions are maybe better asked in the following topic: Creating your WebID on the SAFE Network (Alpha-2)
Added your and my SafeID in the OP.
@southside this is a known error (we’ve a fix, but not yet released in a new browser version).
It basically happens intermittently, so if you see it, for now simply restart the browser and try again. (It could happen a few times in a row, if you’re unlucky). That’s the workaround until the latest version of the browser is out the door.
Just to expand on this a bit more, @happybeing (and @bzee or any devs):
Any app adding/removing/parsing MDs should really also be doing some validity checks on the data, as there’s no way to be sure that another app hasn’t added another key/value to any MD which could break your parsing.
It’s not something you naturally think about, but apps will have to do as they no longer ‘own’ the data as they do on the clearnet.
However, this is another advantage to RDF though, as you can more easily check that the data you’re receiving fits your schema or no (and act accordingly… [ignore/check if vocabs can be useful etc]), which is nice.
How do you create these one word resources?
safe://cyberpunk test video
How big is this community, and how many things have been developed specifically for it? I’m intrigued
You can create such one word resources by choosing www as a Service Name, so safe://www.cyberpunk = safe://cyberpunk.
safe://eye.eye is of course not a one word resource, but 2 times the same word.
Ps: Chrome 69 Removes WWW from URLs.
so thats how its done…
That was bugging me…
This link seems to be incorrect.
Thanks @happybeing, I just updated it with the correct link
@SaraPentland is there a list of the MaidSafe demos currently working with alpha2? Might be good to link to them from the OP here, and from there to this list as well.
For reference I’m aware of only the following Maidsafe supported resources on alpha2:
- WebID Profile Manager demo safe://webidea.ter (requires Peruse WebID PoC)
- Patter demo chat safe://pat.ter/ (requires Peruse WebID PoC)
Anyone know of any others?