It is fair to say that MaidSafe have been fairly quiet in our communication of late, not a complete radio blackout, but certainly low key. This has been intentional on our part. Communication can lose its meaning and impact if you shout about every little thing. We like to keep our powder dry, as they say.
But, now we have something meaningful to convey!
I want to bring everyone who is interested up to speed with what we have been doing during 2015, specifically the past three months, which have been some of the most transformational in MaidSafe’s nine-year history. We do make weekly dev updates on the community-run forum, but these can be pretty technical, and not everyone can get a full picture that way. So I will try and condense these points into as limited an amount of technical language as I can muster.
Sure, follow this post…make a container and put some blobs in it.
The devs are going gaga over this stuff, but when you look at it…it’s just a bunch of blobs sitting in their own terminals doing bugger all…ignoring each other really.
I’ve included a highlights reel of the experience so far:
This is Pre alpha, and not useful, no code worth looking at.
@dirvine! Not useful?No code worth looking at? I wouldn’t quite say that about maidsafe_vaults, I had quite a fun time playing with it! Although maybe it isn’t actually that useful yet… the code still is pretty impressive for what it accomplishes!
I didn’t really do anything special with my droplet to warrant cloning it. Besides, with testing, you don’t want everyone to start from the same baseline, bugs don’t get found/solved that way.
Here are the steps I took to create a droplet:
Create a $5 droplet (I used debian).
Install rust from the command on their site, curl -sSf https://static.rust-lang.org/rustup.sh | sh -s -- --channel=nightly
Install git and screen sudo apt-get install git screen
Create a second non-root user account and su account-name into it.
Clone the git repository into a directory: git clone https://github.com/maidsafe/maidsafe_vault
Open up a new screen with screen.
Run the vault: cargo run --release -- --first
Take note of the port that the node is listening on.
Disconnect from the screen with Ctrl + a and then press d.
Wanting to start from same baseline to simplify trying again to connect.
Given enough eyes, all bugs ARE shallow but if they are all looking from the same pair of shoulders then its not necessarily true.
Your point is well made.
