Today we are releasing the second dev tutorial The new API functionalities of SAFE Launcher enable developers to build apps with dynamic content. To showcase these features we are providing a tutorial (again) that enables users to comment on content using their public name. This tutorial uses Public Appendable Data as opposed to the previous tutorial which was using Private Appendable Data.
The comments plugin we built can be added to any HTML page. In addition to letting people add comments, it also enables the website owner to delete comments and block/unblock users. The ability to block users is enabled by the
filter field of Appendable Data. For this tutorial, we use a blacklist (as opposed to a whitelist). Everyone except the public keys (people) listed in the filter will be allowed to comment (append data).
We are releasing this new tutorial as part of TEST 10. We had to start a new test network because the data that was stored with TEST 9 is incompatible with the new version of SAFE Launcher (this is caused by a few changes from
safe-demo-app). We are planning to bring TEST 9 down tomorrow.
SAFE Launcher now supports the APIs needed for functionality such as a comments plugin. We also had to update the SAFE Mail Tutorial app in order to make it compatible with this new version of SAFE Launcher.
Each client account is limited to 500 PUTs. A PUT is a request to store a single chunk on the network (a file may contain many chunks). The maximum chunk size is 1 MB.
Please be aware that this test network will be reset periodically, wiping all data that is stored on it. We will announce this in a Dev Update (when possible) prior to taking it down.
- Web proxy removed
- Low level api updated to match one to one with safe_core
- Only Rust logs are created. UI logs are currently disabled.
Enable comments on your SAFE website!
When uploading files using SAFE Demo App, the maximum file size is 25 MB per file.
- Reverse DNS specifier updated in package.json
- Updated service links on UI to
You need to use SAFE Browser in order to interact with the SAFE Blog example. The web proxy has been removed from SAFE Launcher.
An example of an email app skeleton to allow developers to pick it up and add some basic functionality for a fully working email MVP. Then add further functionality using the APIs described in this tutorial, to make amazing communication tools in SAFE. We have tried very hard to not make a user-facing app as we want developers to see this as a tutorial and know they have everything they need for communications apps in SAFE and a bit more.
- Updated to work with launcher v0.9.1
If you need help with anything related to SAFE Launcher or SAFE Demo App, please use the #support category on the forum.
GitHub is the best place to report issues and bugs. Using GitHub will help us (MaidSafe) manage issues and prioritise work within the Dev team faster.
- Report issues with SAFE Launcher
- Report issues with SAFE Demo App, SAFE Mail Tutorial or the Website Comments Plugin
We have started with the async overhaul of
safe_core using futures. This of course affects
self_encryption too and that crate has been updated to use futures and the async paradigm. Since futures is a very recent introduction in rust and is going through stabilization phase, we had to study the breaking changes and general design direction of it. With that we have coded a few proof of concepts and will evaluate and start implementation this week.
Disjoint Groups is underway. Fraser has started to integrate the new routing table code with the routing library.
Bart is the newest member of the MaidSafe team. He started working with the routing team this week, looking deeper into various consensus mechanisms and becoming familiar with our code and style. Welcome @bart!
The routing team is also starting to discuss RFC 45 – Node Ageing.
This is an RFC to prevent collusion and group targeting attacks and more. This also brings rank into the heart of the routing library and will make great use of data chains to allow the network to confirm node activities and behaviour. A slight addition is the ability to measure a node against a minimum resource requirement on joining and every relocation event. This takes us closer to handling less capable nodes. It does not address re-publishing data though, that is data chains.
As the team is growing and new people are “bedding in” we are continuing to receive and act on some very good resumes and the new funding will enable us to continue to aggressively recruit across all areas of the company. Engineering and developer outreach will experience growth, and we will also look to start building a channel management team (in time) to assist in fostering relationships with the company’s partners.
Of course the community and continuous improvements all help here, both in getting the name out and also helping us test incremental improvements.
As you are all aware the BnkToTheFuture round has just over a week to go and we are over the minimum requirement. Your continued effort in raising awareness of the campaign in the last 7 days would be very much appreciated. While it looks like we will fall short of our target, we should still do everything we can to maximise the effort and work put into this funding round. The recent news regarding joint ventures shows our intent to “partner to grow”. This is a lot of work, but we believe that it is a very effective route to market and one we will be spending a lot of our efforts on in the medium term.
Thanks you to all that invested, supported and helped out with this round. As usual we are humbled by the selfless time and effort that so many of you gave, it is noticed and very much appreciated!