Now history/favourites/sitedata and settings APIs from beaker all save to the safeNetwork (when the browser is authorised).
SafeStatus page on load shows whether you are authenticated on the network or displays common error issues.
Should authentication fail, or you not be logged into the launcher, there’s a ‘Reauthenticate’ button on the safe status page to enable reauth without rebooting the browser.
safe-js improvements for app development
More details on development and using some of these features can be found on the dev forum.
I was testing out some sites from this link. But we clearly need to make a new list as the url’s don’t work anymore. And that’s a good thing . But poor @davidpbrown safe://dir.yvette links don’t work anymore
safe://tests exists, and it should not show you any bananas. Although its not a very exciting page visually, it should also ask for AUTH if you’re logged in. Though it wont do anything else (you can see the script on the page…) its a simple mockup someone posted in the dev forum (cant remember who… sorry!) which i ended up using for some test purposes.
Yes, the sites still works. But the latest version of SAFE Beaker browser doesn’t pick the .safenet links or the http so when I browse to your site on alpha using the latest version I see the links but they won’t open. Which is okay for people using Alpha and their current browser of course.
Edit 2: will it be possible to just type krekc and the browser will automatically put safe:// in front of it? Right now I’m not really used to type http:// in my browser either.
and on second thought, could Beaker browser transform http://website.safenet links to safe://website on the fly with whatever formatting is preferred for those links?.. that would then provide user specific safe:// without webmasters needing to do anything with the usual links.
Is it planned to let the browser recognize a safe:// as a link? As the normal links aren’t valid on the system we can’t use any hyperlink method at all at the moment.