Update @frabrunelle has caught a couple of errors after updating function nomenclature to better match the API docs. I’ll sort these and push a new release this evening, so perhaps better to hold off on moving to 0.2.8 for now. This weekend back...

0.4.2 Latest/Stable: https://github.com/joshuef/beaker/releases/tag/v0.4.2 Updates Now history/favourites/sitedata and settings APIs from beaker all save to the safeNetwork (when the browser is authorised). Should authentication fail, or you not be...

This features a more robust ‘safemode’ toggle, including a navbar icon showing that you are on the safe network exclusively. This can be toggled by clicking the icon, or going into the File menu. This will reload all tabs upon toggle, blocking/enabling insecure (non safe) content.

Dev Update It’s been a wee bit quiet on the Safe Browser updates as I’ve been knee deep in making some fundamental changes to enable the last stretch goal to be met. So I’m happy to say that I’ve got a working prototype hooking up beaker’s data...

0.4.0. Now with SAFE Sync

More details here:

0.4.2 Latest/Stable: https://github.com/joshuef/beaker/releases/tag/v0.4.2 Updates Now history/favourites/sitedata and settings APIs from beaker all save to the safeNetwork (when the browser is authorised). Should authentication fail, or you not be...

‘Toggle SAFE Browsing’ menu item, I though David’s brief called for a browser that does not connect to clearnet at all? I find this really confusing and what we were trying to avoid, not sure why I would use this browser over my regular browser.

The toggle gives no indication as to what state it is currently in and when the toggle is engaged, all the SAFE tabs do a re-load.

When ‘open link in new tab’, default behaviour should be to remain on current tab.

File/ Open Location - What filetypes is this designed to open? Are the locations on current machine?

The rocket icon that turns into a star/exclamation (next to refresh) what behaviour is this supposed to invoke? (no context when hovering)

The Safenetwork icon… is that going to be pointing to something useful. I’d think it should point to a SAFE hosted version of the Maidsafe site i.e the current central repository of enlightenment and should have a hover value of ‘Help Me’ or similar.

Probably not the fault of beaker, but when the browser is shut down and re-opened, launcher wants to re-authorize, without releasing the previous session(s)

When toggling the Developer Tools, then visiting a SAFE site, beaker kills the current Tab and throws a Javascript error : Object has been destroyed at Error (Native) at Function.Win. Web contents.session.webrequest.onBeforeRequest

‘Authorised with SAFE Launcher’ personally I would like to see ‘Authorised with the SAFE Network’. The ‘Launcher’ is a mental barrier that needs to be banished.

When I decide to try SAFE, I expect to click one link that gives me a browser with some easily accessible links to surf. I do not expect to be prompted with an ‘allow access’ dialogue and a launcher.

SAFE related

Launcher should be packaged with the beaker browser (and named ‘SAFE Network’?)

Why do I need to manually allow the browser in Launcher, can not the system recognise one of it’s official components (MD5 or something)?

Launcher should only run in the background until I initiate an action on the network that requires account creation. ‘This action requires an account, would you like to create one now?’

Account creation process should be a 'step me through it flow, the same as installing local software…I’m familiar with that ( it is not currently obvious that I need to type in a secret and password, should read ‘enter secret and password’ doh!)

Once the ‘launcher’ is happy and I click ‘Finish’, it should minimize to the tray…where geeks can bring it to the front if required.

Current launcher needs the red close button eliminated, I should not be able to close the launcher (disconnecting from the network) in this manner. The only way to shut down launcher, should be a right click from the tray.

Probably not the fault of beaker, but when the browser is shut down and re-opened, launcher wants to re-authorize, without releasing the previous session(s)

Correct. It is not the fault of beaker. It is by the design of their current choice. It is written in the core system. I believe it is in one of the RFC, can’t remember correctly. It said that when user logs out, all cache and tokens are deleted. So it is expected for this behavior to happen.

Launcher should only run in the background until I initiate an action on the network that requires account creation. ‘This action requires an account, would you like to create one now?’

Another reason why authenticator should be headless. It would be easy to plug into any apps. And this is doable on browser, instead of launcher. For example… emacs. If I run any safenet apps on emacs, it will prompt authorization. Much more possibilities with headless authorization tool.

So currently I have 4 instances of Beaker under ‘Authorised Apps’ …that is expected behaviour?

So opening / closing reauth creates a new authed app for you right now. The previous auth is not reused, correct? Or have you used several different versions of beaker without closing the launcher?

chrisfostertv:

When toggling the Developer Tools, then visiting a SAFE site, beaker kills the current Tab and throws a Javascript error : Object has been destroyed at Error (Native) at Function.Win. Web contents.session.webrequest.onBeforeRequest

Some good points above. I like the md5 idea or some such for auto auth. but I think some of this will be addressed with a new authenticator baked in.

chrisfostertv:

I expect to click one link that gives me a browser with some easily accessible links to surf

What would you like to see there? This can be done very easily. But we need reliable /worthwhile links… (and I guess they’d need to be auto created on any network resets to remain useful… )

chrisfostertv:

The toggle gives no indication as to what state it is currently in and when the toggle is engaged, all the SAFE tabs do a re-load.

You mean the icon / rocket is not clear enough? Or what would you like to see?

Tabs reload to allow / prevent non-safe content, so if you have a site trying to request images from the clearnet for example, toggling safemode off would refresh the page and these images would now load. If the page you’re on is only showing safe content, then you wont see any changes.

Now history/favourites/sitedata and settings APIs from beaker all save to the safeNetwork (when the browser is authorised).

Two questions. Where do they save to the SAFE network? And is there any way to opt to save them locally? I ask this because just like one might want to download any other file and save it locally (or back up any other file and save it locally) so to might one want to do the same with their bookmarks and settings. Also there’s the possibility one might want to save said bookmarks and settings between network iterations, particularly the settings in this case. You don’t want to have to reconfigure your safe browser every time the network reincarnates in order to do an update.