Mini Status Update - remoteStorage speaks SAFE Launcher!

[happybeing]

SAFEpress Mini Update - 16th May 2016

I had a mini triumph late last night and want to share... :-)

All I did so far is send an auth request to the Launcher and receive an "Unauthorized" response. But that's after much help from @raucao of the remoteStorage team helping me figure out what the differences were between node.js and pure (in-browser) JavaScript coding is about, and how to use their rather antique build system (I was only one edit away from that working but ... needed the crucial second pair of eyes to help me find it :slight_smile:)

So what what has been achieved so far:

• a SAFE Network backend loads in a sample App and the user can choose to try and connect
• when they do it sends an authorization request to the SAFE Launcher which responds "Unauthorized" (because there isn't a network I think). I copied the MaidSafe /auth example code (link below) and adapted from node.js to pure JavaScript. I posted a summary of what I did on the remoteStorage forum.
• I included libsodium, and had to find a replacement for node.js Buffer (the MaidSafe code uses both). Later I'll try to do without libsodium as it is a whopper, but first I want a functioning remoteStorage backend.
• I had to configure the remoteStorage build system to include my code and the libraries I needed. And all this without breaking the remoteStorage build system and test suite :slight_smile:

I'm crowing about this because I'm new to the whole JavaScript ecosystem. If I can do this, there's a good chance others can, and I may now be able help out when people are stuck.

I pushed the code and you can view it here. I recommend viewing only while wearing sunglasses :wink: If you look carefully you can see the small section that corresponds to the MaidSafe docs /auth example code. Very little else in that file is real or working, just a copy of a totally different backend for Dropbox.