MaidSafe Dev Update - February 16, 2017

[davidpbrown]

Yes, I don’t want to nit-pick, given the assurance received above but just to point out the difference levels of comms that find traction…

@nice

I think I found quite some insight here :

@frabrunelle

Added to that, the refactor of SAFE Authenticator <snip /> This will enable devs to build apps that communicate directly with the SAFE Network, without the need for an intermediary such as SAFE Launcher

but then such qualifier as “We will be integrating it with safe_client_libs to expose the SAFE API to Node.js developers.” in the paragraph that followed shortly after:

@frabrunelle

We are starting the FFI integration with safe_client_libs. Also, we are creating a new Node.js module called safe_app. We will be integrating it with safe_client_libs to expose the SAFE API to Node.js developers. Devs will be able to install safe_app from the npm registry and use it as a dependency for their apps. The example app will be using this Node.js dependency to connect with the SAFE Network.

Suggested to me less than generic interface… where REST is generic… anything can call a request and get a response.

Anyhow, understanding now that Node.js developers is apparently everyone, even those who struggle to install npm correctly.