Safe network dev update – november 29, 2018 – updates – safe network forum electricity billy elliot lyrics

###########

Big news this week that you might have heard about – with the SAFE Network logo appearing in the new #1 US film hit, ‘Ralph Breaks the Internet’! Props to @nigel who first spotted it and @Harvindar who got some photo evidence. Last night the story started to be picked up by the press. We’d love to find out the connection so if anyone knows, please give us a shout!

The rest of the week for marketing has been focused on work around messaging (more on that to come soon), producing content around Dynamic Membership in Parsec (ditto) and content strategy for the new newsletter subscription list (reminder: you can sign up in the footer at https://safenetwork.tech/). We’ve also been working at improving the video work for the weekly updates. Real progress this week and you can take a look at the improvements we’ve made by checking out this unlisted video if you’re interested. electricity dance moms choreography We have a few further things we’re planning to do over the next couple of weeks to raise the quality even further but hopefully you’ll agree that the production values are improving. We’re keen to invest more in video updates moving forwards of various types – so the foundations we’re laying here should stand us all in good stead.

The safe_app_java repository now includes the code comments from which the Javadocs will be generated and published. safe_app_csharp was updated to support x86_64 for Android along with the API being updated to safe_app v0.9.0. Improvements were made in handling error messages on the Mobile Authenticator. With the API stabilized and the tutorials falling in place, we are currently standardizing the project management processes, before we start planning the final testing and release process for the C# and Java APIs.

A new version of the safe_app_nodejs package (v0.10.0) has been published this week on npm, which incorporates some enhancements mainly around the experimental APIs: they are all now exposed behind a flag so developers and users can use them at an early stage, while being explicitly aware of the fact that they are still in an experimental stage. Please refer to the changelog to see the complete list of changes. The following is a summary of the highlights of this release:

We have also upgraded safe_app_nodejs to v0.10.0 and safe_authenticator lib to v0.9.0 in the SAFE Browser, which enables all the experimental APIs in the DOM API to be exposed. electricity rates el paso We’re working on allowing users to have the control to enable/disable them for the use of web apps. We are now trying to finalise this functionality and doing a lot of exploratory testing to be able to release it soon.

There has been a lot of work also going on around the automation of tests for the SAFE Browser, which will help us a lot to assure that changes made don’t affect the existing functionality. gaston yla agrupacion santa fe 2016 We are planning to keep working on enhancing this in the next few weeks, this is one of the main enhancements we’ve been working on in the last months on the browser. As part of this effort, we are trying to move away from AppVeyor onto using Travis for all platforms (Windows, Linux and macOS). SAFE Client Libs

While using Rust libraries is always a better choice because of better security guarantees, we haven’t found libraries implementing the RDF standards completely, and at this point it is not feasible for us to produce them ourselves. Instead, we decided to focus on implementing basic support for SPARQL queries and triple storage on the SAFE Network as quickly as possible. Then we can start testing RDF-based apps and the ideas from RFCs proposing an RDF-based replacement for DNS. And with simple demo apps, we can iterate on these features further, providing better performance, having better API design, and more complete and seamless integration with the SAFE Network.

One simplified the configuration of the input to the consensus protocol. gas zombies Instead of giving routing the full configurability of a custom function, we now only expose a choice between a couple of options. Like any API improvement, it makes our interface harder to misuse while maintaining a sufficient amount of control over the crate’s behaviour.

Another one added a method to indicate which peers are ready to receive gossip communication from a given node’s perspective. Prior to the change, routing would just try any node it knew about until one of the communications succeeded. h gas l gas This approach is simpler and more expressive. It also help us make our tests more robust as we can now verify that nodes that should be able to process our communications.

We kept looking at various forms of Malice and systematically improving Parsec by making it able to deter nodes from engaging in these malicious activities. We implemented detection of Spam malice. That’s when a node deliberately sends us more information than they know we need to incur extra-work for us. We also have a number of changes that should make it into master in the coming days.

@pierrechevalier83 also did a presentation about the synergy between the Rust programming language and the MaidSafe values first to an audience of Rust programmers on Tuesday at the Rust London User Group Meetup, then to a SAFE Network enthusiasts audience on Wednesday at the SAFE Network London Meetup. The slides from the talk can be found on GitHub. electricity voltage in india Both talks were filmed and the videos should be available shortly. Crust

@povilasb took 3 days off to take a trip to Rome to visit the RustFest conference and exchange ideas with fellow Rustaceans. Now back, he’s been solely working on the development of socket-collection. We finally merged the encryption changes. Now different crypto contexts can be passed with socket config structure when constructing UDP or TCP sockets. Also, socket-collection now encrypts the packet header as well, which is just the packet size currently. Now at this point, all the data on the wire will seem absolutely random to the observer. We also added more UDP tests and expanded the docs. Eventually, we introduced the socket trait which will abstract TCP and UDP sockets and reduce the duplicate code.