MaidSafe Dev Update - September 14, 2017

I want to add that the bug that was blocking me and some others has been fixed in the update of SAFE Browser to 0.5.2, for example, @Joseph_Meagher’s chaty, listy, viddy etc apps should be working much better now I think, but I’ve not tried them because… my code is now able to authorise with SAFEnetwork and I’m working on my own demo which I would like to have ready for Alpha2!!! :slight_smile:

Ooops, almost forgot, big thanks to MaidSafe team for fixing these issues so fast and helping me and others over the early issues.

EDIT: Also, thanks for updating the API docs so they are formatted better :+1:


Hm, really strange. For me it’s the opposite. Since the new binaries I cant authorise web apps anymore. I always geht the well known “Uncaught (in promise) Error: Unexpected (probably a logic error): Could not connect to the SAFE Network” error message. Have tried my own app as well as others (Listy, Chaty etc.). Tried to close the browser, waited some minutes etc. Tested on Win10. Webhosting manager is working fine.

EDIT: Was re-testing it again while writing this and now it magically just worked. However I’m left with the feeling that this issue isn’t fully resolved yet. :confused: Does this limit really has to be so strict?


I just got this error too - on connect after successful authorise I think - still looking.

This may be due to the app having maxed out the connections, so not necessarily the same error I had before. EDIT: yes, seems so because shutting down web hosting manager allows me to get a connection. So maybe you have the same issue - too many things using too many connections?

For development we really need mock working to get the app code mostly debugged offline first, but AFAIK there still a blocker there due to a bug in electron :frowning:

1 Like

I think Xamarin includes emulators, so we should be able to play with it and develop that way too.


Listy and Chaty should be working. There is small bug with the browser but I think will be fixed soon that prevents Vidy and Demoy working.


To quote the venerable Zeno-sama(s): “Wow!” “Wow wow!”

Awesome update guys! Alpha 2 next week? Pumped. I’m going to have to come out of my cocoon and start playing with this bad boy. So as I understand it, Vaults are disabled for now, right?


Today a certain coin stands out in green from the rest in red. :wink: Not only was it good news yesterday from the update but when almost the whole cryptomarket is red, maidsafe will draw atention from the public, youtubers and the crypto media by standing out in green. Excellent marketing. :slight_smile:


Yes that’s right, network is provided by vaults managed by MaidSafe at the moment. Alpha 3 will see users running routing nodes (transient data) while alpha 4 will incorporate a storage layer, and at that point we will see user run vaults. I hope that makes sense.


Windows users:

Please let us know if you experience browser hanging or freezing.

When it occurs, take note of the time for the sake of viewing logs and also which site you were browsing at the time.

All of your reporting has been integral to helping us track down bugs.

Thank you so much.
Special shout out to @JPL, @Joseph_Meagher, and @happybeing

If you choose to report on Github, here’s an existing thread:


Excellent news! Thank you for the timely reply and the info on upcoming changes.


So the new question is, when is Alpha 3 being released? :wink:


Yeah It’s very interesting if we will see Alpha 3 before New Year :slight_smile:

1 Like

Never a moment for a breath around these here parts :slight_smile: In any case anyone can speculate :wink: We just keep doing what we do, not much could speed us up, but lots of pressure will slow the team down. Its worth realising that really. Pressure is OK if you can reap a small reward every so often, but if all that happens is you get another lash on the back to keep moving then it can demotivate.

So positive pressure == great, negative == slow and bad results :D. Our team don’t bother about trading or coin value past checking we are still relevant in early adopters eyes, but they do check this forum and every so often they do get depressed looking. It may be on those individuals, but if you worked solid for several weeks not sleeping then perhaps a wee break for a few hours to sleep with good thoughts would be nice.

However, for me I know that will not be the case and I expect constant criticism and pressure, I am OK at handling it though. I just wanted to point out that some comments can be self fulfilling prophecies. I know you have not been critical here, but sometimes it may be best to say thanks and wait a few hours before pressure is reapplied :smiley: :smiley:


I missed the announcement last night as bed called. Very nice to see great progress. Especially the wee mobile app surprise! Well done team! :slight_smile:


Keep on Truckin’

Keep on Truckin


Feel no pressure please! If I could I’d give you a back rub. Take some time off. Whater ever it takes, no rush. This is the most important project I have heard about in a long time. You have delivered so much already. I’m just grateful. Cheers!


Some people look past this but I couldn’t agree more. You guys and gals should not only get support because you’re building something that will benefit humanity but because you’re good folks to begin with and deserve encouragement on a personal level. I’m pulling for you everyone! I hope I don’t miss anyone @dirvine @nicklambert @frabrunelle @bochaco @hunterlester @Viv @ustulation @Krishna_Kumar @marcin @canndrew @Shona @bart @AndreasF @michaelsproul, @Shankar, I know there are more so @maidsafe you make us proud everyday

How could I forget Nakita!!? @nbaksalyar


Since I first found this project there were so many wow moments. Unfortunately with familiarity the awesomeness of what’s been accomplished is overshadowed by the excitement of what tomorrow brings. This surprise is another wow moment and a great reminder as to why I spend my life on this damn forum. Thanks Maidsafe!!


@happybeing @Mindphreaker , the number of clients can connect at a time is limited to four, let me explain in more detail how you should count them so you know when you are hitting that limit.

When the browser is launched, the Authenticator plugin is loaded, it will create a connection to be able to either register you on the network if you are creating an account or to check the credentials upon an login. This will consume the first client (1 out of 4 allowed clients).

After you logged in, you will see that an authorisation request pops up, this is the browser itself trying to register as a SAFE app to then be able to fetch/save the state, i.e. your bookmarks and browsing history. This information was stored locally before, but since it’s private information we thought it’s better to store it only on the SAFE network within your account. Therefore the browser needs to have your authorisation to connect and be able to store this data on your SAFE account. If you are wondering now what’s the difference between this and any other SAFE app requesting access, the answer is simply “there is no difference at all, it’s just a SAFE app, just embedded in the browser”. Therefore, if you authorise the browser app you are using one more connection (2 out of 4 now).

At this point, you may be trying to open up a safesite, so you open a tab and enter a URL, this is when the safe-app-plugin creates its connection to be able to fetch the site. This will be a single connection used by the safe-app-plugin to fetch all safesites no matter how many tabs/sites you open. In this case the connection is an unregistered connection, i.e. a read-only connection to the network to read only data publicly available, and this is why there is no authorisation request for the user, but it still counts as a client connection. This becomes your third connection (3 out of 4).

When you open a safesite, this can either be a static site which doesn’t use the DOM API so it doesn’t need a connection. But it can be a dynamic site/webapp which does connect to the network either unregistered or registered (it needs user authorisation). As an example of this, the safe://chaty.test app creates an unregistered connection upon being loaded to fetch the chats list, and it closes it and re-opens a new connection (this time a registered connection) when you hit the button to send a message. Therefore, in our scenario, an app like this will have the fourth available connection whilst its tab is open (4 out of 4).

If you try to open any other app which creates a connection, regardless if it’s opened form the browser, a desktop app, (ohh!..I almost forget about this, but now I also have to include it here in the explanation) or from a mobile app :wink: , you should get a connection error since you’ve reached the limit already. So at this point you can close any of the apps that is using a connection to free it, and then be allowed to connect with another app.

As you can imagine, you can decide to not allow the browser app if you are not interested in storing the browsing history or bookmarks on your account, and that would allow you to have one less connection used and available for other app. Or you could avoid opening a safesite so the plugin never creates its own connection if you are trying to play with desktop apps.

The main purpose of this explanation is so you can realise if the issue is due to the clients’ limit, or perhaps an invalid/non-white-listed IP, or something else.


Thankyou all of you - u guys are amazing and this project is beautiful. Hopefully u all get that sleep you deserve tonight :slight_smile: