SAFE Network Dev Update - October 3, 2019

[Nadia]

Ah! I understand you now.

The SAFE Browser will always be the SAFE Browser. What’s we’ve done with this release is introduce functionality that makes the data perpetual.

But yes - I can see the confusion now in calling it the Perpetual Browser. Think we need to rethink that one …

Edit: One of the themes is Perpetual Web (not perpetual browser) so I think we need to be more specific going forward e.g. use the SAFE Browser on the Perpetual Web.

[goindeep]

I think this is a general issue Maidsafe have. They love the buzz words. Some of it works some of it doesn’t, mostly it’s just confusing and does nothing for the brand.

Maidsafe
Safe Network
MAID Safe Coin
Safecoin
Safe Browser
The Perpetual Web Browser
The Impossible Network
Autonomous Network

Did I miss any?

Not a massive thing but I just think it can be a bit confusing at times especially for new folks who know nothing about it. Maybe just confusing enough to lose them?

Edit: IMO this is a big deal considering the current state of affairs. Are we planning on making a bigger splash with this? This is Reddit and Wired front page material.

[Josh]

@Josh

Once it connects to the right section, it will become an Infant or Adult right away.

A new node can join as an adult?
I feel like I missed something major somewhere.
Or is that after relocation.

I am still struggling to understand joining as an adult, can you join as an adult if you were cut off/left and return?

[neo]

@maidsafe

In the new approach, we aim to offload most of the work onto the joining node. Instead of the Network negotiating where to relocate the node between themselves, the node is being directed by the nodes it contacts to connect to the right section directly. All communication is happening between the joining node and the nodes it connects to. If the section it connected to isn’t the right one, it will receive the Network addresses of some nodes closer to the proper destination. Once it connects to the right section, it will become an Infant or Adult right away. Then the section is free to perform any necessary checks, but that will be an issue for future tasks.

@maidsafe
Can some please provide a better explanation for this change.

It sounds like you are now providing a way for the bad actor trying to join the opportunity to choose the section to join.

Also are you allowing a node to join directly as an adult (in some circumstances.

[dirvine]

@neo

It sounds like you are now providing a way for the bad actor trying to join the opportunity to choose the section to join.

On new join of a node it is an Infant. It has no authority and will be relocated in time. So we don’t care they select their section as they will be relocated after a period (if they behave), otherwise we kill them. So as a node ages we trust it more, infants, well we don’t trust them at all

On ReJoin it must be known to us (have history and age) and we then also relocated and divide age by 2 as he went offline.

[neo]

@dirvine So to be sure the relocation after a period is done by the section and not some by the node
except the actual requesting to join the new section

[Josh]

@dirvine

On ReJoin

I guess I could have found the answer if I just looked a little harder.

Relocate is very similar to the Join process in that a relocated node is asked to re-join the network at a certain section. It must do that to maintain it’s age

[jlpell]

@dirvine

So we don’t care they select their section as they will be relocated after a period (if they behave), otherwise we kill them.

Is there any change that some ideas from @mav’s “Secure Random Relocation” proposal will come in to play? I’m mostly referring to the random placement vs. explicit section targeting aspect…

[dirvine]

@jlpell

Is there any change that some ideas from @mav’s “Secure Random Relocation” proposal will come in to play? I’m mostly referring to the random placement vs. explicit section targeting aspect…

That is a potential optimisation for sure. Right now we are implementing a direct random relocate decided by the section based on section churn events ( @neo ).

[edit what I mean @jlpell is this is getting all the machinery and tests in place to confirm the network infrastructure and like farm algo we can tweak with ease then]

[Nadia]

hmmmm some of those things you’ve listed are actually different things though:

• Maidsafe is a company, who are part of the community making the Safe Network (a platform).
• MAID Safe Coin - (actually just MAID coin) is the precursor to Safecoin
• Safe Browser is a product for users to browser content on the safe network platform
• The Perpetual Web Browser - is, as we’ve just discussed probably an error in naming
• The Impossible Network - is a title on one of the web pages
• Autonomous Network - is part of the longer description of the features of the safe network

For new folk it can be quite overwhelming - but at the same time this is a large and complex project, so there are bound to be lots of things to learn.

The aim of safenetwork.tech site and the primer is to provide that first level of support for our new, and long standing, community.

Based on your feedback however, I will go and have another look at the safenetwork.tech site and see how clear these are, and if there are any opportunities for further clarification.

[goindeep]

To you and I they are different. But you need to look at it from a noobs perspective. Coming in from a video, article, blog post. What does that talk about, where does it link to etc. Appreciate you looking at it.

[jaco]

https://www.instagram.com/p/B0Yo1wmhObB/?utm_source=ig_web_copy_link

[tfa]

@Nadia

The SAFE Browser will always be the SAFE Browser

In other words: the perpetual SAFE Browser

[Nadia]

hahahaha nice one!

[JimCollinson]

Like…

Mac OS: Sierra
Mac OS: Mojave
≡
SAFE Browser: Alpha 2
SAFE Browser: Perpetual Web

[Dimitar]

Great work Maidsafe devs! This is all going so fast… Almost as fast as I translate technical English, which I barely understand

I add the translation into Bulgarian in the first post
https://safenetwork.bg/safe-network-новини-3-10-2019/

[andreruigrok]

I do agree with Goindeep. It does get confusing for noobs when we throw around too many buzz words.

Keep it simple and instead of placing the focus on words like perpetual, autonomous etc, use them to describe the Safenetwork.

Safenetwork is your brand name and in my opinion by far the best name.

[SmoothOperatorGR]

totally agree.

maybe another first word for the whole system that will be unique and then we connect with it other titles of the sub systems

maybe “safe ecosystem” the main world that has inside:
-safe network
-safe browser
-safe authenticator
-safe mobile browser
-safe cli
-safe etc etc???

[andreruigrok]

Safenetwork and running on that all its applications i would say

[SmoothOperatorGR]

I would argue that safenetwork is discribing the network itself and not all the ecosystem as I suggest that there should be one title/word/s that would be key for noobs to relate to the whole project!