The SAFE Network backend

[happybeing]

Information continues to leak slowly about the SAFE Network API that will have a big impact on how SAFEpress works. Because this is clearly a big deal I'm holding back on my work to define how we'll store and update content, because its looking increasingly likely that the network will do a lot of the work for us.

So we should for now I think focus on the front end side of things: prototyping the CMS UI, and the SafePress Dreamcode API, and any other front-end framework stuff which you fancy writing up ideas for and/or mocking up.

In the mean time, if you want to get an idea of why I'm both excited about the network API and frustrated not to have the details, take a look at the following from the SAFE Network forum:

What we will do (and have done this sprint) is supply a dns type for registration of services. It' just an SD using Put Get etc. that's all. A purpose was to start showing how to use the SD types for different things. Then there is an SD type that holds directories for users. A user can have 2^512 directories and all unique to that user. That's another SD only (data part encrypted). So an enumerable data structure, a disk if you like, it can be public (non encrypted data content but signed (we have implemented these to :)) So enumerating public and private dir types as SD types using Put Get Post so far.

So we can show enumeration and protection of an SD namespace if you like (this is Spandans RFC coming that provides collision proof SD's)

It's so simple it's almost invisible to see

What we need to be able to add is append-able data types, to make blog comments even easier, but that is an RFC for sure, for now it can be done using the tools we have. It's just a matter of selecting your type of SD for clogs and link somehow to comments (in my example I used the blog ID as the entry point for the comment SD type, using the blog ID as the identifier and the version of the SD as a comment identifier) This will be made very much more clear soon.

Krishna and Viv have done some stellar work on the front end planning, so implemented node-wm and found deficiencies and now switched (in just a few days) to the electron libs (atom back end). When that's all up and running (now the stabilisation sprint will happen) we can not only explain how to do this but also just fire together a blog + comments app and shove it in examples. It should take us literally a few hours to do that I think. (I discount all the front end niceties, that is beyond my mechanical brain )

Ref: David (today), https://forum.safenetwork.io/t/deletable-data-and-secure-uses-for-structured-data/4764/87?u=happybeing