A new release of the SAFE Browser (v0.7.0) compatible with Alpha-2 network has been published.
This is the first release in which we are formally making available packages to connect to the Alpha-2 network, as well as those which connect to the
MockVault. We are planning to provide both flavours from now on.
Please note that the artifacts for Windows and OSX were not signed this time, so please use the provided SHA-256 hashes instead.
- Fix the issue with favicons which are now loaded and displayed for safe:// sites.
- Warn the user upon a network disconnection event in the browser, not only from the Authenticator page but in any open tab, and attempt to automatically reconnect every 30 secs if the user doesn’t explicitly do it.
- Assure that when reconnecting to the network, not only the Authenticator connection is re-established but also the ones for the safe_app plugin and the browser app so the browser state can be saved on the network afterwards.
- Functionality to run tests on the DOM API functions within the browser, and creation of a checklist document for manual testing.
- Fix URI scheme registration for dev mode so the browser can receive authorisation requests even when launched with yarn start.
- Minor enhancement to README for Windows build instructions.
- Fix minor issues when fetching sites with a relative path.
- Uses authenticator plugin v0.3.1.
- Uses safe-app plugin v0.3.2.
Where should I report issues?
Feel free to report it on GitHub in the SAFE Browser repository.
Now I see indeed a favicon and less errors in e.g. safe://todo.
This is great stuff, helps people like me with compiling errors
Have been happily using my Mock-Routing builds lately. Thanks so much!
Glad this will continue
But to complete the loop for devs, is there a mock-hosting-manager? So devs can test their code? Or perhaps another website-based demo-app is needed, I’ll see what I can create in terms of that again
The dev tools menu is much clearer now ! thank you
Thank you so much for doing this! Having a prebuilt SAFE Browser with mock routing is awesome. Took me a while to figure out how to build a browser with mock routing, so this is brilliant! Will help new devs out a lot.
Two small packaging things.
I always use 7Zip on windows to open zip files from maidsafe. Never a problem. However, these zip files are locking it up hard and I am unable to unzip them with it.
I unzipped them with WinRAR, and that seemed to work. But the directory names in both zip files are the same. Would be cool if the mock browser had -mock in it’s directory name.
I had the same problem with 7Zip
@Tom_Carlson @JPL Thank you for the feedback.
What exactly are you experiencing when trying to unzip with 7z?
I have just done more testing with 7Zip. I usually just try to unzip the whole thing of course, but now I am trying little pieces at a time to see where the problem lies.
This is not an exhaustive list, but I quit when I felt I found the issue.
7Zip locks up hard when I try to unzip the following directories
What you will notice when you go into these directories is that they contain an empty file that has the same name as a subdirectory. So 7Zip is trying to unpack a folder and an empty file with the same name, in the same place, and locking up hard. (Have to close it with task manager)
Whenever I make a bookmark in SAFEbrowser its never there when I log back in with the same account details. Is this a known bug?
You’d need to save the browser’s state into your account with
Save Browser State (Ctrl + S) before you log out or close the browser. Are you doing this already?
No. I’ll give it ago. Cheers!
ps. Is it hard to make it work like a normal browser in this regards because of the network?
I don’t think it would be hard to add such a behaviour at all, but I would say there are other things that will need to be considered beforehand. E.g. that would/could consume PUTs, thus you would need to provide ways to allow the user to decide/configure when it should be automatically done and when not; or how many PUTs the user wants to allow to be spent in saving the browser state, etc.
As a gral. comment, there are many things which are technically possible and simple to implement but they bring some other type of complexities or additional considerations.
Thanks for the great answer! It really helps clarify the complexity in building the SAFEnetwork compared to the standard net. I forgot it would take PUTs.
Thanks for your hard work bochaco. It’s great what you’re doing
Can we have 0.7 in the Debian repository, please?
There’s no packaging problem. I extracted it with my 7-Zip 17.01 beta (x64) and it work like a charm.
Well it is a problem - but one that the 7-Zip beta seems to have solved (just tried it myself and it worked). It still occurs with the latest stable 7-Zip release though (16.04).
I hope can use it without invitation code, because i’m not following this forum at longtime…
You will need an invitation code, but that shouldn’t be a problem as you are Trust Level 1 (Basic). Just go here https://invite.maidsafe.net/ update your IP and copy the invite code, run SAFE Browser and paste in the invite code when you create an account.