SAFE Network Dev Update - March 14, 2019

Great update Maidsafe devs + marketing team,

Love the interview with Jim especially the down to earth simplicity. :+1:

I’m not sure if this would help on the SAFE Network but here goes…

@happybeing this was literally the first video that I saw this morning on another site before coming to the forum :rofl:

Keep up the good work and have fun


Could do with less jargon and/or hover over long form for the likes of IPC…


The link to ‘FFI calling conventions’ in the Client Libs introduction pages redirects to the home page.

I agree; I think the libraries should separate concerns. It feels like RDF is another layer in the OSI stack, so that makes it sensible to be available as a separate module. I also think NFS should be a separate module. These kind of ‘standardised conventions’ could also include DNS (PNS). I would imagine a lot more conventions will come up that might have no place in the same library as the core one.

From my experience that makes maintenance and testing easier, and also explaining the usage of libraries. Seeing it as a stack of dependencies makes it clear what relies on what. It eases documentation too.


Thanks all for the feedback - all very welcome! Like Sarah said, we’re not professional videographers or interviewers and this series is designed to be very informal and casual. But we do take your feedback on board. We’re planning to film again this afternoon so i’ll try keep from nodding too much :joy:


Will keep this in mind, we want this introduction to be approachable for everybody, but sometimes we developers may not even realize we are speaking jargon :slight_smile: Are there any specific examples of things you didn’t understand?

We have yet to upload a lot of the pages, and there will be some broken links for the time being. The page you mentioned will go up in the next week or so.


The ideal form for introduction to anyone, would be to assume no acronyms or contractions… expand first instance of each. Even Client Libs could.should be noted is Client Libraries?.. if I knew nothing, would it all parse?.. so, first instance of Rust is Rust Programming Language, with a link out perhaps to what is Rust wiki somewhere nice and easy. If it’s all soft and squishy then it’ll be like quicksand and suck noobs in… exciting them that they understand it all! If you want to overdo it, there are tools to measure reading age, which for the current perhaps would tempt moderate techy awareness required… depends the audience how much you need to spell out. For me it’s fairly good as is.


Excellent, thanks! I’ll note down your points, we’ll revisit the intro next week and make it squishier :smile:


@mav, thanks for your feedback!

Yes, we’re also strongly in favour of this option. Even just from the sheer complexity standpoint. E.g., while querying encrypted data in Vaults is theoretically possible, it would require mind boggling tricks and considerable effort to achieve that.

Yeah, it definitely is, in a sense that you would surely be able to use primitive data types (ID/MD/AD or whatever) and store arbitrary binary data on the network. But I’d say RDF should be strongly favoured for structuring apps data, albeit this approach might seem opinionated. It’s important to make RDF/Linked Data as ubiquitous as HTML though, because implied possibilities are huge: S in SAFE would stand not only for Secure but also for Semantic. :wink: That’s why we’re considering basing some of the core Client Libs abstractions (like NFS files/containers) on RDF too.

That’s a very on-point comparison and I think in the same terms. RDF is intended to be low-level and it should not be necessary for developers to learn all of its intricacies. I presume app devs would use higher-level abstractions and APIs, relying on JSON-LD and implicit schemas – something like @joshuef presented a wee while ago in or


excited to read the updated PARSEC paper (although won’t understand it :blush:).
Good call to go peer-review IMO, this is cutting-edge computer science after all.


Are not you putting all the eggs in the same basket by doing that, taking into account that quic protocol can be “easily blocked” by ISP’s / governments?

It shouldn’t be better add quic to the network protocol stack and integrate it in dynamic connections implementation as a one more protocol available?

What am I missing here?


Or you could drink some wiskey at the distillery at the foot of the mountain before making a video, like I did a couple of years ago (the drinking part) :wink: Btw the people at the distillery also don’t like to make videos, it seems. They showed me this dated intro video, older than any wiskey you could buy there.


It’s Friday. I’m not quite able to read or take in any other text. This… good advice.


Great update as usual.

Thanks to the team for keeping the fires burning. I’m certain the video’s will get better as time goes on - it took me nearly a year of making one every week to get my audio decent! [ embarrassed ]. I appreciate the informal approach of the interviews and discussion, so IMO and as others have pointed out, it’s just going to be a process of developing the A/V techniques to make great media and being careful to dumb it down so that the grandparents can understand at least the general ideas of it.

Have a great week Maidsafe team!


Just like any brand new radio show, TV series, even for professional broadcasters and actors it takes a little time to ‘wear in your shoes’. I’m sure we have all noticed it.

That embarrassed feeling, just natural nerves - just stage fright. All listeners and viewers are looking out for is that you are having a good time up on stage.

I look at my early android tutorial videos and I see myself trying to do what I thought a video tutorial should sound like - acting. Nah - just stick up a camera, and talk as yourself, with background noise if you have it. A lot of popular YouTube stars do just that.

Keep making videos.


I still remember your excellent intro to SAFE video. It was top class, and essentially just you talking while showing in a clear straightforward way.

So I think your advice is good and your own output backs that up. And I hope you’ll do some more SAFE videos yourself one day!

I hate doing that stuff, but will have a go again at some point if I have to (hint). For my DevCon presentation (which was a pre recorded screencast) I did several retakes which makes it time consuming for me - that was partly to get within the time limit, and because I had to record the audio separately though.

Soon I’ll have something that will make a great screencast demo I think - short and simple, but powerful.

I’m waiting on a couple of changes to SAFE Browser and some bug fixing in my code, but I think it will impress and reach people we are keen to have join us at this stage.

So @Zoki, if you or anyone else fancies playing with this and making a screencast for it PM me for details.


A big thanks to the Maidsafe team for coming to Brighton - was great to meet yourselves and others in the community.


The next HTTP version, HTTP/3, will be based on QUIC. So when it goes mainstream, SAFEnet traffic will seam undistinguishable from HTTP. If ISPs were to block QUIC, they would be blocking HTTP as well, which probably is very unlikely.