Here are some of the main things to highlight this week:
- We released the first version of the SAFE Network App.
- To focus on delivering Fleming, we’ve decided to delay holding a SAFE Online summit until after Fleming is released.
- The next SAFE Network Brighton meetup will be on November 21.
- We implemented a
dogcommand in the SAFE CLI as a companion to our lonely
catcommand. It will be part of our very next release.
We want to start with a quick update. Over the past few months, we’ve been discussing a number of different events that we were looking to put on in 2019. Over time, the format has changed somewhat - from a full-blown DevCon, to a Hackathon and then ultimately to an online summit. However, we’ve now decided to delay this event. There are a number of reasons behind the decision but ultimately it can be summed up like this: we don’t want any developers focused on anything that might impact on the timescale for the release of Fleming.
As you’re all no doubt aware, SAFE developers are working at capacity. There are some epic shifts being pulled across the teams to get us to Fleming. And as much as the Marketing Team in particular would love to run these events directly, the reality is this type of event is absolutely aimed at a developer audience. That inevitably requires MaidSafe developer input - and with the team at capacity, to take any of them away from crucial work to prepare content, rehearse talks and generally engage in the event in any meaningful way would have an adverse effect on the delivery of Fleming.
We’re all fully aware of how important it is to keep growing the community and spreading the story in the meantime. But delivery within the timescale we’re working to requires laser-focused prioritisation. And anyone following the project should, we hope, now have evidence of that approach in action over the past months.
It’s also worth pointing out how important it is to have Fleming out in the wild by the time we hold this event. We intend to make a major splash with the release, and the result of that awareness will translate into a much larger and more valuable event for everyone concerned - from community, to press, to team members.
Whilst this may be disappointing to some, hopefully you’ll understand our reasons. If nothing else, it should be clear just how important Fleming is.
Onto other news: this week, we released the regular monthly round-up which can be found over on Medium, a bit later than planned due to team holidays. We’ve broken it down into front end and back end key achievements, with a short update on all the fab work marketing have done this month (humble brag ). Of course, this came with a lotta help from the devs who have taken time away from coding to create tutorials, screencasts and podcasts (please note this essential work has shown us just how big an impact any potential event would have had on the team in practice). Give it 50 claps and leave us lots of lovely comments!
We’re also working with the team in Brighton and supporting the next meetup, so save the date of 21st November and get ready for an evening of SAFE chat. We’ll be able to announce speakers very soon, so stay tuned.
And a little Thursday afternoon treat for you all - we have the footage of the talk Dug did back at the Web3 Summit in August. So, here is @DugCampbell with Sam Williams from Arweave and Evgeny Ponomarev of Fluence Labs discussing perpetual data, network speeds and a world where data has no borders. Just to flag, the sound quality isn’t great but it hopefully gives you a feel for the Berlin event.
Vaults Phase 2
We have been continuing to make the changes necessary to run multiple Vaults within a single section. We have expanded the testing framework with capabilities required to simulate multiple Vaults running and exchanging the information.
We are starting to get the first good results: only 5 out of 39 internal Vault tests are failing in the multi-node environment, and these failures are caused by not having a consensus for some of the client request types. We are focusing on addressing this, and we have also started moving towards the integration of the real (non-mock) Routing library with Vaults. We are adding new APIs in Routing in order to let Vaults use Quic-P2P and PARSEC (which are used only internally in Routing for now), and once that is done, we should be ready to start testing Vaults and integration with SAFE Client Libs and real SAFE apps.
SAFE CLI (Command Line Interface)
The main focus during the last few days was creating a first PoC (Proof of Concept) implementation for having the Authenticator run as a daemon (we are calling it
authd). With the aim of merging all
safe_auth CLI commands into the SAFE CLI, and having a single CLI for all operations.
An API will also be incorporated as part of this plan. Thus any application (like the SAFE CLI) can easily communicate with
authd without needing to deal with the communication protocol implemented by it. We’ve made some nice progress and we’re currently trying to finalise some of the APIs to showcase a complete flow of authorisation requests/responses going back and forth between
authd and different applications.
We’ve also implemented some minor fixes in the last few days, and incorporated a new command for inspecting content on the Network. We already had the
cat command which allowed us to not only retrieve any type of content, but with the
--info flags it would also give us some additional information about the content and how that content’s location has been resolved from the URL provided. Given that in some cases (e.g. when retrieving the content of a large file) showing all this information together in a single command output is hard to inspect, we thought we needed a separate command for obtaining this additional information. Therefore, we’ve moved out this feature from the
cat command to a new
We thought that apart from needing a companion for our lonely
cat, the name
dog would also make sense as it helps users to understand how URLs, linked data, and the different types of resolutions (NRS names, files paths, etc.) are applied to find the location of a content being retrieved. Right now it just shows the same type of metadata previously shown by the
cat --info command. But we plan to keep evolving it to make it a powerful tool for inspecting content and linked data. This will be part of our very next release, but if you’re interested in learning more about it, a new section in the User Guide has already been added with information related to the
SAFE Network App
We’re happy to be releasing the first version of the SAFE Network App to all you wonderful people!
We recommend that all users uninstall old versions of the SAFE Browser from their system before downloading and using the SAFE Network App to manage the SAFE Browser. This will avoid any confusion over different versions of the browser existing on your system.
Here’s a video introduction to what it is, and what it will become over the next few weeks and months:
For now it’s limited to simply managing applications (of which we only have one… the SAFE Browser). But this is only the first step. Soon the SAFE Network App will be your gateway to so much more. We’ve already started working on the next releases which will bring proper update management for our applications, and more. In the meantime, this release will work on macOS, Linux and Windows.
As ever, it’s early days for the software, so any and all feedback/experience is super welcome and appreciated!
Note: For intrepid Mac folks who are already running macOS 10.15, you’ll need to right click > open on the
SAFE Network App.app to open it the first time. Previous macOS versions should work fine with the app signing currently in place.
Also, Linux users may need to make the
AppImage file executable. Do this by right clicking and going to Permissions.
SAFE Desktop Browser
After last week’s release, we’ve lined up some further fixes to the NRS resolution system, pinning down all relative assets to the current version of the site being displayed (previously they would be requested from the latest version which was both a) potentially buggy and b) not actually perpetual web-like).
We also sorted some other versioning bugs and have already added in a
XorUrlEncoder API for parsing/managing XOR-URLs and generating them from XOR names. We’ll be releasing this alongside more APIs once we have safe-nodejs updated with a new safe-api release!
SAFE App C#
This week we reviewed and merged the NRS API PR. With this PR merged, we now have all the new APIs exposed in C# from the
safe-api crate alongside documentation for these new APIs.
We already have some unit tests to ensure these APIs return the correct data from the SAFE Network, so next week, we will add some more tests to cover advanced scenarios and perform integration testing with the local, and shared vault. In parallel, we will also be testing these APIs for Android and iOS. Once all the APIs are tested on all the supported platforms, we will release a new NuGet package.
We are quickly tearing through the node age tasks in parallel with a pretty major clean up of code and functions that aren’t required in particular, connection management, candidate approvals and timers are all history.
As part of our journey, features were added to mock or fill a gap to certain parts of the network until the real features came in (such as node age etc). We also had connection management issues with connection security and transport, but the implementation of quic-p2p sorted that for us. So we’ve decided to do this housekeeping now during the implementation of node age and that meant quite a large refactor of tests.
In addition, we implemented Rust-based cryptography (which allows us to increase speed and ability to work on multiple platforms). The node age tasks are going very well and we anticipate completion there very soon.
The team will then focus on the remaining parts of BLS and fold up into Vaults to get them Fleming-ready. There will likely be more clean up and UX work in routing as we go through launch phases, but that is all good news. Exciting days now as we not only see the light at the end of the tunnel for the routing crate, but our foot’s already in the light
Feel free to send us translations of this Dev Update and we’ll list them here:
As an open source project, we’re always looking for feedback, comments and community contributions - so don’t be shy, join in and let’s create the SAFE Network together