I am resending this proposal and now fully support SAFEr Browser(s) Proposal
SAFEbeaker Browser Proposal
This is proposal for the SAFEnetwork community to fund and support the development of a standalone SAFE Browser that directly interacts with SAFEnetwork Launcher and directly with the network. We will use a forked version of Beaker Browser, which is an electron based cross platform engine. The vision of this project is to not only build a core application for the SAFEnetwork that will become the default platform bundled application, but also provide valuable data on how to successfully build utility software needed for the community.
The simplest and most sensible way seems to work with the FS-API Beaker, which is already implemented in Beaker browser, with the ability to intercept calls and redirect them to the API Launcher. https://github.com/pfraze/beaker/blob/master/app/lib/fg/fs-api.js
This will require the creation of a new module based on fs-api, and it will be necessary to put the cap which will redirect all requests to a new module, banning all other outputs (including the file system and to the Internet).
Thus two tasks will be implemented -
- The browser will be able to work only with SAFEnetwork traffic, other traffic will be blocked.
- Work will be available through the API Launcher.
We anticipate this project will require at least 90,000 MaidSafeCoins to complete. This amount was derived from current MAID market value, developer cost estimates, and a small amount to reimburse @MrAnderson’s initial investment and risk.
(If we are over the minimum funding goal, then we will introduce an exciting way we will hire/fund/build these features)
The beaker.fs API is a safe way to access the SAFEnetwork filesystem.
Beaker applications that are loaded via SAFE Launcher have a sandboxed folder available to them. But, they also need a way to get outside the sandbox, eg to work on a spreadsheet in ~/Documents This is an API for both use-cases.
Each application has a sandboxed folder, which they can use without asking permission. This is the 'App' folder.
User Files and Folders
Applications can ask for files and folders outside of their sandbox. These are 'User' files and folders. The permission to use these objects will persist until released by the application.
Merge SAFE Launcher and SAFEbeaker
Used to serve SAFE applications, and provided as a permissioned API.
As @happybeing smartly describes “merging SAFEbeaker with SAFE Launcher so for most activity the user has just one desktop application with websites and Web Apps apps on the browser tabs.”
Node filesystem is on the Beaker’s Dev planned list and should have a SAFE style effect of “raising all boats.” We are open to community input to other desired features and will later introduce a way for the community to vote on what feature to work on next, once the core browser is complete.
Our team consists of:
@PureF - Dev company
@dkarataev has agreed to build this application and has been vetted by @MrAnderson to be more than capable to produce a quality product in stated time of one month. PureF represents a software dev company based in the United States. They develop web applications, ecommerce and mobile apps that bring real value to businesses and online communities. Dev Company are a professional team with 10+ years of experience each that has worked with clients ranging from local businesses to global brands and enterprises. Technologies: Ionic/Cordova (Android&iOS), HTML5, PostCSS, CSS Modules, LESS, NodeJS, AngularJS, ElasticSearch, ReactJS, Gulp, AWS, Webpack, MongoDB, Socket.io. Get in touch for our full portfolio.
@MrAnderson - SAFEnetwork Community Member
Travis Remington will be the point of contact for this project development. He personally reviewed, interviewed, and has a mutually agreed contract with @PureF to build the application. Travis has maintained an active role in the SAFE community forum since early 2014 and has spent extensive time in the crypto-sphere since 2011. In addition to SAFEnetwork community, @MrAnderson is a founding member of Crowd Found Hub and sees this SAFEbrowser as an important milestone in proving the power of community driven development that allows people to labor in freedom. Travis has several projects ready to be built on SAFE and is doing everything possible to contribute to the quick success of MaidSafe and the SAFEnetwork.
POC duration and justification:
We will need to test, which is anticipated to take two weeks; (debugging). Writing a code itself is 20-25 days