We are working in several parallel tracks right now. This week we will share the next iteration of binaries and invite the community to partake in TEST 5. We were aiming for today, as per usual, but there are a couple of “niggle like” loose ends to clean up. We anticipate these will resolved and we will be ready to release TEST 5 tomorrow, assuming all of our tests are ok. There were a few large changes here, so we want to make sure it’s not a wasted test.
The purpose of this network will be to test specific aspects of SAFE, one of which includes improved data persistence. This involves disabling the ability to run multiple vaults per LAN, as well as re-implementing immutable data caching (this was turned off in TEST 3). These tests are very important and have been incredibly valuable, we really plead with the community to not attempt to disable the switches we have set here. This is of huge importance. We are still chasing down the mechanism to handle very low quality nodes, both in terms of measuring these and also having them stopped or relocated. We appreciate any input on these matters as we continue the testing.
Another track, as you know is the Community Engagement Project. We had hoped to publish the proposal request for the SAFE browser today, but time has beaten us. We hope to publish this proposal this week though.
We are also considering some further funding options in relation to MaidSafe itself, which hopefully we will share in the next few weeks / months. We cannot publicise all negotiations, but will endeavour, as always, to keep you as informed as is feasible. It is fair to say though, that there are some options that we feel will again benefit everyone. We are also trying to ensure the current exchange issues in China are being co-ordinated with tech support from the Omni team. The issues experienced are more process driven as opposed deep underlying technical issues.
The client apps, including launcher, are also seeing larger improvements in the background. These improvements are all aimed at providing much more efficient and clear feedback to users. The community really has helped to show a clear path here and allow us to effect the designs required.
##Crust, Core: Andrew, Spandan (tl) & Vinicius.
Core now does error recovery for composite operations. For example, if Operation A required 2 PUTs to succeed and due to some reason the 2nd PUT failed, the user is informed (correctly) that operation A failed. This could be because the network was disrupted between the two operations. Now when the user retries A, the 1st PUT itself will fail because it had succeeded the last time. So the user is deadlocked and can never perform operation A again without changing some parameter. Now with the recovery mechanism in place
Core will check if the PUT failure is due to the data being already present and if so it will further check if we are the owner. If all conditions are satisfied the code will declare that the current PUT in that composite operation has succeeded and will proceed to the next PUT and finally return success for the entire operation A.
Core also provides facility to extract stats on number of GETs/PUTs/POSTs/DELETEs performed.
The team have also completed other refactors relating to Clippy errors and general code hygiene.
##Routing, Vaults: Adam, Andreas (tl), Fraser & Qi.
We have reimplemented caching, made the chunk store directory configurable and improved the reproducibility of our unit tests. We are also continuing our spring cleaning: reorganising our code and updating some neglected parts of the documentation to get everything into a better shape for future extensions.
##Client : Krishna (tl), Scott & Shankar.
The tasks which were planned as a part of implementing v0.5 of launcher have now been completed and we are currently testing these updates now. The NFS API has been refactored with support for streaming. Encryption and base64 conversions between an app and launcher have been removed along with a few other minor updates. The demo application has also been updated to work with this latest launcher version.
We have not made any UI or UX improvements in this version because @scott is working on a new UI (mockups will be shared to the community soon). Since there is a new UI planned, spending time improving UX on the present version would not be the most efficient or effective use of limited resources within the current Client team. The new UI will introduce new features such as launcher analytics and user statistics.
For this coming week, we will release the v0.5 of launcher and continue working on the new UI for launcher.
We hope you enjoy TEST 5 this week and thanks again for your continued support!